Oculus go problem. Incorrect tiles are displayed.

  • Hi!

    Perhaps a device type "mobilevr" (oculus go) is not correctly detected.

    When I viewing a virtual tour in the oculus go, he displays sets of tiles in multires mode

    Code
    <image if="!webvr.isenabled">

    , and not those that are created specifically for him

    Code
    <image if="webvr.isenabled">

    .

    To exclude my possible mistakes, I checked the test scene by creating a tour with a standard droplet "MAKE VTOUR (VR-OPT) droplet".

    Test confirmed suspicion. The Oculus Go displays tiles from the <image if="!webvr.isenabled"> section, not from the <image if="webvr.isenabled">.

    If you manually erase the entire <image if="!webvr.isenabled"> (multires) section, more suitable tiles are displayed. The image does not suffer from moire, the display performance is quite smooth.

    How to make it work by switching modes?
    I tried using

    Code
    <image devices = "mobilevr">

    . Does not help.

    Moire and slowdowns are very critical. How to get the krpano to display the correct sets of tiles in the oculus of go?

  • Did some testing on my Go and I think I know what you are seeing -- and I finally know why I'm seeing a significant performance problem as you start a tour.

    The problem happens when you first enter VR mode. When you are in non-VR mode the multi-rez tiles are displayed. When you enter VR mode the entire multi-rez scene needs to fully render and only then do you switch to the VR tiles. This takes a long time, especially if using oversampling=2 and looking around during the rendering. In the Oculus browser, it is 7 - 12 seconds for me and significantly longer in FxR. And performance during that time is horrid! Once the VR tiles are in use performance is great.

    Switching scenes in VR mode only shows the VR tiles. Transitions a quick and performance great. When you switch out of VR the multi-rez tiles again display.

    To demonstrate this I put together a test case where I use tiles from different panos for preview, multi-rez and VR within a scene.

    Klaus - This is a critical problem that has been pissing off a couple of clients and causing me to lose hair. It may be related to a recent update in the Oculus Environment because the same thing suddenly started happening even with v1.19.16 in all browsers on the Go. But I think the solution could be quick and easy. Two ideas:

    1) If you are in a mobilevr browser, only display the VR tiles (and previews, of course) even in a window. If someone really wants the desktop experience in a headset they can click the browser's "desktop mode" button.

    2) When switching to VR mode immediately switch to the VR tiles, perhaps using the preview as an intermediary, if needed.

    PLEASE fix this ASAP. It is business-critical for me.

  • My colleagues advised me on a simple workaround for the problem:


    Code
    <events name="vr_enter_workaround" webvr_onentervr="loadscene(get(scene[get(xml.scene)].name), null, keepview, blend(0.5))"  keep="true" />




    And it worked.
    Work only on 1st scene %)

  • Hi,

    to load the special VR images directly on startup on devices like the Oculus Go or Oculus Quest change the xml this way:

    Explanation: the device.mobilevr setting (new since 1.20) is true on these devices and so the VR images get loaded directly on startup even when not in VR mode. And by setting the havevrimage setting to false on these devices the reloading of the image will be skipped when entering VR mode, because it would be the same in this case.

    Additionally attached here an updated vtour-vr.config to add these settings automatically on building:
    vtour-vr-config.zip

    Btw - oversampling=2 should be not necessary when using version 1.20, that version uses automatically a higher oversampling setting.

    Best regards,
    Klaus

  • Hi,

    one additional change - when using the desktop mode in the Oculus browser it's not possible to detect that the device is a 'mobilevr' device, so here small change in the vtourksin.xml to load the VR images faster:

    Look for this line in the vtourskin.xml:

    Code
    loadscene(get(xml.scene), null, MERGE|KEEPVIEW|KEEPMOVING|KEEPPLUGINS|KEEPHOTSPOTS|NOPREVIEW, BLEND(0.5));

    and remove there the NOPREVIEW flag:

    Code
    loadscene(get(xml.scene), null, MERGE|KEEPVIEW|KEEPMOVING|KEEPPLUGINS|KEEPHOTSPOTS, BLEND(0.5));

    That avoids the waiting until the vr images are fully loaded.
    For not available parts the preview pano image will shown instead.

    Best regards,
    Klaus

  • WOWZA, those changes make a world of difference. Sadly my hair may never come back but I should be able to keep some clients.

    Not sure anyone has mentioned this before but Klaus.... Darn, you are good!

    And big thanks for localhostroot. Without your original post I don't know how long it would have taken to figure this out.

    As to oversampling=2 not being necessary, I'm not so sure. I did the comparison and on my Go aliasing is essentially eliminated and detail is noticeable improved. And I don't detect a performance hit. For me, oversampling=2 is still essential.

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!