• Content count

  • Joined

  • Last visited

About grommile

  1. Yadex has been unmaintained for years, Eureka has an intolerable defect in its interaction with X11 (the map view subwindow grabs focus on mouseover), and I don't currently have the patience to go wading into the guts of SLADE's use of wxwidgets 3 to get it running stably and full-featured on my system. What other Doom level editor runs comfortably on Linux?
  2. *twitch* oh god that one blue corridor...
  3. Eternity, HMP, continuous, can't be bothered digging out exactly what my settings are. MAP01 Short, easy, and well-textured. Nothing about the design really leaps out at me. I might go back afterwards and IDDT it to find the secret I missed.
  4. The unconquerable king of hateful official-IWAD levels is The Plutonia Experiment MAP11 "Hunted". Second through fourth places are occupied by the three versions of MAP30. Fifth place goes to E4M1.
  5. That is the answer under the physics of the real world, where gravitational acceleration is applied in discrete lumps so small that on a classical scale the behaviour is apparently continuous. Under the overtly discontinuous physics of the Doom world, where gravitational acceleration is applied in discrete lumps 35 times per second, you get a different answer that has been explained in-thread. Discrete approximations to continuous functions will always tend to contain systematic errors.
  6. If you've found ways in which another source port does a better job of vanilla compatibility than Chocolate Doom, you should file a bug report against Chocolate Doom because that's not supposed to happen :)
  7. Blind run, enjoyed MAP01 (got quite close to dying a few times), then died early in MAP02 because I am terrible at dealing with arachnotrons.
  8. Pump action shotguns with a two-shell fixed magazine are legal on a shotgun certificate, and pump action shotguns with larger and/or detachable magazines are legal on a firearm certificate.
  9. Which part of Europe? British Doom would be very different to French Doom, which would be quite different to Italian Doom.
  10. E4M1, the first half of E4M2, and E4M9 are bastardly. The rest of the episode is easier than the nastier parts of Doom II.
  11. You'll need to learn some ACS, so that you can set up a script that calls the PlaySound() function and then make your linedef invoke that script.
  12. If the map is interesting and I feel like I'm doing better each time I die: quite a lot. If the map is way outside my current competence zone: enough to establish the fact. If it's a good map (Saturnine Chapel springs to mind), I'll make a note to maybe try coming back to it later. If the map feels like it's designed by a sadistic asshole with no sense of gameplay (this includes all clones of Icon of Sin): very few. And the main reason I'm reluctant to change the difficulty setting is that very few wad authors actually do multiple difficulty settings well even if you ignore the ones who just plain don't bother, or who do weird-ass stunts to express their disdain for the concept.
  13. If you want examples of how to render Doom levels in OpenGL, look at the source code for GZDoom or PrBoom+ :)
  14. The complication with getting Unixy people to stop using Autotools is that - as usual where such matters are concerned - even though lots of Unixy people agree that it's fucking awful, there are numerous strongly-held and mutually incompatible opinions about what the replacement should be: Some people replace it with a hand-rolled Perl script and a Makefile specifically written for use GNU Make, since they don't care about Visual Studio users and everyone in the Unix (or Cygwin/MinGW) world has Perl and either has, or can more or less trivially obtain, GNU Make. Some people replace it with CMake (which might actually finally be winning the Autotools Succession War that has been smouldering for an alarming number of years). Some people replace it with waf (despite its architecture making Autotools + Make look sane). Some people replace it with SCons (which may well be fading from view). A few people replace it with redo. Some people replace it with something insane of their own devising. Some people replace it with the specialist toolchain for the GUI library they're using. Some people write their programs in a language that has its own building-and-packaging toolchain specifically designed for programs in that language. Some people refuse to replace it because get off my goddamn lawn. Some people refuse to replace it because Autotools has the notable virtue that if all you want to do is build and install the packaged upstream source code of a program you don't actually need to have autotools installed; you can just invoke the 'configure' script shipped with the packaged source code. (Strictly speaking, the expected SOP is that if someone grabs the packaged upstream source, your build sequence can be invoked as if your software used autotools i.e. "./configure && make && sudo make install" should configure the software to build on your system, build it on your system, and install it into /usr/local .)
  15. Let me remove your uncertainty: In Debian, 'Essential: yes' means "this package is a sufficiently critical system component that all packages which aren't Essential: yes are allowed to assume it has been installed". grep, as shown, is Essential: yes and depends on libpcre3, so... yes, libpcre3 is a critical system component. (The C header files won't be automatically installed, but installing them is a simple matter of saying 'apt-get install libpcre3-dev'.) Linux is the Unix-like platform on which it is easiest to get rid of fucking Autotools, because you don't need to care about backwards compatibility with 742 subtly different flavours of antediluvian steam-driven proprietary commercial Unix :D :D :D (Lots of people still use it because, y'know, people get set in their ways, but nobody likes it except possibly Saint Richard.)