Forum Discussion
sbdykes
6 years agoExpert Protege
C++ asw::exceptions on library initialization
I've had native Oculus support in my project for quite some time, and things are working just fine. However, after upgrading to Windows 10 Pro, I've noticed that during the Oculus library initialization in my engine there are a dozen or so exceptions being generated, presumably from within the runtime itself (asw::exceptions::error). Now, it's worth noting that everything still seems to be functioning properly, but obviously exceptions are not something you want to have happening.
The further caveat to this is that I am using a DK2 dev kit/headset. So if the answer is "it's because the DK2 isn't officially supported anymore" that's fine. As I said, everything is actually functioning properly. But I would like to get to the bottom of the exceptions.
I've attached a text document that has the runtime debugger output for the initialization sequence, for both release and debug configurations.
Thanks!
No RepliesBe the first to reply
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
- 6 months ago