Unable to set full screen resolution

[udihow]

So I decided to try flightgear again, last time was like 8 years ago, I barely remember what it was like.

Running Windows (8.1). Problems arise right from the start. I've gone through everything I can find on the subject, still no solution.

If I put --geometry=*anyresolution* I get that resolution, but in a window..
If I put --enable-fullscreen or select "Start full-screen" I get fullscreen but at maximum resolution where the GUI is very tiny and it's just not optimal.

When I combine these two I'm expecting fullscreen at the entered resolution, but that is not what is happening. Instead I keep getting the maximum res no matter what I put after --geometry=. Why is it so?

What should I do if I want 2560x1440 at full screen?

[Necolatis]

Fullscreen is always at what your monitor resolution currently is at as far as I know.

[AndersG]

There used to be a "game mode" that ran as full screen at a selected resolution, switching screen resolution as required. However, it was, IIRC, removed some years ago as it was rarely used at that point and possibly not even working anymore at the time.

[wkitty42]

i've had no problems using

Code: Select all

--enable-fullscreen
#--geometry=1024x768
#--geometry=1280x1024
--geometry=1600x1200


in my startup options... i just uncomment the geometry i want and comment the other out... works just fine for me on kubuntu 14.04.5... i haven't seen any changes in running the latest 2017.1.0 alpha code... i just double checked and no problems at all... not even setting to 800x600 in full screen mode... the image is a bit grainy compared to 1024x786 and my normal 1600x1200...

i've tried with using --enable-fullscreen as well as using the "start full screen" check box...

so that begs the question of what does your fgfs.log file show? if you can use "--log-level=debug" on your command line and then set your options in the options box... start the sim and wait a minute or two then exit it... then finding and looking at the fgfs.log file, within the first 100 lines you should see something like this...

Code: Select all

[...]
general:3:/home/myuser/flightgear-dev/next/flightgear/src/Main/options.cxx:2345:      option:enable-terrasync =
general:3:/home/myuser/flightgear-dev/next/flightgear/src/Main/options.cxx:2345:      option:enable-real-weather-fetch =
general:3:/home/myuser/flightgear-dev/next/flightgear/src/Main/options.cxx:2345:      option:disable-rembrandt =
general:3:/home/myuser/flightgear-dev/next/flightgear/src/Main/options.cxx:2345:      option:enable-fullscreen =
[...]
general:3:/home/myuser/flightgear-dev/next/flightgear/src/Main/options.cxx:907:Setting geometry to 1024x768

general:3:/home/myuser/flightgear-dev/next/flightgear/src/Main/options.cxx:2345:      option:geometry = 1024x768
[...]


[zakalawe]

The interaction of requesting a geometry and full-screen mode depends on some details of OpenSceneGraph and will vary by each platform. My understanding was that full-screen always used the native screen resolution, but I haven't tested this in any great detail, so if it does interact with --geometry on some platforms, that's essentially a bonus feature.

[wkitty42]

as long as you select a geometry supported by your monitor and video driver, why shouldn't you be able to use fullscreen mode at some geometry less than your monitor's max resolution? then again, i'm using a ""real"" monitor... a good old fashioned CRT... samsung syncmaster 900p... weighs a ton and huge on the desk but i can do any resolutions up to 1600x1200 as long as the driver also supports them... LED/LCD/Plasma stuff? yeah, i've seen plenty of them that won't change their resolution for anything...

[zakalawe]

It's a software issue, the basic OpenSceneGraph windowing implementation we use doesn't support mode-switching on the monitor. Essentially full-screen mode is just a maximised window with the borders / decoration removed. We could add mode-switching but that's some platform-specific, quite unpleasant work. (And I don't volunteer to to support all the ways it can go wrong...)