Slashdot Mirror
Doomsday Gets DOOM, Heretic, Hexen Engines Upgrade
Ant writes "I just noticed Doomsday HQ, source of some of the best enhancements of original DOOM, Heretic, and Hexen game engines since the code was open-sourced, has released v1.8.0 of both the Linux and Windows ports. SkyJake, the author, also mentions on the news page that a Mac OS X version might be ported in the future." As the official beginner's guide notes, you'll need "a copy of the original shareware/registered [game .WAD]" to play.
This is such an awesome source port of doom, but the documentation for the Linux version leaves a *lot* to be desired. I still have no idea where to place my updated textures, music files and models to get them into my game under Linux. :-(
.exe, user is jfiles and password blank) and the updated music it looks and sounds nearly as good as quake 3. :-D (no, seriously :-D ) Make sure to turn on all the rocket trail and mouse look stuff, most of it is disabled by default. :-D
:-D
.wads from id's ftp I think...
By default it looks like regular doom, but if you get the texture pack (big zip file at the bottom of the page,) model pack (direct link to a 9 meg
Hrm... opengl doom at 1280 * 960... hrm...
You can still get the demo
You put .pk3 files into Data/jDoom/Auto. Ideally, all the content you download will be .pk3 files, making it a lot easier. I think there is also a use for Data/jDoom/Textures and Data/jDoom/Patches, but I haven't quite figured it out yet.
And the "jDTP" texture pack is much superior to the Doom 2 Retexturing project.
Unfortunately, it seems to lack permanent hosting. http://www.jdql.tk/ links to it, but the FTP site it links to for the jDTP seems to be down. I managed to get one part of it (the Doom1-only textures), and they are a hell of a lot nicer and more faithful to the originals than the Retexturing Project's textures.
Eat the rich.
I still have no idea where to place my updated textures, music files and models to get them into my game under Linux. :-(
/usr/local, so the data files were in a directory tree under /usr/local/share/deng; if you're still having problems when you read this comment, post a reply and I'll give you more details. (Can't do it at the moment as I'm at work. And The Boss's desk is right behind mine. Talk about living dangerously ;-)
/vfat and symlinking the data directory into it. What fun. There's probably a "proper" way of solving that one, mind.
Heehee, I was wrestling with this yesterday evening.
I resorted to using strace, redirecting stdout and stderr to a file, then searching through the trace for the string "No such file" to see where it was expecting the files to be. I installed Doomsday into
To add to the problems, Doomsday seemed to be expecting a case-insensitive filesystem (a legacy of its Windows origins, no doubt), as it seemed quite inconsistent in its use of (for example) "jdoom" vs. "jDoom", "md2" vs. "MD2" etc, so I ended up mounting a FAT32 partition under
-Stephen
jDooM Quick Links for other goodies since I just discovered this site a few days ago after submitting my story!
Ant(Dude) @ Quality Foraged Links (AQFL.net) & The Ant Farm (antfarm.ma.cx / antfarm.home.dhs.org).
The placement of resource files such as PK3s and WADs should be covered in the engine readme file, which is conveniently not included in the Linux source tarball. :-) Also, you'll have to manually create the Auto directory under Data/jDoom. I guess there would be a need for an install script that takes care of the basic setup.
All the current resource packs have been developed on Windows systems, so you may also run into some troubles with case sensitivity. In general, Doomsday will handle the contents of PK3s in a case-insensitive manner but it's something to watch out for.
The Textures and Patches directories are explained in the engine readme. They can be used to replace the original low-resolution images with high-resolution ones.