Can you tell me if you already know this issue ?
Thank you so much, Klaus ! You're the best ! CheersCan 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
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/
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.
|
|
Quellcode |
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();
);
);
|
|
|
Quellcode |
1 2 3 4 5 6 |
<action name="test" autorun="onstart">
if(true, break());
trace('a')
break();
trace('b');
</action>
|
That's not a bug, that's how the break() currently is intended to work.so i guess either there is a bug or "stop the execution of the current actions call" is not meant how i understand it
I will think about it, maybe as exitcall()...it would be nice to have a return(), even if it is not used for a return value. could be called exit() ?
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?