We are currently looking into this. Please keep in mind here, users in this specific thread here report actually two different issues, so don't mix this up please.
On our various Windows 10 test machines, we can simply start Aerofly RC 8 in VR mode by choosing the correct start option in the Windows program group. Aerofly RC 8 automatically loads the Oculus VR app and switches to VR mode.
Also when Windows Font scaling is active in Windows 10, we can properly choose fullscreen mode.
We just need to find out why Windows decides to run aerofly RC 8 in compatibility mode on a few customer machines.
Yes you are correct, there are a few extra issues mixed into this thread. Maybe because some like me think they may be interrelated. These seem to me to be;
- inability to change video resolution
- startup problems with Oculus Rift, and
- rc8 running in win8 compatibility mode
I'll try to briefly address each of these.
For me, I do not have any problems changing video resolutions between windowed and fullscreen. My default monitor setting is 1920x1080 (= 1080p). The only problem I have is that with my Oculus Rift the fullscreen setting is not remembered and I need to remind it by adjusting it in the startup settings view settings. If I do not do this then I cannot see the full RC8 menus later. For me, this is no big deal.
If you startup your pc without previously using Oculus Home then select the RC8 VR-mode shortcut (with -othervr in it's properties) then it all starts up fine. Albeit you may need to hit the space bar to centre your VR view. If you try to startup rc8 in VR when you have previously used another Oculus Rift app then it will crash. Also, if you try to use Oculus Home after exiting rc8 then you may get an error message saying that your Oculus Server is not connected. This is not big deal for me because Oculus will then restart and all will be fine (except for restarting rc8). I have found a workaround to this. After using Oculus home with your touch controllers you need to close the Oculus app, then bring up win10 task manager, go to services, right click on ovr runtime, select stop. After it is stopped, right click and start it again. then restart RC8 and all should be ok. Pretty simple, lol! I might as well also add that the audio switcher for RC8 does not work. If you want to hear sounds through your Rift headphones you need to select/change your Win10 taskbar audio setting from your PC speakers to your Rift headset prior to staring up rc8. Actually, I would not recommend doing this because the audio seems to very quickly go from both headphones to all right or left and this is kind of annoying. There does not seem to be any proper doppler effect like there is in other apps.
The Win8 compatibility issue seems to me to be a common problem with all tm.log files I have seen so far. I'm really not sure if this causes any other problems (like no Vulcan beta options) but in any case it should not be happening if rc8 has been designed for win10 to begin with. Hopefully this will get sorted out soon.
So, I will try not to mix these issues into this thread from now on and I will discuss my Oculus Rift VR startup issues in more detail later in my Oculus Startup Procedures thread. With a few current workarounds I am really enjoying RC8 in VR. Thanks Ikarus!
