Can't start FG - new monitor

[Avionyx]

Hi All,

I got a new monitor last week and despite uninstalling FG completely, making sure my ini file was cleared and reinstalling the graphics drivers I can't get Fg to start at all. I just get a blank white screen and the following in the log:

22.87 [ALRT]:view C:\Jenkins\workspace\Windows-nightly\flightgear\src\Viewer\fg_os_osgviewer.cxx:448: affinity=
22.87 [INFO]:view C:\Jenkins\workspace\Windows-nightly\flightgear\src\Viewer\renderer.cxx:791: FGRenderer:: Maximum texture size 32768
22.87 [INFO]:general C:\Jenkins\workspace\Windows-nightly\flightgear\src\GUI\gui.cxx:135: NVIDIA Corporation
22.87 [INFO]:general C:\Jenkins\workspace\Windows-nightly\flightgear\src\GUI\gui.cxx:138: NVIDIA GeForce RTX 3080/PCIe/SSE2
22.87 [INFO]:general C:\Jenkins\workspace\Windows-nightly\flightgear\src\GUI\gui.cxx:141: 4.6.0 NVIDIA 526.98
22.87 [INFO]:general C:\Jenkins\workspace\Windows-nightly\flightgear\src\GUI\gui.cxx:151: 4.60 NVIDIA
22.87 [INFO]:general C:\Jenkins\workspace\Windows-nightly\flightgear\src\GUI\gui.cxx:165: VertexAttribDivisor supported

I'm presuming it's because it's a widescreen monitor? I've had no issue with anything else on the PC it's just FG left to sort out so any help would be greatly appreciated.

Alex

[wkitty42]

what do you mean by "making sure [your] ini file was cleared"? which one?

maybe also try deleting the autosave_xxxx.xml file...

then there's also the setting(s) in the launcher for the video and resolution...

are you trying to run it full screen or in a window?

do you have only the one monitor, now, or are you trying to run with both connected?

lastly, try running FG from the command line like this "fgfs --launcher --log-level=debug"... this will print some output to the terminal window you started it in... when you exit, it may provide more information that you can copy'n'paste here... the log file should also have more info, too...

[Avionyx]

Hi there,

I appreciate the reply.

I run with 3 monitors, I've replaced the central "main" monitor so am running the same setup just with a different central monitor at a different resolution. I only run FG on the central monitor - no fancy dual setups when it comes to FG.

So far I've deleted the ini in my C:\Users\[user]\AppData\Roaming\flightgear.org\FlightGear folder.
I've also set the video>resolution settings in the launcher. However FG doesn't give me the option to select the correct resolution for my monitor so I've selected various ones in there for windowed as well as full screen but it seems to make no difference.

I was previously running with debug enabled for the logging and the output again is the same as in my first post, almost exactly.

Here's the full dump:

Code: Select all

    0.00 [INFO]:general   C:\Jenkins\workspace\Windows-nightly\flightgear\src\Main\fg_init.cxx:566: Created multi-app mutex, we are in writeable mode
    0.00 [INFO]:general   C:\Jenkins\workspace\Windows-nightly\flightgear\src\Main\main.cxx:633: FlightGear:  Version 2020.4.0
    0.00 [INFO]:general   C:\Jenkins\workspace\Windows-nightly\flightgear\src\Main\main.cxx:634: FlightGear:  Build Type Nightly
    0.00 [INFO]:general   C:\Jenkins\workspace\Windows-nightly\flightgear\src\Main\main.cxx:635: Built with Microsoft Visual C++ version 1926
    0.00 [INFO]:general   C:\Jenkins\workspace\Windows-nightly\flightgear\src\Main\main.cxx:637: Jenkins number/ID 4399:4399
    0.00 [DBUG]:general   C:\Jenkins\workspace\Windows-nightly\flightgear\src\Main\fg_props.cxx:209: Logging priority is debug
    0.00 [INFO]:general   C:\Jenkins\workspace\Windows-nightly\flightgear\src\Main\options.cxx:3188: platform default fg_root = Path "../data"
    0.00 [DBUG]:general   C:\Jenkins\workspace\Windows-nightly\flightgear\src\Main\fg_init.cxx:737: Reading global defaults
    0.01 [DBUG]:general   C:\Jenkins\workspace\Windows-nightly\flightgear\src\Main\fg_init.cxx:753: Finished Reading global defaults
    0.24 [INFO]:navaid    C:\Jenkins\workspace\Windows-nightly\flightgear\src\Navaids\NavDataCache.cxx:297: NavCache at:Path "C:/Users/nethe/AppData/Roaming/flightgear.org/navdata_2020_4.cache"
    0.24 [INFO]:navaid    C:\Jenkins\workspace\Windows-nightly\flightgear\src\Navaids\NavDataCache.cxx:300: NavCache read-only flags is:0
    0.24 [DBUG]:navaid    C:\Jenkins\workspace\Windows-nightly\flightgear\src\Navaids\NavDataCache.cxx:1104: NavCache: no rebuild required for Path "X:/FlightGear 2020.4/data/Airports/apt.dat.gz"
    0.25 [DBUG]:navaid    C:\Jenkins\workspace\Windows-nightly\flightgear\src\Navaids\NavDataCache.cxx:1255: NavCache: no rebuild required for apt.dat files
    0.25 [DBUG]:navaid    C:\Jenkins\workspace\Windows-nightly\flightgear\src\Navaids\NavDataCache.cxx:1104: NavCache: no rebuild required for Path "X:/FlightGear 2020.4/data/Airports/metar.dat.gz"
    0.25 [DBUG]:navaid    C:\Jenkins\workspace\Windows-nightly\flightgear\src\Navaids\NavDataCache.cxx:1104: NavCache: no rebuild required for Path "X:/FlightGear 2020.4/data/Navaids/nav.dat.gz"
    0.25 [DBUG]:navaid    C:\Jenkins\workspace\Windows-nightly\flightgear\src\Navaids\NavDataCache.cxx:1255: NavCache: no rebuild required for nav.dat files
    0.25 [DBUG]:navaid    C:\Jenkins\workspace\Windows-nightly\flightgear\src\Navaids\NavDataCache.cxx:1104: NavCache: no rebuild required for Path "X:/FlightGear 2020.4/data/Navaids/fix.dat.gz"
    0.25 [DBUG]:navaid    C:\Jenkins\workspace\Windows-nightly\flightgear\src\Navaids\NavDataCache.cxx:1255: NavCache: no rebuild required for fix.dat files
    0.25 [DBUG]:navaid    C:\Jenkins\workspace\Windows-nightly\flightgear\src\Navaids\NavDataCache.cxx:1104: NavCache: no rebuild required for Path "X:/FlightGear 2020.4/data/Navaids/carrier_nav.dat.gz"
    0.25 [DBUG]:navaid    C:\Jenkins\workspace\Windows-nightly\flightgear\src\Navaids\NavDataCache.cxx:1104: NavCache: no rebuild required for Path "X:/FlightGear 2020.4/data/Navaids/poi.dat.gz"
    0.25 [DBUG]:navaid    C:\Jenkins\workspace\Windows-nightly\flightgear\src\Navaids\NavDataCache.cxx:1104: NavCache: no rebuild required for Path "X:/FlightGear 2020.4/data/Navaids/awy.dat.gz"
    0.25 [INFO]:navaid    C:\Jenkins\workspace\Windows-nightly\flightgear\src\Navaids\NavDataCache.cxx:1449: NavCache: no main cache rebuild required
    0.25 [INFO]:general   C:\Jenkins\workspace\Windows-nightly\flightgear\src\Main\fg_init.cxx:1485: init package root at:Path "C:/Users/nethe/FlightGear/Downloads/Aircraft"
    0.28 [DBUG]:general   C:\Jenkins\workspace\Windows-nightly\simgear\simgear\package\Catalog.cxx:213: creating catalog from:Path "C:/Users/nethe/FlightGear/Downloads/Aircraft/org.flightgear.fgaddon.trunk"
    0.29 [INFO]:general   C:\Jenkins\workspace\Windows-nightly\flightgear\src\Main\locale.cxx:127: User langauge 0:en-US
    0.29 [DBUG]:general   C:\Jenkins\workspace\Windows-nightly\flightgear\src\Main\locale.cxx:220: Trying to find locale for 'English'
    0.29 [DBUG]:general   C:\Jenkins\workspace\Windows-nightly\flightgear\src\Main\locale.cxx:165: Searching language resource for locale: 'English'
    0.29 [DBUG]:general   C:\Jenkins\workspace\Windows-nightly\flightgear\src\Main\locale.cxx:220: Trying to find locale for 'en-US'
    0.29 [DBUG]:general   C:\Jenkins\workspace\Windows-nightly\flightgear\src\Main\locale.cxx:165: Searching language resource for locale: 'en-US'
    0.29 [DBUG]:general   C:\Jenkins\workspace\Windows-nightly\flightgear\src\Main\locale.cxx:165: Searching language resource for locale: 'en'
    0.29 [INFO]:general   C:\Jenkins\workspace\Windows-nightly\flightgear\src\Main\locale.cxx:177: Found language resource for: en
    0.29 [DBUG]:general   C:\Jenkins\workspace\Windows-nightly\flightgear\src\Main\locale.cxx:226: Found locale for 'en-US' at '/sim[0]/intl[0]/locale[0]'
    0.29 [INFO]:general   C:\Jenkins\workspace\Windows-nightly\flightgear\src\Main\locale.cxx:329: Reading localized strings for 'en' from Path "X:/FlightGear 2020.4/data/Translations/default/sys.xml"
    0.29 [INFO]:general   C:\Jenkins\workspace\Windows-nightly\flightgear\src\Main\locale.cxx:329: Reading localized strings for 'en' from Path "X:/FlightGear 2020.4/data/Translations/default/atc.xml"
    0.29 [INFO]:general   C:\Jenkins\workspace\Windows-nightly\flightgear\src\Main\locale.cxx:329: Reading localized strings for 'en' from Path "X:/FlightGear 2020.4/data/Translations/default/tips.xml"
    0.29 [INFO]:general   C:\Jenkins\workspace\Windows-nightly\flightgear\src\Main\locale.cxx:329: Reading localized strings for 'en' from Path "X:/FlightGear 2020.4/data/Translations/default/weather-scenarios.xml"
    0.29 [DBUG]:general   C:\Jenkins\workspace\Windows-nightly\simgear\simgear\structure\subsystem_mgr.cxx:1059: Adding subsystem http
    0.45 [DBUG]:gui       :0: Restored default aircraft: QUrl("file:///X:/FlightGear 2020.4/data/Aircraft/c172p/c172p-set.xml")
    2.44 [DBUG]:io        C:\Jenkins\workspace\Windows-nightly\simgear\simgear\io\HTTPClient.cxx:214: msg->data.result=0
    6.79 [DBUG]:general   C:\Jenkins\workspace\Windows-nightly\flightgear\src\Airports\airport.cxx:672: FGAirport::processThreshold: found runway not defined in the global data:PHTO/3
    6.79 [DBUG]:general   C:\Jenkins\workspace\Windows-nightly\flightgear\src\Airports\airport.cxx:672: FGAirport::processThreshold: found runway not defined in the global data:PHTO/8
    7.89 [DBUG]:navaid    C:\Jenkins\workspace\Windows-nightly\flightgear\src\Airports\xmlloader.cxx:53: reading groundnet data from Path "C:/Users/nethe/FlightGear/Downloads/TerraSync/Airports/B/I/K/BIKF.groundnet.xml"
    7.90 [DBUG]:navaid    C:\Jenkins\workspace\Windows-nightly\flightgear\src\Airports\xmlloader.cxx:68: parsing groundnet XML took 6
   27.90 [WARN]:general   C:\Jenkins\workspace\Windows-nightly\flightgear\src\Main\globals.cxx:501: aircraft path not found:Path "C:/Users/nethe/FlightGear/Downloads/Aircraft/org.flightgear.fgaddon.trunk/Aircraft"
   27.90 [DBUG]:general   C:\Jenkins\workspace\Windows-nightly\simgear\simgear\structure\subsystem_mgr.cxx:1059: Adding subsystem error-reporting
   27.90 [INFO]:input     C:\Jenkins\workspace\Windows-nightly\flightgear\src\Main\options.cxx:2415: aircraft = c172p
   27.90 [INFO]:general   C:\Jenkins\workspace\Windows-nightly\flightgear\src\Main\fg_init.cxx:242: found aircraft in dir: X:/FlightGear 2020.4/data/Aircraft/c172p
   27.93 [DBUG]:general   C:\Jenkins\workspace\Windows-nightly\flightgear\src\Add-ons\AddonManager.cxx:71: Initializing the AddonManager
   27.93 [INFO]:general   C:\Jenkins\workspace\Windows-nightly\flightgear\src\Main\locale.cxx:127: User langauge 0:en-US
   27.93 [DBUG]:general   C:\Jenkins\workspace\Windows-nightly\flightgear\src\Main\locale.cxx:220: Trying to find locale for 'en-US'
   27.93 [DBUG]:general   C:\Jenkins\workspace\Windows-nightly\flightgear\src\Main\locale.cxx:165: Searching language resource for locale: 'en-US'
   27.93 [DBUG]:general   C:\Jenkins\workspace\Windows-nightly\flightgear\src\Main\locale.cxx:165: Searching language resource for locale: 'en'
   27.93 [INFO]:general   C:\Jenkins\workspace\Windows-nightly\flightgear\src\Main\locale.cxx:177: Found language resource for: en
   27.93 [DBUG]:general   C:\Jenkins\workspace\Windows-nightly\flightgear\src\Main\locale.cxx:226: Found locale for 'en-US' at '/sim[0]/intl[0]/locale[0]'
   27.93 [INFO]:general   C:\Jenkins\workspace\Windows-nightly\flightgear\src\Main\options.cxx:2756:    option:prop = /nasal/local_weather/enabled=false
   27.94 [INFO]:general   C:\Jenkins\workspace\Windows-nightly\flightgear\src\Main\options.cxx:2756:    option:metar = XXXX 012345Z 15003KT 19SM FEW072 FEW350 25/07 Q1028 NOSIG
   27.94 [INFO]:general   C:\Jenkins\workspace\Windows-nightly\flightgear\src\Main\options.cxx:2756:    option:prop = /environment/weather-scenario=Core high pressure region
   27.94 [INFO]:general   C:\Jenkins\workspace\Windows-nightly\flightgear\src\Main\options.cxx:2756:    option:prop = /sim/rendering/texture-cache/cache-enabled=false
   27.94 [INFO]:general   C:\Jenkins\workspace\Windows-nightly\flightgear\src\Main\options.cxx:2756:    option:enable-fullscreen =
   27.94 [INFO]:general   C:\Jenkins\workspace\Windows-nightly\flightgear\src\Main\options.cxx:2756:    option:disable-terrasync =
   27.94 [INFO]:general   C:\Jenkins\workspace\Windows-nightly\flightgear\src\Main\options.cxx:2756:    option:enable-sentry =
   27.94 [INFO]:general   C:\Jenkins\workspace\Windows-nightly\flightgear\src\Main\options.cxx:2756:    option:aircraft-dir = X:/FlightGear 2020.4/data/Aircraft/c172p
   27.94 [INFO]:general   C:\Jenkins\workspace\Windows-nightly\flightgear\src\Main\options.cxx:2756:    option:aircraft = c172p
   27.94 [INFO]:general   C:\Jenkins\workspace\Windows-nightly\flightgear\src\Main\options.cxx:2756:    option:airport = BIKF
   27.94 [INFO]:general   C:\Jenkins\workspace\Windows-nightly\flightgear\src\Main\options.cxx:2756:    option:parking-id = AVAILABLE
   27.94 [INFO]:general   C:\Jenkins\workspace\Windows-nightly\flightgear\src\Main\options.cxx:2756:    option:fg-aircraft = C:/Users/nethe/FlightGear/Downloads/Aircraft/org.flightgear.fgaddon.trunk/Aircraft
   27.94 [INFO]:general   C:\Jenkins\workspace\Windows-nightly\flightgear\src\Main\options.cxx:2756:    option:launcher =
   27.94 [DBUG]:general   C:\Jenkins\workspace\Windows-nightly\flightgear\src\Main\fg_props.cxx:209: Logging priority is debug
   27.94 [INFO]:general   C:\Jenkins\workspace\Windows-nightly\flightgear\src\Main\options.cxx:2756:    option:log-level = debug
   27.94 [INFO]:general   C:\Jenkins\workspace\Windows-nightly\flightgear\src\Main\options.cxx:2780: Using default download dir: Path "C:/Users/nethe/FlightGear/Downloads"
   27.94 [DBUG]:io        C:\Jenkins\workspace\Windows-nightly\flightgear\src\Main\globals.cxx:425: read-allowed path not found:Path "C:/Users/nethe/FlightGear/Downloads/AI"
   27.94 [DBUG]:io        C:\Jenkins\workspace\Windows-nightly\flightgear\src\Main\globals.cxx:425: read-allowed path not found:Path "C:/Users/nethe/FlightGear/Downloads/Liveries"
   27.94 [INFO]:general   C:\Jenkins\workspace\Windows-nightly\flightgear\src\Main\options.cxx:2803: Using default texture cache directory: Path "C:/Users/nethe/FlightGear/Downloads/TextureCache"
   27.94 [INFO]:general   C:\Jenkins\workspace\Windows-nightly\flightgear\src\Main\options.cxx:2826: Using TerraSync dir: Path "C:/Users/nethe/FlightGear/Downloads/TerraSync"
   27.94 [INFO]:general   C:\Jenkins\workspace\Windows-nightly\flightgear\src\Main\main.cxx:742: EmbeddedResourceManager: selected locale 'en-US'
   27.94 [DBUG]:general   C:\Jenkins\workspace\Windows-nightly\simgear\simgear\structure\subsystem_mgr.cxx:1059: Adding subsystem graphics-presets
   27.94 [ALRT]:view      C:\Jenkins\workspace\Windows-nightly\flightgear\src\Viewer\renderer.cxx:476: Creating osgViewer::CompositeViewer
   27.94 [ALRT]:general   C:\Jenkins\workspace\Windows-nightly\flightgear\src\Viewer\renderer.cxx:483: affinity=
   27.94 [ALRT]:view      C:\Jenkins\workspace\Windows-nightly\flightgear\src\Viewer\renderer.cxx:495: Calling composite_viewer->setUseConfigureAffinity() with flag=1
   27.94 [INFO]:astro     C:\Jenkins\workspace\Windows-nightly\simgear\simgear\scene\sky\cloud.cxx:342: initializing cloud layers
   27.96 [DBUG]:view      C:\Jenkins\workspace\Windows-nightly\flightgear\src\Viewer\fg_os_osgviewer.cxx:208: Using CompositeViewer
   27.96 [DBUG]:view      C:\Jenkins\workspace\Windows-nightly\flightgear\src\Viewer\fg_os_osgviewer.cxx:210: Creating osgViewer::View
   27.96 [DBUG]:view      C:\Jenkins\workspace\Windows-nightly\flightgear\src\Viewer\renderer.cxx:1104: adding view to composite_viewer.
   27.96 [INFO]:view      C:\Jenkins\workspace\Windows-nightly\flightgear\src\Viewer\fg_os_osgviewer.cxx:225: mode=SingleThreaded
   27.97 [DBUG]:view      C:\Jenkins\workspace\Windows-nightly\flightgear\src\Viewer\WindowBuilder.cxx:114: Using full screen size for window: 1920 x 1080
   28.00 [DBUG]:general   C:\Jenkins\workspace\Windows-nightly\flightgear\src\Viewer\WindowBuilder.cxx:241: Changing defaultWindowName from FlightGear to FlightGear
   28.00 [WARN]:general   C:\Jenkins\workspace\Windows-nightly\flightgear\src\Main\main.cxx:781: Enabling ATI/AMD viewport hack
   28.00 [INFO]:general   C:\Jenkins\workspace\Windows-nightly\flightgear\src\Main\fg_init.cxx:964: Configuration State
   28.00 [INFO]:general   C:\Jenkins\workspace\Windows-nightly\flightgear\src\Main\fg_init.cxx:965: ============= =====
   28.00 [INFO]:general   C:\Jenkins\workspace\Windows-nightly\flightgear\src\Main\fg_init.cxx:967: aircraft-dir = "X:/FlightGear 2020.4/data/Aircraft/c172p"
   28.01 [INFO]:general   C:\Jenkins\workspace\Windows-nightly\flightgear\src\Main\fg_init.cxx:968: fghome-dir = "Path "C:/Users/nethe/AppData/Roaming/flightgear.org""
   28.01 [INFO]:general   C:\Jenkins\workspace\Windows-nightly\flightgear\src\Main\fg_init.cxx:969: download-dir = "C:/Users/nethe/FlightGear/Downloads"
   28.01 [INFO]:general   C:\Jenkins\workspace\Windows-nightly\flightgear\src\Main\fg_init.cxx:970: terrasync-dir = "C:/Users/nethe/FlightGear/Downloads/TerraSync"
   28.01 [INFO]:general   C:\Jenkins\workspace\Windows-nightly\flightgear\src\Main\fg_init.cxx:972: aircraft-search-paths =
   
   28.01 [INFO]:general   C:\Jenkins\workspace\Windows-nightly\flightgear\src\Main\fg_init.cxx:973: scenery-search-paths =
   C:/Users/nethe/FlightGear/Downloads/TerraSync
   X:/FlightGear 2020.4/data/Scenery
   28.02 [ALRT]:view      C:\Jenkins\workspace\Windows-nightly\flightgear\src\Viewer\fg_os_osgviewer.cxx:448: affinity=
   28.02 [INFO]:view      C:\Jenkins\workspace\Windows-nightly\flightgear\src\Viewer\renderer.cxx:791: FGRenderer:: Maximum texture size 32768
   28.18 [INFO]:general   C:\Jenkins\workspace\Windows-nightly\flightgear\src\GUI\gui.cxx:135: NVIDIA Corporation
   28.18 [INFO]:general   C:\Jenkins\workspace\Windows-nightly\flightgear\src\GUI\gui.cxx:138: NVIDIA GeForce RTX 3080/PCIe/SSE2
   28.18 [INFO]:general   C:\Jenkins\workspace\Windows-nightly\flightgear\src\GUI\gui.cxx:141: 4.6.0 NVIDIA 526.98
   28.18 [INFO]:general   C:\Jenkins\workspace\Windows-nightly\flightgear\src\GUI\gui.cxx:151: 4.60 NVIDIA
   28.18 [INFO]:general   C:\Jenkins\workspace\Windows-nightly\flightgear\src\GUI\gui.cxx:165: VertexAttribDivisor supported

If I unplug the new monitor and put the old one back in then it works fine.

[wkitty42]

I run with 3 monitors, I've replaced the central "main" monitor so am running the same setup just with a different central monitor at a different resolution. I only run FG on the central monitor - no fancy dual setups when it comes to FG.

ok... what was the old monitor's resolution and what is the new one's?

So far I've deleted the ini in my C:\Users\[user]\AppData\Roaming\flightgear.org\FlightGear folder.

ok, that's only for the launcher settings... have you also tried to delete or remove the autosave_xxxx.xml file(s) in the directory above there?

I've also set the video>resolution settings in the launcher. However FG doesn't give me the option to select the correct resolution for my monitor so I've selected various ones in there for windowed as well as full screen but it seems to make no difference.

yeah... i don't recall what subsystem does the queries for the monitor resolution but apparently it is not seeing what your monitor is capable of OR that resolution just isn't supported at this time...

I was previously running with debug enabled for the logging and the output again is the same as in my first post, almost exactly.

Here's the full dump:

ok, that's good... it tells me you are trying to run FG at 1920x1080 fullscreen... you get the same white screen if you try windowed, too?

If I unplug the new monitor and put the old one back in then it works fine.

yeah, that's kind of expected since things are as they were...

one problem that i have in diagnosing this is that i run on linux and have a 4k and a 1080p monitor... on my (kubuntu 20.04) setup, fullscreen tries to use the entire desktop space as defined in my NVIDIA control tool... that means it is trying to use a resolution of 5760x2160... the problem with this is that i'm missing a full 1080p section in the top right of my layout because my 1080p is my lower right while my 4k is my entire left side... so i end up missing the whole top right view port area and that's not good...

Code: Select all

  <                 5760                   >
^ +--------------------------+
  |                          |
  |                          |  no monitor
  |                          |   here yet
2 |                          |
1 |          4k area         +-------------+ ^
6 |                          |             | 1
0 |                          |    1080p    | 0
  |                          |     area    | 8
  |                          |             | 0
v +--------------------------+-------------+ v
  <           3840          ><    1920     >


so what i ended up doing was to create a config file that i load on the command line via the --config option... this config file defines my screen where i want FG to run... in this case, it is on my 1080p monitor in borderless window mode... note the X/Y positioning for the top left corner of the camera-group window FG will use...

file: fg-monitor-1080.rc

Code: Select all

# this file sets FG to appear on the bottom right 1080p monitor in borderless window mode

--prop:/sim/rendering/camera-group/window/name="FlightGear 1080"
--prop:/sim/rendering/camera-group/window/display=0
--prop:/sim/rendering/camera-group/window/screen=0
--prop:/sim/rendering/camera-group/window/fullscreen=0
--prop:/sim/rendering/camera-group/window/decoration=0
--prop:/sim/rendering/camera-group/window/x=3840
--prop:/sim/rendering/camera-group/window/y=1080
--prop:/sim/rendering/camera-group/window/width=1920
--prop:/sim/rendering/camera-group/window/height=1080
--prop:/sim/rendering/camera/window/name="FlightGear 1080"
--prop:/sim/rendering/gui/window/name="FlightGear 1080"


the camera-group numbers i got from my NVIDIA control tool by looking at how my desktop is defined and being seen... yes, my two monitors are configured as one entire desktop... i also had to give the window a name... leaving that out or trying to use the normal name just didn't work so i gave it the name you see here... then it worked and i only needed to adjust my OBS to look for this window name to capture its output for streaming and recording...

i have no idea how your setup is seeing your monitor layout or if it is seeing them all as one desktop or three separate desktops... i also know that on windows, one can generally just drag an application to the monitor where they want it to run all the time... i can do that on my linux setup but not for FG so i resorted to using the above camera-group file that i load using this command line:

Code: Select all

fgfs --launcher --config=/path/to/fg-monitor-1080.rc

i don't know if this will help you at all... hopefully someone else with a windows multi-monitor setup will jump in and add some other information and thoughts on how to get your's working properly...

[Avionyx]

Thank you for that hugely in depth reply, it's very much appreciated.

I hope you don't think I'm not doing justice with my short reply here but I don't want to get lost in my own badly informed thinking.

The old monitor was 1920 x 1080, the new one is 3440 x 1440 - so quite a difference. I really don't mind what resolution FG decides to run in at this point I just want it to work and nothing seems to be able to achieve that - windowed / fullscreen or whatever I just get a blank white box.

I've tried this morning purging my PC of everything FG and reinstalling again from scratch but the same result. Just a plain white box.
I may try booting into Linux (I dual boot) and seeing If it works in there. I haven't tried that approach so far as previously my Linux graphics drivers led to strange shadow issues but otherwise it worked.

Thanks for all the help so far.
Alex

[wkitty42]

Thank you for that hugely in depth reply, it's very much appreciated.

I hope you don't think I'm not doing justice with my short reply here but I don't want to get lost in my own badly informed thinking.

no problem at all... once i got started, i just kept going...

if i were you, i'd set up a source forge account if you don't already have one, and report this issue on the FG issue tracker there... this way you can interact with any responding devs to test code and provide feedback as needed... at the very least, i'd expect some sort of quick video system resolution detection tool that would basically duplicate what FG does and output a textual table list thing of what it finds and can or cannot support...

[Avionyx]

Don't suppose anyone has got any clever suggestions for this?

Currently the only way I've got to make FG work is to unplug all of my monitors apart from 1 with a resolution of less than about 2600px wide. The issue seems to be the width.
I can then start FG and plug the monitors back in and move the window to wherever I want and it's fine - it's just the starting it that's the issue.

[wkitty42]

Don't suppose anyone has got any clever suggestions for this?

something wrong with my suggestion of creating and using a monitor config file like i show above? i don't see anything in any of your posts indicating that you have actually tried doing something like that...

[Avionyx]

Hi Wkitty,

Thanks for your continued input on this, I appreciate it.

Trying your method it picks up the config file and I can see it's trying to load it as the window it creates is given the name from the config file.

However It just hangs the same as it has been doing before, with this on the end of the log:

Code: Select all

   14.19 [ALRT]:view      C:\Jenkins\workspace\Windows-nightly\flightgear\src\Viewer\fg_os_osgviewer.cxx:448: affinity=
   14.19 [INFO]:view      C:\Jenkins\workspace\Windows-nightly\flightgear\src\Viewer\renderer.cxx:791: FGRenderer:: Maximum texture size 32768
   14.19 [INFO]:general   C:\Jenkins\workspace\Windows-nightly\flightgear\src\GUI\gui.cxx:135: NVIDIA Corporation
   14.19 [INFO]:general   C:\Jenkins\workspace\Windows-nightly\flightgear\src\GUI\gui.cxx:138: NVIDIA GeForce RTX 3080/PCIe/SSE2
   14.19 [INFO]:general   C:\Jenkins\workspace\Windows-nightly\flightgear\src\GUI\gui.cxx:141: 4.6.0 NVIDIA 526.98
   14.19 [INFO]:general   C:\Jenkins\workspace\Windows-nightly\flightgear\src\GUI\gui.cxx:151: 4.60 NVIDIA
   14.19 [INFO]:general   C:\Jenkins\workspace\Windows-nightly\flightgear\src\GUI\gui.cxx:165: VertexAttribDivisor supported


I have 4 monitors all set up in the following configuration:



Monitor 1 and 2 are both individually - 1080 x 1920
Monitor 3 is 1920 x 1080
Monitor 4 - 3440 x 1440

All configured as separate desktops.

Flightgear will ONLY start if Monitor 3 is the only one plugged in. Any other configuration and it just hangs. A plain white box shows up of roughly about 70% of the screen size and it will stay like that for as long as I leave it.

Trying a configuration file I've just taken yours and changed the values. I've tried putting in the values of the two side portrait monitors but the results seem to be the same.

Code: Select all

--prop:/sim/rendering/camera-group/window/name="FlightGear 1080"
--prop:/sim/rendering/camera-group/window/display=0
--prop:/sim/rendering/camera-group/window/screen=0
--prop:/sim/rendering/camera-group/window/fullscreen=0
--prop:/sim/rendering/camera-group/window/decoration=0
--prop:/sim/rendering/camera-group/window/x=3440
--prop:/sim/rendering/camera-group/window/y=1440
--prop:/sim/rendering/camera-group/window/width=3440
--prop:/sim/rendering/camera-group/window/height=1440
--prop:/sim/rendering/camera/window/name="FlightGear 1080"
--prop:/sim/rendering/gui/window/name="FlightGear 1080"


Any idea where I'm going wrong?

Alex

[wkitty42]

i do not know where the problem may reside, alex... in my setup, i have my monitors set up as only one desktop... not separate ones like you say your's is... but we can give this a try if you can provide the needed information... probably the best way to get that info would be for you to take screen shots of your NVIDIA control tool for each of the monitors...

so to try to describe this verbally, on my linux system, i have the NVIDIA X Server Settings tool open... the 2nd option in the left menu is "X Server Display Configuration"... when i click on it, i see a Layout drawn like the ASCII drawing i've posted of my monitor layout... what i'm wanting from you is a screen shot of that for each of your monitors... they should be selectable and the settings for them underneath... like these two pictures where i have selected each monitor (red outline) for the individual image...

with the information from these screen shots, we may be able to figure out what needs to be done for your setup... if i cannot, hopefully the information will be informative to someone else who knows more about running FG in a multi-monitor setup... especially one that is configured with each monitor as a separate desktop as you indicate your's is...

[Avionyx]

Resolved!

I was going really insane with this one and it has spoiled my FG experience for the past 2 months.

However, by going into the nVidia Control Panel and setting my widescreen monitor to "fullscreen" when all the others are set to "aspect ratio" scaling it seems to work in a fashion.



That's how I have it set up. With a config file as per the suggestions above.
It still won't let me run FG in Fullscreen mode (everything seems offset, can't click the buttons as they are out by about 50px and 45 degrees below and right) BUT it does mean I can start and use FG finally.

I haven't found the corresponding setting in Arch Linux yet but will try that this week, at least for now I can use FG again.

Thank you so much wkitty for all your help. It really is much appreciated.
Alex

[wkitty42]

Resolved!

I was going really insane with this one and it has spoiled my FG experience for the past 2 months.

However, by going into the nVidia Control Panel and setting my widescreen monitor to "fullscreen" when all the others are set to "aspect ratio" scaling it seems to work in a fashion.

wowow! i never would have thought of that but then i always think of all my monitors as being part of one large desktop... kind of like those old wall TVs that were multiple TV screens...

That's how I have it set up. With a config file as per the suggestions above.
It still won't let me run FG in Fullscreen mode (everything seems offset, can't click the buttons as they are out by about 50px and 45 degrees below and right) BUT it does mean I can start and use FG finally.

have you enabled the F10->View->Rendering->Compensate field if view for wider screens option? i'm not sure if that only affects the FOV of the scene or if it also affects the menu bar...

I haven't found the corresponding setting in Arch Linux yet but will try that this week, at least for now I can use FG again.

\o/ \o/ \o/ YAY! \o/ \o/ \o/

Thank you so much wkitty for all your help. It really is much appreciated.

you're quite welcome... i mean, i wasn't that much of a help in this case but apparently some information i provided was of some assistance.. which information that was, i have no idea but i am very glad that you figured it out and got it running to this point...