vlookatmin / vlookatmax not working with gyro2 before the first loadscene call

chugreevd · November 5, 2016 at 3:47 PM

Hi,

I am having the following issue with html5 + gyro2 (tested on 1.19-pr8):

vlookatmin and vlookatmax are ignored UNTIL the first switch to another scene. (In another words, I have a limited vertical FOV pano and don't want to see the black holes, but the viewer still lets me see them)

Both vlookatmin and vlookatmax are set to 0

Code

<view fov="67.7371694067" fovmax="67.7371694067" fovtype="VFOV" hlookat="0" limitview="lookat" maxpixelzoom="2.0" vlookatmax="0" vlookatmin="0"/>

Adding this code to plugin[skin_gyro].onavailable solves the problem but introduces a noticeable lag, so it is not an ideal solution:

Code

delayedcall(0.1, loadscene(get(xml.scene),null,get(skin_settings.loadscene_flags),get(skin_settings.loadscene_blend));			plugin[skin_gyro].resetSensor(get(view.hlookat)););

With the old gyroscope plugin it is working well.

Is it a bug, or what might be wrong?
Thanks.

klaus.krpano · November 11, 2016 at 9:55 AM

Hi,

when the gyro gets enabled, then it disables the viewing limitations.

A way to get limiting with gyro usage anyway would be this:

Code

<plugin name="gyro"
   ...
   camroll="false"
   onenable="set(view.limitview, range);"
   ...
   />

The setting camroll="false" should be set because the rolling is ignored in the viewing limitations.

Best regards,
Klaus

chugreevd · November 14, 2016 at 3:23 PM

Hi Klaus,

Thank you, it worked.
With the only difference -- instead of "set(view.limitview, range);" I had to do "set(view.limitview, lookat);"

vlookatmin / vlookatmax not working with gyro2 before the first loadscene call

Participate now!

Users Viewing This Thread