Forum Discussion
PhilipRamirez
11 years agoHonored Guest
Changing Anti-Aliasing during runtime causes crashes
Hello everyone! This forum has been an immense help to me as I've been developing with the Oculus. Recently though I've run into a problem I don't know how to fix and I didn't see anything about it on the forums. Time to start my own thread!
As the subject heavily implies, I'm having troubles changing the Anti-Aliasing setting in Unity while in a build which immediately crashes the program. I've tested this in a clean Tuscany scene and sure enough the problem persists. I've noticed that the crashes only happens when I launch the build through the DirectToRift.exe.
This is in Unity version: 4.5.2.
Oculus version: 4.3
Build: Windows 32-bit
And here is a little snippet from the error.log file:
OVRDisplayRT32.dll caused an Access Violation (0xc0000005)
in module OVRDisplayRT32.dll at 0023:66334b56.
As the subject heavily implies, I'm having troubles changing the Anti-Aliasing setting in Unity while in a build which immediately crashes the program. I've tested this in a clean Tuscany scene and sure enough the problem persists. I've noticed that the crashes only happens when I launch the build through the DirectToRift.exe.
This is in Unity version: 4.5.2.
Oculus version: 4.3
Build: Windows 32-bit
And here is a little snippet from the error.log file:
OVRDisplayRT32.dll caused an Access Violation (0xc0000005)
in module OVRDisplayRT32.dll at 0023:66334b56.
2 Replies
Replies have been turned off for this discussion
- PhilipRamirezHonored GuestAlso, Dx11 is the rendering mode.
- vrdavebOculus StaffI've filed a bug on this. For now, can you avoid changing the AA mode until after OVRManager has been set up or use extended mode?
Quick Links
- Horizon Developer Support
- Quest User Forums
- Troubleshooting Forum for problems with a game or app
- Quest Support for problems with your device
Other Meta Support
Related Content
- 3 years ago
- 4 years ago