While doing IO intensive operations (loading) Unity tends to freeze when run from editor mode with a Vive hooked up. I.e. when the vive goes into background mode because you are skipping frames (or whatever that is)
Has anyone else experienced this?
It crashes over and over again at times, and at other times it works flawlessly for long periods of time (across many start stops). At first I thought that it was something overheating, but it occurs across many machines and many Vives even right after the machine has been off for a long period of time
It only happens near the beginning of a session.
I haven’t been able to nail down what exactly causes the crashes, but I am looking for patterns.
When I run Standalone it does not crash or report errors.
Granted I am using a beta, so I am hoping that it will go away with the final, but for now I would love to find any techniques to reduce the crashes.
I’ve been getting a lot of crashes in beta 5.4 with the vive and now even with the f3 release. It’s annoying because I haven’t been able to track down what’s causing it. The editor just goes away. I can’t get much out of the log other than access violation. I never saw this much crashing with 5.3.
Can either of you provide a small repro project? If so, please submit a bug report and post the case number here. Then I can take a closer look at some potential causes of this issue.
Additionally, I have seen some crashes with Vive/OpenVR and DX12 API. So make sure that the default graphics API is set to DX11.
