The 0.4.2 runtimes are unfortunately NOT compatible with the 0.4.1 integration that’s in 4.4.1. Please uninstall the 0.4.2 runtimes and reinstall the older runtimes if you want to use 4.4.1. The upcoming 4.5 release will be compatible with 0.4.2.
Please remember if you’re developing for UE4, you should check with which version the engine supports before upgrading your Oculus drivers. They’re early, and they are not always forward compatible with minor revisions.
Also, 0.4.1 wasn’t very performant in direct mode. The display driver had some issues, and Oculus recommends running in Extended mode with 0.4.1. 0.4.2 is much improved, but the display driver still has some issues with direct mode. This is NOT something we can fix at an engine level. Unfortunately, we need the updated display driver from Oculus. With the 0.4.2 integration, direct mode is more functional, but there are still some performance issues.
As for the tracking and monitor detection, cooked build or no cooked build shouldn’t make a difference. I’d try in extended mode to see if you get the same results. I tried a cooked build internally, and it worked here. Sounds like the plugin isn’t the problem if it was detecting and rendering in stereo in a windowed mode. You should just have to full screen it to have it pop to device.
Unforutnately, we were at the mercy of the 0.4.1 release, which has some issues internally which we cannot address. Things are much better with 0.4.2, but there are still some kinks in the direct mode driver. We’ve tried a preview of the later drivers, which are much more stable. Hopefully those will be released to everyone soon!
Are you experiencing any other bugs that we can investigate?