Worse still, the key binds that are there aren’t really in any particular order, so it will take forever to find what you need. Not all of the variables are there for you to map. You’ll need to specify your keys yourself in the zdoom.ini. Unfortunately, zdoom doesn’t save any mappings you make within the wrapper. I didn’t include it, since other WADS such as Heretic, Hexen and Strife are incompatible with Brutal Doom. If you want it to, you’ll need to provide -file /home/cpi/games/ChocoDM/brutalv20b.pk3 before -iwad in the launcher line. Keep in mind, this won’t load the Brutal Doom mod. LAUNCHER=zdoom -width 320 -height 240 -iwad Unfortunately I don’t know how to independently choose both -file and -iwad arguments, besides having discrete nfig files for each -file combination. WAD/.pk3 files, you can make an nfig file to specify which WAD to use. Just keeping things tidy.Īlternatively, if you’ve got a lot of. I chose to have the WAD directory as ROM=/home/cpi/games/ChocoDM, since this is a path already installed on a stock 0.5 system, and is where the chocoDM built in wrapper expects WAD files to be. You’ll need to specify the directory in the zdoom.ini file. Running the script without any parameters telling it where to find PAK files can allow you to choose which WAD file to use. (I’ve installed the launch files to the /usr/games/zdoom directory, so I can just use the shorter alias to start it, but that’s just my own OCD preference) zdoom -width 320 -height 240 -iwad /home/cpi/games/ChocoDM/DOOM2BFG.WAD -file /home/cpi/games/ChocoDM/brutalv20b.pk3 (I’m guessing the 324x240 resolution specified was an error?)Įg. I’ve added a forced resolution into my *.sh launch script, forcing the 320x240 resolution. Snd_mididevice=-2 if you also want to have music. Awesome job on this! Glad you finally got some closure on a good thing!Īnother thing to include in the zdoom.ini file is
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |