This document describes
config/gfxmodes.txt, an advanced configuration file with which you can add otherwise unavailable screen modes to Outgun.
This document applies to Outgun 1.0.
gfxmodes.txt hasn’t been used by any previous versions.
You don’t need
gfxmodes.txt in normal operation; it’s useful if Outgun doesn’t detect the mode you want to use. One usual case is that you want to run Outgun in a window with a custom size or even other than 4:3 geometry. Note that whichever ratio you choose, Outgun always treats the screen as if pixels were square, and therefore the playfield is always sized 4:3 in pixels.
The format Outgun 1.0 understands is very simple. Every non-empty line that is not a comment (those start with a semicolon, ‘;’), should describe a screen mode. The lines should include a width, a height, and a colordepth, separated by spaces. For example the line
640 480 32
adds the resolution of 640×480 with 32 bits per pixel. There are limitations: the width must be at least 320 pixels (640 before Outgun 1.0.3), the height at least 200 (400 before 1.0.3), and accepted values for color depth are 16, 24, and 32.
When the basic limits are met, Outgun accepts the mode and makes it available in the menu, without testing it in any way. Note that you can’t choose whether the mode is usable in full screen and/or window, it’s always made available to both even if it doesn’t actually work in one. Naturally, in windowed mode the width and height determine the size of the window, and in full screen, the resolution – just as with the automatically detected modes. Usually almost any size can be used in a window (larger than the desktop obviously isn’t useful), while there are limited options for full screen which depend on the gfx card.
For easy testing of which modes work, or fine tuning a window size, you can edit the file while Outgun is running.
gfxmodes.txt is reloaded each time you open the screen mode menu.