You are not logged in.

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

Dear visitor, welcome to krpano.com Forum. If this is your first visit here, please read the Help. It explains in detail how this page works. To use all features of this page, you should consider registering. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.

klaus.krpano

Administrator

  • "klaus.krpano" started this thread

Posts: 12,884

  • Send private message

101

Thursday, May 12th 2016, 7:42am

Quoted from "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

sgk

Beginner

Posts: 1

  • Send private message

102

Thursday, May 12th 2016, 9:50am

Time line for VR hotspots

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

LMB

Trainee

Posts: 60

  • Send private message

103

Thursday, May 12th 2016, 10:18pm

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?

Source code

 
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>

andrewglover

Beginner

Posts: 19

  • Send private message

104

Wednesday, May 18th 2016, 3:41pm

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.

Timescale

Trainee

Posts: 120

Location: Netherlands

Occupation: Archaeologist, Timescale R&D

  • Send private message

105

Wednesday, May 18th 2016, 4:00pm

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 :

Source code

 
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.

andrewglover

Beginner

Posts: 19

  • Send private message

106

Wednesday, May 18th 2016, 4:46pm

Quoted from "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.

Timescale

Trainee

Posts: 120

Location: Netherlands

Occupation: Archaeologist, Timescale R&D

  • Send private message

107

Wednesday, May 18th 2016, 5:20pm

Quoted from "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.

herrpedro

Intermediate

Posts: 171

Location: Lisbon

Occupation: Programmer/analyst

  • Send private message

108

Friday, May 20th 2016, 11:46am

*thumbsup* *thumbsup* *thumbsup*

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

mastucc

Beginner

Posts: 37

  • Send private message

109

Monday, May 23rd 2016, 10:31am

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:







Thank, Marco

This post has been edited 1 times, last edit by "mastucc" (May 23rd 2016, 10:44am)

Umalo

Professional

Posts: 1,051

Location: Osijek, Croatia, EU

  • Send private message

110

Monday, May 23rd 2016, 1:48pm

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)

This post has been edited 1 times, last edit by "Umalo" (May 24th 2016, 7:55am)

klaus.krpano

Administrator

  • "klaus.krpano" started this thread

Posts: 12,884

  • Send private message

111

Monday, May 23rd 2016, 9:34pm

Hi,

Quoted from "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:

    Source code

    		 
    1

    <layer name="defaultskin_buttons" scale="2.0" devices="mobile" />
    to this:

    Source code

    		 
    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

Tuur

Sage

Posts: 3,431

Location: Netherlands

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

  • Send private message

112

Monday, May 23rd 2016, 10:19pm

Source code

 
1

if="device.mobile AND stagescale LT 1.0"


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

Tuur *thumbsup*
https://www.virtualtuur.com
Skype:studiotuur

Krpano ToolBox: https://krpano.com/forum/wbb/index.php?p…&threadID=16023
Measure in 360 photos with : https://pame.virtualtuur.com
Moving Hotspots V2: https://krpano.com/plugins/userplugins/movinghotspots/#top

klaus.krpano

Administrator

  • "klaus.krpano" started this thread

Posts: 12,884

  • Send private message

113

Tuesday, May 24th 2016, 7:24pm

Quoted from "Tuur"

Didn't know that way of using 'if'
See here: http://krpano.com/docu/xml/#if ;-)

klaus.krpano

Administrator

  • "klaus.krpano" started this thread

Posts: 12,884

  • Send private message

114

Tuesday, May 24th 2016, 7:25pm

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

dreamcutter

Beginner

Posts: 48

Location: Moscow

  • Send private message

115

Tuesday, May 24th 2016, 9:01pm

*thumbsup*

zappano

Trainee

Posts: 52

  • Send private message

116

Monday, May 30th 2016, 11:11am

New Button in mobile layout

Hi all there

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



Source code

 
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?

Source code

 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76

	<!-- 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

This post has been edited 1 times, last edit by "zappano" (May 30th 2016, 1:28pm)

benji33

Intermediate

Posts: 244

Location: France

Occupation: Senior Software engineer

  • Send private message

117

Tuesday, May 31st 2016, 3:10pm

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

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

tsukada

Beginner

Posts: 27

Location: Tokyo, Japan

Occupation: Programmer

  • Send private message

118

Wednesday, June 1st 2016, 1:06pm

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.

klaus.krpano

Administrator

  • "klaus.krpano" started this thread

Posts: 12,884

  • Send private message

119

Wednesday, June 1st 2016, 3:24pm

Quoted from "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

tsukada

Beginner

Posts: 27

Location: Tokyo, Japan

Occupation: Programmer

  • Send private message

120

Thursday, June 2nd 2016, 3:11am

Hi Klaus,

Thanks for your quick response.
That works quite well.

Similar threads