Skip to main content
motorsep
Inspiring
June 6, 2018

[Go / Gear VR] Are UE 4.20 updates relevant to mobile VR ?

@imperativity

4.20 preview 1 is out and it has some interesting goodies: https://forums.unrealengine.com/unreal-engine/announcements-and-releases/1485599-unreal-engine-4-20-preview

I am wondering if any of those goodies relevant to Go / Gear VR (GLES2 and Vulkan in the nearest future):

Instanced Stereo Rendering: Translucency Support. We’ve taken the improvements to the Instance Stereo Rendering (ISR) path that we made for Robo Recall, and improved them to work across a more robust set of features in the engine. 4.20 adds support for performing the translucency rendering pass using ISR, which can significantly reduce CPU cost on translucency-heavy scenes

Mobile Updates:
  • All of the mobile improvements and optimizations we’ve made for Fortnite on iOS and Android
    • Improved Android Debugging
    • Mobile Landscape Improvements
    • RHO Thread on Android
    • Occlusion Queries on Mobile
    • Software Occlusion Culling
    • Platform Material Stats
    • Improve Mobile Specular Lighting Model


    This topic has been closed for replies.

    43 replies

    Show previous replies
    Neontop
    Inspiring
    July 28, 2018
    Voted...Thanks @voobrazhenie
    motorsepAuthor
    Inspiring
    July 28, 2018


    Hey! I found one critical issue in unreal engine 4.20.0 and 4.20.1. Gear VR touch input is disabled. After bug report to ue, they approved and created a bug - https://issues.unrealengine.com/issue/UE-62251. Hope it will be fixed in 4.20.2. Vote for bug if you can. 
    motorsepAuthor
    Inspiring
    July 28, 2018
    I hate this forum software - once I accidentally hit Tab and cursor goes into quoted field, I can't get it out and type my reply :/ Sorry about post with quote but no reply.

    @voobrazhenie Here is what I wanted to say - it's worth sending a bug report to Oculus directly, because Epic might have a target fix for 4.99 (as there is no Gear VR support in Fortnite BR) and I am sure we all need it to be fixed in 4.20.2  ;)
    Anonymous
    July 30, 2018


    Hey! I found one critical issue in unreal engine 4.20.0 and 4.20.1. Gear VR touch input is disabled. After bug report to ue, they approved and created a bug - https://issues.unrealengine.com/issue/UE-62251. Hope it will be fixed in 4.20.2. Vote for bug if you can. 

    Actually this is by design by Oculus I think in the new Oculus SDK version? There are new nodes for the GearVR touchpad:


    Once I switched to using these everything worked as expected again

    Anonymous
    July 30, 2018

    motorsep said:

    @imperativity

    4.20 preview 1 is out and it has some interesting goodies: https://forums.unrealengine.com/unreal-engine/announcements-and-releases/1485599-unreal-engine-4-20-preview

    I am wondering if any of those goodies relevant to Go / Gear VR (GLES2 and Vulkan in the nearest future):

    Instanced Stereo Rendering: Translucency Support. We’ve taken the improvements to the Instance Stereo Rendering (ISR) path that we made for Robo Recall, and improved them to work across a more robust set of features in the engine. 4.20 adds support for performing the translucency rendering pass using ISR, which can significantly reduce CPU cost on translucency-heavy scenes

    Mobile Updates:
    • All of the mobile improvements and optimizations we’ve made for Fortnite on iOS and Android
      • Improved Android Debugging
      • Mobile Landscape Improvements
      • RHO Thread on Android
      • Occlusion Queries on Mobile
      • Software Occlusion Culling
      • Platform Material Stats
      • Improve Mobile Specular Lighting Model





    I tested some of this stuff out and it's really great! I've several projects that have specular and it looks so much better now. The hardware Occlusion with ES3.1 works on mobile vr but only if you disable Multi-view. With multi-view on meshes that should be visible are only visible on certain angles. So it will depend on the project if this brings more gain than mutli-view.

    Did anyone create a bug for Epic to fix occlusion with multi-view yet?


    motorsepAuthor
    Inspiring
    July 30, 2018

    aussieburgerVR said:


    The hardware Occlusion with ES3.1 works on mobile vr but only if you disable Multi-view. With multi-view on meshes that should be visible are only visible on certain angles. So it will depend on the project if this brings more gain than mutli-view.

    Did anyone create a bug for Epic to fix occlusion with multi-view yet?




    Can't speak for the rest, but I haven't submitted anything since I haven't had a chance to test ES3.1 (it used to not work for me on Gear VR using S6).

    If I were you, I'd submit it to both Epic and Oculus. I can't imagine running mobile VR games without multiview.
    Anonymous
    August 1, 2018

    motorsep said:




    The hardware Occlusion with ES3.1 works on mobile vr but only if you disable Multi-view. With multi-view on meshes that should be visible are only visible on certain angles. So it will depend on the project if this brings more gain than mutli-view.

    Did anyone create a bug for Epic to fix occlusion with multi-view yet?




    Can't speak for the rest, but I haven't submitted anything since I haven't had a chance to test ES3.1 (it used to not work for me on Gear VR using S6).

    If I were you, I'd submit it to both Epic and Oculus. I can't imagine running mobile VR games without multiview.

    Bug ticket for Epic is public here:


    Please vote guys! ;) I think it's an Epic issue not Oculus since the same occurs on Daydream.

    FYI @motorsep : Did you try ES3.1 with 4.19 on your device to see if that works? My last tests with ES3.1 from 4.19 have it finally working for my projects at least

    motorsepAuthor
    Inspiring
    August 6, 2018
    @imperativity

    ^^ we have a breach here  :#
    Cykyria
    Participant
    August 22, 2018
    So I tried the 4.20 Oculus Github fork today and this is still happening. Was that fixed and I need to change some settings, or do we have to wait for 4.21?
    motorsepAuthor
    Inspiring
    August 22, 2018

    Cykyria said:

    So I tried the 4.20 Oculus Github fork today and this is still happening. Was that fixed and I need to change some settings, or do we have to wait for 4.21?


    What is still happening ?
    Show more replies
    Terms & ConditionsAccessibility statement