Forum Discussion
Oculus SDK for Windows 1.10.0 Released
Oculus PC SDK 1.10.0
New Features
- Enabled ASW by default. For more information, see Asynchronous SpaceWarp.
- Added Touch optimizations.
- Minor performance improvements, memory management fixes, and other updates.
Known Issues
- If you encounter intermittent tracking issues, remove the batteries from any Engineering Sample Oculus Remotes that you paired with your headset and contact Developer Relations for replacement remotes.
- If you bypass the shim and communicate with the DLL directly, without specifying a version to ovr_Initialize, the DLL has no way of knowing the SDK version with which the application was built. This can result in unpredictable or erratic behavior which might cause the application to crash.
- There are some USB chipsets that do not meet the USB 3.0 specification and are incompatible with the Oculus Rift sensor. If you receive a notification in Oculus Home or the Oculus App, plug the sensor into a different USB 3.0 port (blue). If none of the USB 3.0 ports work, plug the sensor into a USB 2.0 port (black).
- Antivirus software, such a McAfee, can cause installation issues. To work around the issue, make sure you have the latest updates and disable real-time scanning.
- If you encounter installation issues, delete the Oculus folder and install the software again.
- If the Rift displays a message that instructs you to take off the headset, remove it and place it on a flat surface for 10-15 seconds.
- The keyboard and mouse do not work in Oculus Home. To select an item, gaze at it and select it using the Oculus Remote or Xbox controller.
- Bandwidth-intensive USB devices, such as web cams and high-end audio interfaces, might not work when using the Rift. To work around this issue, install the device on another USB host controller or a separate computer.
- For dual-boot systems using DK2 or CB1 HMDs, the OS selection screen might appear on the HMD instead of the monitor. To work around this, try plugging the HMD into a different port or unplug the HMD while booting.
- If you are running your application from the Unity Editor and you press the controller's home button to return to Oculus Home, you will be prompted to close the application. If you select OK, Unity might remain in a state where it is running, but will never get focus. To work around this, restart Unity.
6 Replies
- With 1.10 release we are not able to link with libovr.lib anymore:
ibovr.lib(OVR_CAPI_Util.obj) : error LNK2038: mismatch detected for 'RuntimeLibrary': value 'MT_StaticRelease' doesn't match value 'MD_DynamicRelease' in <OurDLL>.obj
Is there is a plan to provide different libs for /MT /MD flags?
Thanks!
QaUnigine said:
Is there is a plan to provide different libs for /MT /MD flags?
The lib ovr is fully sourced with the project, you can build your own, i personally rebuild them when i upgrade a sdk too.
I had the error too btw, they also turned off exception and it had warnings while compiling the lib. I think they did that for the C operop mode. They should have add new target config instead of screwing up the existing ones…- The provided VS 2015 projects for libovr and libovrKernel don't even compile. Probably not difficult to fix, but it shakes my confidence in the 1.10 version. Nothing seems to fit together with it. I won't adapt my projects to 1.10 and hope for a fixed version before Touch release.
- They compile for me no problem. It may be something with your configuration.
cybereality said:
They compile for me no problem. It may be something with your configuration.
@cybereality They compile, but new warnings ( at least in vs 2015 ) because you disabled the exceptions and changed the default runtime library ( from dll to static ).
I don't care much personally because it is a small library and i integrate the new version merging over a local depot. But i understand why developers can be pissed off with breaking changes like that.
The changes you made that broke people is in regards to supporting a C project. It seems to be a request for some developers and why not, but in that case, Oculus should introduce alternative compilation target instead of changing the existing ones ( To be honest, you should from the beginning provide targets for every flavor of runtime library, it is not right from Oculus to enforce the choice here ).
cybereality said:
They compile for me no problem. It may be something with your configuration.
Indeed. I forgot to set Target Platform Version to Win 10 SDK. After that it compiled. Sorry for that. :(
For all who might still have the problem: Open the LibOVR project, go to All Options / Runtime Library and set /MD. I had to do this both for the debug and release version, where I could just use the release version of LibOVR also for the debug version of my project with older SDK versions.
