I’ve detected an issue which I can reproduce every time I try:
Specifications:
Windows 7 Ultimate 64 bit SP1 (updated).
Oculus Rift SDK 2.
Oculus Runtime 0.7.0.0.
Unreal 4.9.1.
Intel core i7 4790K.
16 GB RAM.
NVidia Geforce GTX 970. (drivers updated to 355.98).
I’ve been working until now with Unreal 4.7.6 and Oculus 0.5.0.0 because it was the only configuration I could got working. I’m perfoming some code writting and after attach a parent to an object NVidia drivers crash and restart, shutting down Unreal and the game in progress… So I decided to try (one more time) the newest engine version and the latest oculus runtime. So I create a demo of Realistic Rendering Scene in unreal 4.9.1. I switched to Standalone Game, everything worked properly, but when I pressed Alt + Enter to enter into VR mode, the screen went black and the window didn’t response… So I had to open task manager and kill that window manually. This ocurred everytime I tried like 16 times in a row.
After several tests, I’ve discovered that if I firstly open the console (~ + showlog), then I can switch to VR mode as suposed to do (Alt + enter) or typing the command in the console (~ + stereo on). I can’t figure out why if the log is showed up, VR works as it should and if it’s not showed, the whole application crashes :-S In a similar way, if I type ~ + fullscreen, VR mode switches to normal mode and the window doesn’t fit the whole screen…
I don’t know even if I could fix this weird issue, the drivers are going to work properly with my example in the last version…
Any tip, clue, idea? I know this seems kind of ridiculus…
Thank you in advance and if you need more information, please, don’t hesitate to ask me for it.
Best regards,
I am having the same problem. It seems that the only demos that work on the Oculus SDK 2 are the ones that were created using Unity. I have recently got to grips with Unreal engine in terms of lighting and importing geometry < I started on Unity a couple of years ago now but opted to switch to Unreal because of how realistic the lighting is and I don’t want to go back to the drawing board and start using Unity again.
I can not get any of the demos in Unreal to work. When I press Alt+Enter my screen flashes a couple of times and then the window minimizes. Even the Oculus template and couch knights don’t work.
Specifications:
Windows 7 Ultimate 64 bit SP1 (updated).
Oculus Rift SDK 2.
Oculus Runtime 0.7.0.0.
Unreal 4.9.1.
Intel core i7
64 GB RAM.
NVidia Geforce GTX 970. (drivers also updated to 355.98).
Sorry this has not been any help and I hope someone comes along soon and has a solution to our problems as it doesn’t come cheap, doing this sort of thing.
Thanks for the Tips Yesterday, I did try them. When I type “showlog” without quotes, for some reason I can’t type anything, I also don’t see any text at the top of the editor. I know the Oculus works because it works with
the Helix rollercoaster made in Unity,(Makes me feel sick but it works). Maybe I am missing something, I have The runtime installed and the SDK in a folder. it seems that for me Unreal doesn’t recognize the Oculus. Do you know of anything
else I may need to install.
Once again Thank you for taking the time to reply. P.S. the 64GB RAM is a works computer. my home computer is 16GB, wish I had more.
Oculus compatibility is embebed into Unreal Engine, the only thing you need to install is the Runtime. I belive the SDK is intended to make your own adaptations or use Oculus by yourself in your developments
“I can’t type anything” … so weird. Don’t forget to press ~ before typing and the input text box in balck and a cursor should appear at the bottom of the window. If you get the console shown, you have to know that is only for output, every command should be typed always in command line inside Unreal’s window.
NOTE: if you are using a non-english keyb, such a spanish or so (as I do), the key you have to press is the ‘º’, ‘ª’, ''] key, just below Esc key, to show the command line.
Here we have some kind of problem because, as I experienced before, if the runtime is not according to the unreal’s engine version, some issues can rise (as command not recognised or VR not working, for example, if you try to use runtime 5 with unreal 4.9.1 ). The more stable version of Unreal I’m using is 4.7.6, I strongly recommend you to try it. With this version, I’m using Oculus Runtime 0.5.0.1. If you want to use unreal engine v.4.9.1, you should use Oculus runtime 0.7.0.0. Check this out and tell me if everything is ok and we should think on this a bit deeper.
Thanks again for your advice on this matter, much appreciated :-). I have been in London For the Soluis exhibition on VR and AR at the building centre in London yesterday, hence not getting back to you.
however before I left for London I managed to get The Oculus working for all the Levels I have in unreal engine. I simply went back to the beginning and re-installed the run time on the Oculus website while leaving the Oculus plugged in.
I think my problem was, That I installed the runtime before plugging the Oculus in (USB’s first, Then the HDMI cable apparently this can be important). After I re-installed the run time 0.7.0.0. and tested it on a scene Play in VR and then hit Alt + Enter.
Hey presto everything working fine. I hope this helps you in some way.
