I disagree. I’ve been using an HMD (reverb g2) with head tracking for some time now and there’s no drop in fidelity that wouldn’t be overcome by the ability to move your head freely. I would go into more detail but I have a feeling we all have our preferences and reasons. I would recommend trying this if you have a HMD. I play using Virtual Desktop (not free) from Steam using the virtual fixed horizon curved 2d display that wraps around my entire FOV and OpenTrack for head tracking. Input is set to Valve SteamVR and Output is set to freetrack 2.0 Enhanced. Don’t forget to set your curves. It was at this point I realized I want a real 1-1 3d cockpit. It’s time.
Best posts made by thefalcone
-
RE: Not looking forward to the VR update
Latest posts made by thefalcone
-
RE: Not looking forward to the VR update
I disagree. I’ve been using an HMD (reverb g2) with head tracking for some time now and there’s no drop in fidelity that wouldn’t be overcome by the ability to move your head freely. I would go into more detail but I have a feeling we all have our preferences and reasons. I would recommend trying this if you have a HMD. I play using Virtual Desktop (not free) from Steam using the virtual fixed horizon curved 2d display that wraps around my entire FOV and OpenTrack for head tracking. Input is set to Valve SteamVR and Output is set to freetrack 2.0 Enhanced. Don’t forget to set your curves. It was at this point I realized I want a real 1-1 3d cockpit. It’s time.
-
RE: Bms launches in low resolution (not menu)
MS has been steadily moving away from the dynamic one size fits all development methodology to a more static but stable methodology. Well, they’re trying to move away anyway. The problem is MS is really good at providing legacy compatibility. So good in fact that if anything went wrong with an app Windows was able to automatically patch on the fly without the user noticing. It is likely that developers became too reliant on this “shim” architecture and why not? The code that worked yesterday still worked 10 years later. That is until MS started moving towards the stricter “windows app” methodology.
Since Windows 10, when MS started taking a hardline stance on encouraging (forcing) users to upgrade to the latest and greatest MS has been getting bitch slapped by the users and developers at every turn. They were pretty naieve to expect any other reaction. This is likely the reason that within one update everybodies FBMS resolution went to hell.
The old MS would have automatically provided a compatibility fix. The new MS snuck the per app “disable full screen optimization” fix in but chose not to apply it automatically. They can’t have it both ways. At least I hope they can’t.
*I wonder if it would be possible to launch the cockpit directly out of the BMS launcher via patch. It appears that the scaling transition from menu to cockpit at full screen is what is tripping up Windows 10.
-
RE: Cockpit resolution?
*update: I noticed forcing the game into windowed mode incurs a small performance hit. I doubt it would be noticed with decent hardware but it is noticable on my test laptop. I also tested with the “disable full screen optimization” setting enabled and I notice a similar FPS decrease. This isn’t a scientific benchmark by any means but for those using underpowered hardware it’s worth noting.
I took a slightly different approach to fix this although Xyzryo’s reply will likely solve the issue in 99% of the cases. It appears that because the FBMS menu renders at 1024x768 Windows then goes ahead and changes the desktop resolution (I’m assuming this is the full screen optimization feature) to 1024x768 which in turn causes the cockpit resolution to fall back to 1024x768. Most video card drivers have a display scaling option that will stretch 1024x768 to fill a 16x9 display and the result is not pretty.
To fix I first opened the “Cockpit Display Extraction” configuration tool. With the “Main” window radio button selected I unchecked the borders box and checked the enabled box. In my case I noticed that there was a strange value in the Left input field. I set all of these values to zero.
I also unchecked “Enabled” for the six other windows. If you don’t do this you will end up with six windows on top of the main window.
Unchecking the borders box stops the game from launching in full screen mode.
The menu will still render at 1024x768 but the cockpit will now render at the resolution configured in the Graphics setup menu.
Setting the game resolution to 1024x768 renders the cockpit similar to the way the menu is displayed but notice that it is not full screen and therefore no scaling occurs.
Setting the game resolution to your system’s native resolution (in my case 1920x1080) effectively renders the cockpit at 1920x1080, which fills my entire screen, and no scaling is required.