You are not logged in.

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.

121

Friday, March 16th 2018, 3:15pm

Can you tell me if you already know this issue ?

Sure - it's a Chrome bug - see these threads for more information about updated plugins:
Possible gyro issue with Chrome 65 for Android.
Webvr not working with Chrome's latest updates

122

Saturday, March 17th 2018, 9:10pm

Can you tell me if you already know this issue ?

Sure - it's a Chrome bug - see these threads for more information about updated plugins:
Possible gyro issue with Chrome 65 for Android.
Webvr not working with Chrome's latest updates
Thank you so much, Klaus ! You're the best ! Cheers

Posts: 1,850

Occupation: Virtual Tours - Photography - Krpano developer

  • Send private message

123

Monday, March 19th 2018, 7:49pm

You can download Chrome Canary for the moment to get it working.

Hello Klaus !

I've noticed that since the last Chrome update ( 65 ) the gyroscope is not working anymore on my Samsung smartphone.

http://www.prismamediaxrlab.com/tour-de-france/

KRPano Developer: Portfolio ::Gigapixel Tagging Solutions - Porfolio 2 :: Facebook :: Twitter :: reddit.com/r/VirtualTour

jordi

Intermediate

Posts: 427

Location: Barcelona

Occupation: creating ideas & coding them

  • Send private message

124

Tuesday, March 20th 2018, 12:39pm

i also never understood break();
long ago i tested it and i failed to use it to exit an action on a condition.
since then i never used it again.



Just a simple code for demo

Source code

1
2
3
4
5
6
7
8
for(set(i,0), i LT 2000, inc(i), 
	if(scene[get(i)].name, 
		error(i);
		,
		error('no more scenes');
		break();
	);
);


you can check it will stop once the condition is not true anymore, and then you will avoid looping until 2000
everpano.com smart virtual tours

125

Tuesday, March 20th 2018, 6:01pm

the docs say:
"Break / stop the execution of the current actions call."

now, the problem is that break() only breaks the actual block
this works for loops, but you cant use it in a condition to exit an action.

Source code

1
2
3
4
5
6
	<action name="test" autorun="onstart">
 		if(true, break());
 		trace('a')
		break();
 		trace('b');
	</action>


INFO: a <--- this should not happen
note: the 2nd break() works, 'b' wasnt logged

strangely it works in the condition in your example....
so i guess either there is a bug or "stop the execution of the current actions call" is not meant how i understand it

it would be nice to have a return(), even if it is not used for a return value. could be called exit() ?

Scott Witte

Intermediate

Posts: 248

Location: Milwaukee, WI USA

Occupation: Professional Photographer

  • Send private message

126

Wednesday, March 21st 2018, 4:31am

Hotspot math in WebVR problems

Hi Klaus,

Having a hard time understanding the new hotspot math in WebVR mode. For example, I place the scene title in a non-distorted text hotspot at the top of the stage. In non-vr mode and in pre pr14 releases that is easy: oy = stageheight/-2. But in true WebVR mode (simulated works much differently) in pr14 I can't figure out what is going on. What is the formula?

If you want to see my various attempts I will post them.

127

Thursday, March 22nd 2018, 8:52am

Hi,

so i guess either there is a bug or "stop the execution of the current actions call" is not meant how i understand it
That's not a bug, that's how the break() currently is intended to work.

But for the next release I have improved the break() functionality a bit - then call break() will not only stop the current flow of actions, but also one flow from 'one level' up - that means when called inside an if() it will stop the flow inside the if() actions and also the flow() that was calling that if() - and if there was a loop() one level up, then also this loop.


it would be nice to have a return(), even if it is not used for a return value. could be called exit() ?
I will think about it, maybe as exitcall()...

128

Thursday, March 22nd 2018, 8:59am

Having a hard time understanding the new hotspot math in WebVR mode. For example, I place the scene title in a non-distorted text hotspot at the top of the stage. In non-vr mode and in pre pr14 releases that is easy: oy = stageheight/-2. But in true WebVR mode (simulated works much differently) in pr14 I can't figure out what is going on. What is the formula?

Sorry, but placing hotspots relative the screensize is a bad idea in VR - in VR there is basically no screen anymore. The screen size and resolution defines indirectly only the maximum possible fov, but that's also depended on the VR headset and the lens distortion. And the field-of-view is not square, depending on the lens it is a mixture of round and square.

That means the screen/stage sizes shouldn't be used in VR for positioning at all.
Better just use fixed angels in VR (like in real) - e.g. something 30° degree upward (atv=-30).

Best regards,
Klaus

129

Thursday, March 22nd 2018, 9:20am

I will think about it, maybe as exitcall()...

that would be great *squint*
it just would allow nicer code by avoiding big condition blocks sometimes

spacerywirtualne

Professional

Posts: 866

Location: Poland, Europe

Occupation: krpano developer : virtual tours

  • Send private message

130

Thursday, March 22nd 2018, 10:13am

I will think about it, maybe as exitcall()...

It would be great. *thumbsup*


Piotr
You own online, cloud tool for creating virtual tours - www.cms4vr.com

facebook page :: facebook group :: youtube

cms4vr team *thumbsup*

Similar threads