Skip to main content
motorsep
Inspiring
January 9, 2018

[Gear VR / Oculus Go] Any optimizations or Vulkan, or ES 3.1 support coming to UE 4.19 / 4.20 ?

Since Oculus Go is about to be launched (assuming release time frame outlined in 2017 as "beginning of 2018" still stands) I am wondering if UE 4.19 (or 4.20) will get more optimizations / features enabled or get Vulkan (or ES 3.1) support for Gear VR and Oculus Go.

Thanks
This topic has been closed for replies.

14 replies

Show previous replies
RuptureGames
Up and Coming
November 10, 2018
@imperativity

is there any update on oculus go ES3.1 performance?  I'm in the process of migrating to UE4 4.21 from 4.20.  On 4.20 when I repackage with the Support ES3.1 toggle on I get some pretty patchy performance.  I have a steady 60 with no hitches on ES2,  in 3.1 I get huge slow down.  I don't know if this will be better in 4.21 but I'm currently looking into implementing World Position Offset vertex shader which isn't supported on ES2.  I'm doing this for tree/ foliage movement which is a very nice visual enhancement.  It's supposedly doable on ES3.1.  
Anonymous
November 19, 2018


@imperativity

is there any update on oculus go ES3.1 performance?  I'm in the process of migrating to UE4 4.21 from 4.20.  On 4.20 when I repackage with the Support ES3.1 toggle on I get some pretty patchy performance.  I have a steady 60 with no hitches on ES2,  in 3.1 I get huge slow down.  I don't know if this will be better in 4.21 but I'm currently looking into implementing World Position Offset vertex shader which isn't supported on ES2.  I'm doing this for tree/ foliage movement which is a very nice visual enhancement.  It's supposedly doable on ES3.1.  

 @r@RuptureGames
Epic did say they improved the performance of 3.1 in 4.21

Did you try the Emulated Uniform Buffers on Android command?:



You can now use Emulated Uniform Buffers for projects that target the OpenGL ES3.1 feature level, significantly reducing memory usage and improving rendering performance
depending on your application complexity. Emulated Uniform Buffers have
also been optimized to help reduce the size of the data that needs to
be transferred to the GPU when your project is being packaged. To enable
Emulated Uniform Buffers when using the OpenGL ES3.1 feature level, add
the following line to your project's DefaultEngine.ini under
[/Script/Engine.RendererSettings]:



[/Script/Engine.RendererSettings]

OpenGL.UseEmulatedUBs=1


Epic said this was the major problem with 3.1 performance that they fixed for Fortnite:

https://forums.unrealengine.com/development-discussion/android-development/1525990-emulated-uniform-buffers-explanation-from-the-fortnite-on-android-launch-technical-blog

My project was small enough not to have any 3.1 issues however would be interesting to know if this fixes the issue for your project!




motorsepAuthor
Inspiring
November 19, 2018

aussieburgerVR said:

 @r@RuptureGames
Epic did say they improved the performance of 3.1 in 4.21




Yes, they did. But improving GLES 3.1 for pancake isn't the same (at times) as improving it for VR.
Anonymous
November 20, 2018

motorsep said:


 @r@RuptureGames
Epic did say they improved the performance of 3.1 in 4.21




Yes, they did. But improving GLES 3.1 for pancake isn't the same (at times) as improving it for VR.


That's true but in 4.21 at least there have been some mobileVR 3.1 improvements. (see: hardware culling now working for multiview). I am also sure that the Emulated Uniform Buffers works for mobileVR as well since it has nothing to do with stereo rendering.

Anyway even more excited about the next unreal version for mobileVR as Epic hopefully includes their improvements to get Roborecall working nicely on the Quest!
Terms & ConditionsAccessibility statement