3440x1440 display sometimes loads, but not always
-
I’m trying to get this g-sync ultra wide monitor to display falcon in 3440x1440 100Hz. Sometimes the game will load, and display correctly, but mostly not - most always loads the game in the same size as the Falcon UI. Falcon is the only game where I’m having this problem. Is there a setting in the config file or something with FOV that I need to set so that 3440x1440 displays as desired? The monitor is a asus rog pg348q, graphic card is 1060 6MB on a ryzen 1800x with 32GB of ram. I’ve tried updating the graphic card drivers to the latest version 398.36 to no avail, and I’ve also tried configuring the Falcon exexcutable nvidea settings both configured or none - either way, makes no difference.
-
Heh… it’s not your graphics fault, I guess… It happened to me also on amd Rx580. I think something is wrong with setup with that ‘middle’ above fullHD resolution(s) (1440) , !, but, 3440x2160 works OK …
I tried to see what’s wrong… in resolutions file in …/art/… but I don’t know , they’ll have to check again I guess. I’m using fullHD 1080/1200 and happy
Cheers
-
Friend had the same issue a few days ago, on a regular 1080p monitor. It wouldn’t always load in 1080p, instead showing black bars left and right.
We fixed it by booting the executable from a shortcut with the -window addendum (so it looks like “C:\Falcon BMS 4.33U5\Launcher.exe” -window). In the Cockpit Display Extraction menu, make sure that borders are NOT enabled for the main screen.This will boot the 2D menu in 1024*768 resolution, but you’ll get full screen resolution when going into 3D. We assume it was probably some hickup when BMS needs to switch between the 2D and 3D resolution?
-
Thanks for the replies. Curious about running Falcon in a window, and will see if the manual explains how to configure accordingly. I would like to run Falcon in the monitor’s native 3D size - meaning 3400X1440, because it looks awesome to me. If there is something I’m missing in the replies I’ve read, please do clarify as it seems to me I’m not the only person having this sort of issue.
-
If you’re on Windows 10 have you tried going to the exe properties and disabling fullscreen optimizations? That’s in the compatibility tab.
-
eurybaric - I just tried making the change you suggest, but then I loose the jet as mouse cursor in the Falcon UI - good though though.
I tried adding -window as a parameter to the BMS desktop shortcut, can see window is confirmed in the BMS control panel. However, when launching Falcon into the 3D world, the display shifts down and to the right lower quadrant of the display, and can not be repositioned to center. I should also mention, that when Falcon is started after a system reboot, the game comes up in the 3D world, and displays properly for 3440X1440, but eventually reverts back to the issue on subsequent launches into the 3D world. I’ve also tried several other display settings in the Falcon graphics settings to no avail. Any other ideas I can try - appreciated.
-
I am using 3440x1440 gsync 90hz with no problem at all.
But my windows is still win7/64. -
when launching Falcon into the 3D world, the display shifts down and to the right lower quadrant of the display, and can not be repositioned to center.
Can you confirm that you have your options set like this? (you don’t need the -ef, that’s for EyeFly)
Shortcut:
Cockpit Display Extraction:
Falcon BMS.cfg:
set g_bUseExternalWindows 1 (not sure if this one is actually needed, but I have it like this)
set g_bCenterUI 0 // If set, the 2D UI in window mode will be centered horizontally and vertically on the desktop (e.g. for triple screen users)Like this, it should load the 2D UI in the top left corner, then load the 3D in full screen.
-
Use the “display extractor” accessible from the launcher. Remove borders and set window position to (0, 0) origin.
-
I also have a 3440x1440 display from samsung with a GeForce MSI 1070 and had no problems.
I use the RTTClient/RTTServer as display extraction and I think with fullscreen (not windowed).
-
Eagle-Eye and sthalik - YES, a positive result. Making your suggested setting changes for the Falcon BMS shortcut, display extractor, and config file solved the problem. Additionally, I had to change Window 10 display "scale and layout from 125% to 100%. For regular use, the display scale of %125 is preferable. QUESTION: Is there a way to set the display scale to %100 just for Falcon BMS in the Nvidea Control Panel or something?
Thanks! -
Nope , it is windows thing, but, you can try right-click bms exe or shortcut , click properties , then under compatibility tab down near the bottom is “Change High DPI settings” , there, again at the bottom, select by “Override by Application” !not ‘system/enhanced’.
That should put BMS in control of DPI , which is responsible for display scaling…
I use it that way… because my monitor is UHD(4k) and using 125% scaling which is adequate.
Does this work ?? … I honestly don’t know , I think NOT … eh, win10, what can you do … but you can try and see.
-
Thanks white_fang - actually, the changes you suggest I try out did a treat. I’m all set - thank you all for helping me solve this issue.
-
WEll then … glad it did it for 'ya. … The reason why I was suspicious in the first place is when I activate that setting , it changes my radio and menu fonts … so it is noticeable , but does it work as advertised… I can’t tell.
I also use gpu-scaling on all my monitors via driver/amd-settings, to a ‘full-panel’ or ‘preserve-aspect’ , but that is pure hardware (gpu) … so that also influences picture stretching (enlarging) or enforces default resolution in preserve-aspect mode. Anyways.
Great! . Cheers
-
Additionally, I had to change Window 10 display "scale and layout from 125% to 100%.
Thanks!Double-click the “Falcon BMS.exe” executable, set compatibility options, select DPI status managed by application (not system nor system enhanced).
edit: white_fang got the correct answer. Just remember to do it on “Falcon BMS.exe”.
-
Thanks for the clarification - I did make the DPI scaling change to the “Falcon BMS.exe” executable.
-
As it turns out, windows mode was not necessary. I also turned off windows for the instruments display in “cockpit display extraction”, because each individual window, for a given cockpit instrument, was appearing I could see before entering into the main 3D world. What solved the original issue was setting the “Falcon BMS.exe” compatibility for DPI status management. I think the issue is that I have the windows scaling set to %125 for other than Falcon BMS. So the compatibility for managing the DPI scaling to “application” for the executable is the solution.