Sie sind nicht angemeldet.

Scott Witte

Fortgeschrittener

  • »Scott Witte« ist der Autor dieses Themas

Beiträge: 382

Wohnort: Milwaukee, WI USA

Beruf: Professional Photographer

  • Nachricht senden

1

Sonntag, 10. Januar 2016, 06:51

Previous / Next buttons bug in VR mode?

In VR mode, when you tilt down far enough the previous / next buttons float up. I gather this is by design. Clicking one will change scenes but the cursor is no longer locked in the center of the screen. It floats and never re-calibrates. Is this a bug. I'm using IOS 9.2, Safari.

2

Mittwoch, 13. Januar 2016, 11:59

Hi,

I haven't seen such yet - link to the example?

Best regards,
Klaus

Scott Witte

Fortgeschrittener

  • »Scott Witte« ist der Autor dieses Themas

Beiträge: 382

Wohnort: Milwaukee, WI USA

Beruf: Professional Photographer

  • Nachricht senden

3

Mittwoch, 13. Januar 2016, 19:31

Example: Lakehouse

It may not happen in the first pano but beyond that it is very consistent for me.

Scott Witte

Fortgeschrittener

  • »Scott Witte« ist der Autor dieses Themas

Beiträge: 382

Wohnort: Milwaukee, WI USA

Beruf: Professional Photographer

  • Nachricht senden

4

Sonntag, 17. Januar 2016, 00:15

Figured it out

The problem happens when setting architectural view to something other than 0. In my case I have architectural="1" added to the scenes' view elements.

Again, to reproduce using my Lake House example above switch to VR Mode (fake VR Mode is fine). Tilt down and hover-click a next/previous arrow. The first time it works as expected, changing panos and keeping the view. The second time you do this KEEPVIEW is not honored. Rather the default view is displayed and the cursor no longer stays centered.

I can't think of an easy workaround. It doesn't seem there is a devicecheck for VRMode, for instance ( architectural.no-webvr ). Any chance this can be fixed soon???

5

Dienstag, 19. Januar 2016, 21:40

Hi,

I will look for it - the problem might be related to changing the view setting when in WebVR mode.

Currently the WebVR works that way - when entering VR mode, a backup of the current <view> setting will be made and then the <view> settings for VR will be set - BUT when now the <view> settings will be changed later, this can cause problems.

About devicecheck for VR - that's not possible - WebVR is not a device, it's a plugin that will be added later and it does VR-support detection at runtime.

Best regards,
Klaus