Skip to main content
August 9, 2017

[GearVR] 3D widget performance degregation in 4.17

There appears to be a oculus gearvr related issue in 4.17 involving 3D widget performance / rendering. 
It would be great if someone from oculus could take a look because this issue does not occur on daydream and renders 4.17 useless: https://answers.unrealengine.com/questions/664617/gearvr-3d-widget-performance-degregation-in-417-pr.html
This topic has been closed for replies.

16 replies

Inspiring
September 15, 2017
@aussieburgerVR

How did the test go with real app ? (debug and shipping builds)
September 16, 2017
While it does make the game playable it is far from ideal. It obviously only works if there's nothing on the widget you wish to update more often than a second and there is still small a random hitch every few seconds or so. So this "workaround" will only be bearable for certain projects.

Unrelated to the topic but why it took so long to reply:
To make matters worse it's getting very difficult for me to test as I currently constantly get this with my device:

"Check mobile device is properly inserted into Gear VR"

It had been getting worse and worse with my device and now it takes about 5-10 attempts before anything gearvr starts up - it seems all the constant taking phone in and out of the headset has warped the connector of the phone :(

Seems a common problem:
https://forums.oculus.com/community/discussion/51613/gear-vr-will-not-load
https://forums.unrealengine.com/development-discussion/vr-ar-development/1349669-gearvr-error-unable-to-use-gear-vr-check-mobile-device-properly-inserted-in-gear-vr
https://forums.oculus.com/community/discussion/36104/how-to-fix-gear-vr-not-launching-when-phone-is-plugged-in/p3




New Participant
September 23, 2017
This issue is also not fixed in Unreal 4.18 preview.
Inspiring
September 25, 2017

redhill71 said:

This issue is also not fixed in Unreal 4.18 preview.


That's because the fix is slated for 4.19 (if they don't forget about it by then)
New Participant
October 6, 2017
Fortunately, this issue has been fixed in 4.18.0 Preview 2 or Preview 3. :)
October 9, 2017
Just curious, does anyone know which GitHub commit contains the fix?