Provides borderless fullscreen support for Battlefield 1942.
- Download the latest release into the directory where
BF1942.exe
is located. - In
Mods\bf1942\Settings\VideoDefault.con
, setrenderer.setFullScreen
to0
. - In
Mods\bf1942\Settings\Profiles\Custom\Video.con
, setgame.setGameDisplayMode
to the resolution of your monitor (eg. mine is set to1920 1080 32 0
) - Run
Borderless1942.exe
and it will open BF1942, remove its borders and manage its position. - If you want to run the expansions, pass
+game {mod}
as arguments where{mod}
is:XPack1
for the Road to RomeXPack2
for Secret Weapons of WWII
To make it easier to launch the expansions, create a shortcut to Borderless1942.exe
with the following:
- Target:
"C:\path\to\bf1942\Borderless1942.exe" +game XPack2
- Start In:
C:\path\to\bf1942\
Basically I was having issues running the game in fullscreen on a machine of mine. The game would run fine in the menu but would crash loading the map - simply by running it in a window fixed that.
Running in a window though was a bit crappy with the border and where it positioned itself on the screen. Borderless 1942 removes the border and repositions the window based on the window size so it is always in the center.
BF1942 throws an extra curveball by changing process when you exit out of a map. Borderless 1942 also tracks this and reapplies the border and positioning logic on the new process.
Probably. I built this because I wanted to and seemed like a fun side project to do. 🤷♂️
Borderless 1942 is the console window. Closing it won't close BF1942 but will stop the border and positioning logic.
Closing the game through the Quit
menu item will close the console window after a few moments.
You'll need the .NET 6 SDK but besides that, just run build.bat
and it will build from source.
It uses a mixture of .NET and Win32 APIs to find the window for the main BF1942.exe
process.
Once it has that, it is just a matter of constantly checking if the process has changed or closed,
updating the window position and removing the borders.
To center the window though, it also access Win32 monitor APIs to get the size for the primary monitor for the window.
I dive a bit deeper into how it all came to be in my blog post.
Nope! It is a self-contained executable - it contains everything it needs to run.
It is also why the file size of Borderless1942.exe
is as large as it is.