This is an article I had been working on that could replace the command line arguments list. This allows people to link directly to any singular parameters, and gives space to note every relevant thing about each parameter.

  • I think I still needed to do some research on some stuff, so it's a work in progress.
  • I chose an alphabetical order instead of dividing the parameters into types or something. Some overlap in what they deal with anyway. I did add tags so one can immediately tell what the parameter is for.
  • I'd say source port parameters are best listed on the pages of those ports, or if they have tons of parameters worth writing about, yet separate articles. Articles on engines with few differences can just note and describe what changed and what's new (or missing) otherwise linking here. Who is like God? 06:07, 21 May 2008 (UTC)
Separating vanilla and source port parameters is a good idea, though I'd prefer to have the most common source port parameters in one unified article and the more unique/port specific ones listed as you mentioned (though this would probably be necessary only if someone actually bothered to properly document the majority of the source port parameters). Another suitable solution would be one source port parameters "hub" article that has an assortment of links pointing to each port's parameters section/article. A combination of these solutions might be good also. -- Janizdreg 20:05, 21 May 2008 (UTC)

-drone parameter[edit]

The -drone parameter is missing --Russell 03:40, 19 December 2008 (UTC)

-drone is not a vanilla option, so it belongs in the Source port parameters article.    Ryan W 14:16, 6 April 2012 (UTC)

-emulate parameter[edit]

The -emulate parameter is mentioned here , but I don't know if it works with the Doom95 engine played on Windows XP. I could be playing any of the Doom's (Ultimate, II, Final), and my entire screen's colors go wrong randomly during gameplay - sort of CGA'ish. Reloading my saved game fixes the colors until next time it happens, however, I also have issues with my saved games. If I reload a game while Doom is running (F3 or F9), the first Demon I encounter runs faster than the Fast Monsters option ever allows (not so much chopping movement, but instantaneous and in my face), and causes the whole game to freeze right there. To avoid that issue, if I have to reload a game I exit the game first, then reload from the Doom95 menu. However, not all saved games reload correctly this way, either, but instead crash the entire engine (I'm told it's a bug involved with when I save my game), thus I have to start a new game one level earlier so I can regain the backpack (one of four items cheat codes can't directly restore).

Actually, I thought I had been playing with XP's Compatibility Mode, but when I checked the shortcuts, none of the Compatibility checkboxes have been marked.
Suggestions based upon the fore mentioned? 05:36, 6 April 2012 (UTC)

When I had Doom95 on XP, I frequently used -emulate to speed up demo playback.  That said, the performance of Doom95 depends greatly on hardware and driver configuration (mine was more compatible than average apparently).  On a modern graphics card, the presence or absence of -emulate may even crash the program.
My experience with Compatibility Mode is that it is just window-dressing and doesn't actually run the program differently, but others may disagree (especially when the application was developed for Win9x in the first place, which Doom was not).  Any evidence of its actually working should be included in this article, given the thousands of people who have tried and failed to run Doom95 on XP.    Ryan W 14:31, 6 April 2012 (UTC)
P.S.  I clearly recall watching demos on youtube with the faster-and-faster-monsters savegame bug, and the uploader descriptions may even have mentioned crashes, but now I can't find them again, arrgh...    Ryan W 15:34, 6 April 2012 (UTC)
P.P.S.  The youtube video is here.    Ryan W 17:00, 14 April 2012 (UTC)