Note also the gzdoom executable location is that indicated following gzdoom installation at the start of the guide.įinally, note the %F replacement variable which will be replaced by any dropped. Note that we need to specify the full paths for the ini file and the save game location Make sure the paths include your username: Edit with a text editor and add the following contents (you may need to use the nano sktopĪdd the following (note we are using nano here). Again, using the Brutal example:įrom File Explorer/Desktop, create a new file called - e.g. They are basically text files that point to other files and define how they should be processed. It is more fiddly to create desktop launchers in Ubuntu than it is in Windows. Note that these locations reflect my deployment path ~/Deploy/Doomįinally, we want launchers for each gameplay mod that allow autoload of gameplay mod and drag-n-drop of custom WADs from any location. Path=/home/username/Deploy/Doom/Brutal/DoomMetalVol4/DoomMetalVol4.wad Path=/home/username/Deploy/Doom/Brutal/brutalv20b.pk3 Here, we want to load Brutal (Duh!) and DoomMetal. The others are added by default when the. ![]() Note the addition of the third 'path=' entry above. Note that 'username' is your Ubuntu user login: config/gzdoom/gzdoom.ini, when we did the test run of the menu launcher). Therefore, add that to the relevant section of the new ( copied from the default, as created in. GZDoom will look in various default locations, but I wanted to specify those in my Doom directory as above. Using the setup for Brutal Doom as an example here, we need to create a custom gzdoom-brutal.ini file, in the /Config directory above, specifying various locations and default overrides: Note that all this section uses standard zdoom configuration that can be read about here. I specified subdirectories in the configs for each gameplay mod. ini file locations are important when defining a desktop file, later on. ini files, defining non-default IWAD locations, savegame locations and different autoloads. I set up a simple structure in ~/Deploy/Doom/ like so (note I added ~/Deploy/ for other purposes):Ī number of GZDoom. I didn't want to bugger about with hidden directories, shell files and CLI launching (as I said before - lazy fucker.), I wanted desktop icons with drag and drop, the gameplay mods, the IWADs and specific. This is where the setup differs somewhat to the procedure for Windows. It would of course be possible to alter the default shell file to point to the correct places, but I won't be doing that in this guide. I won't be using this launcher from here on in. Running the above menu launcher will result in: However, at this point, it will not work because we don't have any IWADs defined. ini file in the hidden folder, ~/.config/ of ~/.config/gzdoom/gzdoom.ini. ![]() It will also add a gzdoom launch icon to the application menu: This will open the installer package and, following sudo confirmation password, will install to a fixed location of /opt/gzdoom/ and add a default launcher shell file to /usr/games/. deb file, so once downloaded (to ~/Downloads most likely), right-click and select 'Open with Software Install': These are likely older now and there is an Ubuntu version available from the zdoom website. There are various posts around that describe to compile from source or use alternate repositories. The differences to the Windows solution are that GZDoom is installed in a hidden location, and desktop shortcuts are created differently. Also, as before the key is different GZDoom.ini files, one per autoloaded gameplay mod. Right as promised in this post, here is the equivalent for Ubuntu (18.04 lts).Īs before, I want to use purely a single deploy of GZDoom, autoload of gameplay mods and allow drag-n-drop PWAD launching as well.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |