I’ve been running into an odd issue that I’m unable to replicate when running in-editor.
From what I understand, Oculus recently (with CV1 i think) added the ability for the headset to go put itself to sleep after a certain period of inactivity.
I found that when leaving my packaged UE4 game idle with Oculus sitting on my desk that the game will crash and bring up the error reporting screen when the Oculus decides to go idle. (It also causes some full desktop graphical issues like flickering and the like sometimes)
This behaviour isn’t shown in editor. In editor, it seems as the game thread properly pauses and resumes when activity is detected on the headset.
Is this a known issue or is there something that I am doing incorrectly from my end?
I just ran a test with this and didn’t get a crash with the Oculus retail kit I have at my desk. I created just a simple packaged default level and let the Oculus go to sleep. I did see that the screen froze, but that was only until I used the remote to wake the headset back up from the sleep screen. After this everything returned to normal and worked for the level. I also did not see any additional issue with my Desktop and flickering.
I may need the following to proceed:
Can you grab the logs from the packaged project and upload the text file here. (Project Packaged Folder > project Name > Saved > Logs)
If you create a basic project packaged and try do you see the same result, or only with your project?
I think I’ve isolated the issue. I’m running multiple threads and I believe that it’s building up a data queue while idle that’s not getting cleared due to the oculus pausing the main tick threads.
So follow up question: is there a way to detect if the main threads are paused so I can pause my background threads?