krpano 1.19-pr4 / 1.19-pr5 / 1.19-pr6

Lieber Besucher, herzlich willkommen bei: krpano.com Forum. Falls dies Ihr erster Besuch auf dieser Seite ist, lesen Sie sich bitte die Hilfe durch. Dort wird Ihnen die Bedienung dieser Seite näher erläutert. Darüber hinaus sollten Sie sich registrieren, um alle Funktionen dieser Seite nutzen zu können. Benutzen Sie das Registrierungsformular, um sich zu registrieren oder informieren Sie sich ausführlich über den Registrierungsvorgang. Falls Sie sich bereits zu einem früheren Zeitpunkt registriert haben, können Sie sich hier anmelden.

1
…
- 2
- 3
4
5
6
7
8
9
10

klaus.krpano

Administrator

Beiträge: 13 499

101

Donnerstag, 12. Mai 2016, 07:42

Zitat von »svb«

The pano quality in the Samsung Browser is not as good as in chrome, is there a higher compression or is there a lower quality loaded?

The Samsung VR browser is rendering the WebVR WebGL canvas only with 2048x1024px - that's for both eyes and before lens distortion - and that's very low. Manually trying to increase that resolution doesn't work. Samsung itself would need to improve the browser.

Best regards,
Klaus

Zum Seitenanfang

sgk

Anfänger

Beiträge: 1

102

Donnerstag, 12. Mai 2016, 09:50

Time line for VR hotspots

Hi Klaus,
is there an indicative timeline for completion of hotspots in stereo panoramas / VR?
Great program.
Steffan

Zum Seitenanfang

LMB

Schüler

Beiträge: 60

103

Donnerstag, 12. Mai 2016, 22:18

textfield not selectable

Hi Klaus,

With the new PR4, I find that the textfield is not selectable anymore.
With PR3, and variable selectable="true", I can select the text

Without changing the XML:
* if I use the PR4 krpano.JS/SWF, and leave the old plugins: text not selectable (handcursor)
* if I use the PR3 krpano.JS/SWF, and change the textfield.swf plugin to the one of PR4: text not selectable

are there any new settings I should be aware of?

Quellcode

1
2
3

<layer name="xmask" type="container" align="lefttop" x="10" y="30" width="300" height="284" bgcolor="0xFFFFFF" bgalpha="0.8" maskchildren="true">
<plugin name="xmasktext" keep="true" url="%SWFPATH%/plugins/textfield.swf" html="tmptxt" css="font-family:Tahoma; font-size:13px;" border="false" background="false" selectable="true" align="lefttop" y="2" width="100%" height="100%"/>
</layer>

Zum Seitenanfang

andrewglover

Anfänger

Beiträge: 19

104

Mittwoch, 18. Mai 2016, 15:41

mobilevr_touch_support

Can someone please explain to me what this specif attribute (mobilevr_touch_support) does on the webVR plugin?

I'm trying to come up with a way to place a hotspot on a layer that floats in the top center of the spit screen so that it can detect touch based events within that trigger zone and trigger an event on whatever hotspot the cursor is over.

Zum Seitenanfang

Timescale

Schüler

Beiträge: 120

Wohnort: Netherlands

Beruf: Archaeologist, Timescale R&D

105

Mittwoch, 18. Mai 2016, 16:00

There exists documentation : http://krpano.com/plugins/webvr/#mobilevr_touch_support

If you need a clickable layer in the top center somewhere that works in VR then you could simply try :

	Quellcode
1	<plugin name="cornerClick" url="./TransparantClickArea.png" align="top" y="12" onclick=anActionOnClick()" />

Also, next time try and post non release related posts and questions in the appropriate forum channel.

Zum Seitenanfang

andrewglover

Anfänger

Beiträge: 19

106

Mittwoch, 18. Mai 2016, 16:46

Zitat von »Timescale«

Also, next time try and post non release related posts and questions in the appropriate forum channel.

Thank you for the help. There is currently not a webVR plugin forum channel, which is why it was asked here.

Zum Seitenanfang

Timescale

Schüler

Beiträge: 120

Wohnort: Netherlands

Beruf: Archaeologist, Timescale R&D

107

Mittwoch, 18. Mai 2016, 17:20

Zitat von »andrewglover«

Thank you for the help. There is currently not a webVR plugin forum channel, which is why it was asked here.

I'd say a generic thread in the channel "plugins" or something in the krpano viewer channel (general or under beginners) would be more appropriate I feel.

Zum Seitenanfang

herrpedro

Fortgeschrittener

Beiträge: 210

Wohnort: Lisbon

Beruf: Programmer/analyst

108

Freitag, 20. Mai 2016, 11:46

will try this this weekend... just noticed that there was the pr4.. been away for a while.

nice work and thank you!

Rui Pedro
https://www.panoramalace.com

Zum Seitenanfang

mastucc

Anfänger

Beiträge: 37

109

Montag, 23. Mai 2016, 10:31

Buttons bar problem with 1.19pr4

Hi Klaus, hi all.
I would like to report a problem with 1.19pr4.
With the version 1.19pr4 the the buttons version does not scale correctly, while with version 1.18.5 - 1.18.6 it work very fine.
I tested this example a sun Galaxy S7 Edge with Firefox and Chrome browers.
Does anyone have the same problem???

Link:

1.18 -> http://www.marcostucchi.com/temp/vr18/a.html

1.19pr4 -> http://www.marcostucchi.com/temp/vr/a.html

Thank, Marco

Dieser Beitrag wurde bereits 1 mal editiert, zuletzt von »mastucc« (23. Mai 2016, 10:44)

Zum Seitenanfang

Umalo

Profi

Beiträge: 1 051

Wohnort: Osijek, Croatia, EU

110

Montag, 23. Mai 2016, 13:48

Could be:
- http://krpano.com/docu/html/#mobilescale
You have mobilescale:1.0 in html
See more here

- <krpano version="1.18"> in a.xml while you are posting 19.4 example
- maybe old plugins used in plugins folder (don't think this is case here, but people usually forget to update also plugins)

Dieser Beitrag wurde bereits 1 mal editiert, zuletzt von »Umalo« (24. Mai 2016, 07:55)

Zum Seitenanfang

klaus.krpano

Administrator

Beiträge: 13 499

111

Montag, 23. Mai 2016, 21:34

Hi,

Zitat von »mastucc«

With the version 1.19pr4 the the buttons version does not scale correctly

Thanks - right, that's due an updated default html template file (with mobilescale=1.0 by default now) and missing update of the defaultskin.xml (which assumes a mobilescale=0.5 for mobile devices).

To correct this:

either remove the mobilescale=1.0 from the html file

or edit the defaultskin.xml and change this line:

	Quellcode
1	<layer name="defaultskin_buttons" scale="2.0" devices="mobile" />

to this:

	Quellcode
1	<layer name="defaultskin_buttons" scale="2.0" if="device.mobile AND stagescale LT 1.0" />

(this change/fix will be also included in the next release)

Best regards,
Klaus

Zum Seitenanfang

Tuur

Erleuchteter

Beiträge: 3 839

Wohnort: Netherlands

Beruf: Krpano custom coding / Virtual Tours / Photography / Musician / Recording engineer

112

Montag, 23. Mai 2016, 22:19

	Quellcode
1	if="device.mobile AND stagescale LT 1.0"

AH!
Good to know!
Didn't know that way of using 'if'
*love*

Tuur

https://www.virtualtuur.com
Panimator: https://krpano.com/plugins/userplugins/panimator/#top
ToolBox: https://bit.ly/3TTnd6U
Measure in 360 photos

: https://pame.virtualtuur.com
Moving Hotspots V2: https://krpano.com/plugins/userplugins/movinghotspots/#top
Donations
https://bit.ly/3NnpynC

Zum Seitenanfang

klaus.krpano

Administrator

Beiträge: 13 499

113

Dienstag, 24. Mai 2016, 19:24

Zitat von »Tuur«

Didn't know that way of using 'if'

See here: http://krpano.com/docu/xml/#if ;-)

Zum Seitenanfang

klaus.krpano

Administrator

Beiträge: 13 499

114

Dienstag, 24. Mai 2016, 19:25

Hi,

there is an update for version 1.19-pr4 - krpano 1.19-pr5 - its' mainly a bug-fix release.
Many things that were working in older versions, but not in 1.19-pr4, should now work again.

These things were fixed:

<layer> elements without align setting were positioned wrong.
When changing the crop setting, the width and height settings were not updated instantly like in previous versions.
In some cases the width and height settings were not set/updated already in the onloaded event and this was leading to many incompatibly problems.
The position of non-zoomed/non-distorted webgl-hotspots was wrong.
The size of non-zoomed/non-distorted webgl-hotspots was wrongly 'stage-scaled'.
The position of css3d-hotspots with children elements was wrong in some cases.
The position of textfield-hotspots was wrong sometimes in some cases.
It was not possible to re-use a videoplayer plugin a second time as pano.
Don't trigger the onout event when changing/reloading a webgl-hotspot image.
WebGL creation error when the pano-element had a size of exactly 320x240px at startup.
Support the latest GearVR 'Samsung Internet' browser.
Disable/block autorotate in VR mode.
Support HTTPS in Bing Maps plugin.
The width of an opened combobox was wrong in some cases.
The name of <action> elements with protect=true were wrongly case-sensitive.
The defaultskin.xml supports mobilescale=1.0.
Fixed for the vtourskin.xml: map spots were behind the map in some browsers, calling skin_hideskin at startup works now, improved deep-linking.
Updated Three.js example.

Best regards,
Klaus

Zum Seitenanfang

dreamcutter

Schüler

Beiträge: 56

Wohnort: Moscow

115

Dienstag, 24. Mai 2016, 21:01

Zum Seitenanfang

zappano

Schüler

Beiträge: 52

116

Montag, 30. Mai 2016, 11:11

New Button in mobile layout

Hi all there

I want to add one button here, is no problem in desktop mode:

	Quellcode
1 2 3	<layer name ="infobutton" style="skin_base\|skin_glow" crop="64\|710\|64\|64" align="bottom" x="230" y="0" scale="0.6" alpha="1.0" keep="true" onclick="action(showintroimage);" />

But where in vtourskin.xml must I add this button in mobile layout in the center of this menu?

It must be here in this part, ist there anybody, who can explain me this?

Quellcode

	<!-- determine the visibility of the buttons and calculate their positions -->
	<action name="skin_arrange_buttons">
		calc(show_selbuttons, scene.count GT 1);
		calc(show_thumbutton, skin_settings.thumbs == true);
		calc(show_mapbutton,  skin_settings.maps == true);
		calc(show_gyrobutton, plugin[skin_gyro].available == true AND view.vlookatrange == 180 );
		calc(show_vrbutton,   webvr.isavailable == true);
		calc(show_fsbutton,   device.fullscreensupport == true);
		calc(show_infobutton,  skin_settings.maps == true);
		
		set(lpos,6);
		set(cpos,0);
		if(show_gyrobutton, dec(cpos,20));
		if(show_vrbutton, dec(cpos,24));
		set(rpos,6);

		calc(show_dirbuttons, !device.mobile AND ((area.pixelwidth + 2*cpos) GT 520));

		copy(layer[skin_btn_navi].visible, show_dirbuttons);

		copy(layer[skin_btn_prev].visible, show_selbuttons);
		copy(layer[skin_btn_next].visible, show_selbuttons);
		if(show_selbuttons, inc(lpos,44); inc(rpos,44); );

		copy(layer[skin_btn_thumbs].visible, show_thumbutton);
		copy(layer[skin_btn_thumbs].x, lpos);
		if(show_thumbutton, inc(lpos,40));

		copy(layer[skin_btn_map].visible, show_mapbutton);
		copy(layer[skin_btn_map].x, lpos);
		if(show_mapbutton, inc(lpos,40));
		

		

		if(show_dirbuttons,
			copy(layer[skin_btn_navi].x, cpos);
			inc(cpos,140);

			set(layer[skin_btn_gyro].align, center);
			copy(layer[skin_btn_gyro].visible, show_gyrobutton);
			copy(layer[skin_btn_gyro].x, cpos);
			if(show_gyrobutton, inc(cpos,48));

			set(layer[skin_btn_vr].align, center);
			copy(layer[skin_btn_vr].visible, show_vrbutton);
			copy(layer[skin_btn_vr].x, cpos);
			if(show_vrbutton, inc(cpos,80));
		  ,
			set(layer[skin_btn_gyro].align, left);
			copy(layer[skin_btn_gyro].visible, show_gyrobutton);
			copy(layer[skin_btn_gyro].x, lpos);
			if(show_gyrobutton, inc(lpos,40));

			set(layer[skin_btn_vr].align, left);
			copy(layer[skin_btn_vr].visible, show_vrbutton);
			copy(layer[skin_btn_vr].x, lpos);
			if(show_vrbutton, inc(lpos,80));
		  );

		copy(layer[skin_btn_hide].x, rpos);
		inc(rpos,40);		
		


		copy(layer[skin_btn_fs].visible, show_fsbutton);
		copy(layer[skin_btn_fs].x, rpos);
		if( show_fsbutton, inc(rpos,40));

		copy(layer[infobutton].x, 40);
				

		
		
		
	</action>

Thanks
MIchael

Dieser Beitrag wurde bereits 1 mal editiert, zuletzt von »zappano« (30. Mai 2016, 13:28)

Zum Seitenanfang

benji33

Fortgeschrittener

Beiträge: 244

Wohnort: France

Beruf: Senior Software engineer

117

Dienstag, 31. Mai 2016, 15:10

I've noticed a "redraw" issue on iPhone when NOBLEND is used with a loadscene with these parameters :
loadscene(%1, "view.fisheyefovlink=0.5&view.architectural=0.0&view.pannini=0.0&view.fisheye=0.0&view.stereographic=false", NOPREVIEW|MERGE|KEEPVIEW|KEEPMOVING, NOBLEND);

No issue with this kind of BLEND : BLEND(0.1, easeInCubic)

Zum Seitenanfang

tsukada

Anfänger

Beiträge: 27

Wohnort: Tokyo, Japan

Beruf: Programmer

118

Mittwoch, 1. Juni 2016, 13:06

Gif animation

Hi,

With pr3 gif animation hotspot works well.
But with pr4 or pr5 gif animation doesn't work.
In case of layer, gif animation still works.

Is there any way to activate gif animation hotspot with pr4/pr5 ?

Our application's base already moved to pr4 and I know very well how to make animation hotspots with krpano,
but our customers already used gif animations and want to use gif animation.

Any advice is appreciated.

Zum Seitenanfang

klaus.krpano

Administrator

Beiträge: 13 499

119

Mittwoch, 1. Juni 2016, 15:24

Zitat von »tsukada«

Is there any way to activate gif animation hotspot with pr4/pr5 ?

Yes, just add -renderer="css3d" - to your hotspots, then the browser will render the hotspots via CSS3D transform as in the previous versions.

But note - using gif animations is not recommend - there is no Flash support, on some mobile devices their usage is causing bad overall performance, they have only limited color palette, only 1 bit transparency, there is no animation control - and there is no support for WebGL and VR planed.

Best regards,
Klaus