Jump to content
Search In
  • More options...
Find results that contain...
Find results in...


  • Content count

  • Joined

  • Last visited

Everything posted by Mattfrie1

  1. DOWNLOAD LINKS TO TC (Copied from ScottGray's post) PSX Doom TC Version 2.135 fenderc01 (Who made the original PSX Doom TC) has kindly made a mediafire page which compiles all the files (including the most recent TC update) related to this project on one page. Please click here for the link. GAME MUSIC (PSXTCMUS.PK3) (76.5MB) http://www.mediafire.com/download.php?w1uo81ee7ikc7kb Credits fenderc01 (Maker of PSX DOOM TC/Resources/Tester) Dragonsbretheren (Updated TC Maker/Tester) Gez (Assistance with weapon and monster coding) Scottgray (Lead Programmer on PSX Final Doom maps) Omnipotus (PSX Final Doom Converter) lafoxxx (Rerecorded Music/Tester) unknownna (Multiple Bugfix Updates) scalliano (Credits roll/Tester) Sodaholic (Sprite/Palette Conversion) Testers: francis247uk buttspit GBT3 Hellknight2012 Charu nirv ORIGINAL POST
  2. Mattfrie1

    Dissecting Sega Saturn Doom

    As we all know, Doom on the Sega Saturn was a less than stellar port. The Saturn version borrows many resources from the much superior Playstation port. I did a little bit of digging around on the disc to see how it compares to the PSX version, and here are some of my findings: ⦁ The total disc size of PSX Doom is 241 MB. The total disc size of Saturn Doom is 557 MB. The main reason as to why the Saturn version is so much bigger is due to the inclusion of more CD Audio tracks. For comparison, the cd audio on the PSX version takes up 194 MB of 241 MB total. The cd audio on the Saturn version takes up 493 MB out of 557 MB total. ⦁ Unlike the PSX version, the Saturn version uses these extra CD audio tracks for the level background music instead of the midi-like .lcd files that the PSX version uses. Only half of the tracks from the original PSX version were converted to the redbook audio format on the Saturn. Almost all of the ambient tracks on the Saturn version seem to have some slightly different elements to them (i.e. different fades for some instruments, some instruments played back at slightly different pitches, different track length, etc.). This makes me wonder how these tracks were "acquired" for this version. Did Rage Software personally contact Aubrey Hodges for the music? Or did they just rip the files from the PSX disc and play them back on slightly different equipment? ⦁ The main resource wad on the Saturn version is called JIMSDOOM.WAD, obviously named after Jim Bagley, one of the lead programmers for this port. The wad is a 1:1 copy of PSXDOOM.WAD , and even includes resources that only pertain to the PSX port (i.e. Buttons graphic that contains symbols for buttons on the PSX controller, original legal screen that appears at the beginning of the PSX version, etc.). ⦁ This wad contains some interesting things in it. The status bar for the PSX version is still here. Also, the graphic for the title screen is missing the GT Interactive logo that is present in the version included in PSXDOOM.WAD. Most interesting of all however is that the LIGHTS lump from the PSX version is still present in JIMSDOOM.WAD. This makes me wonder if the Saturn version is capable of colored lighting like the PSX version, but wasn't included due to time restraints. ⦁ One thing that puzzles me, why is JIMSDOOM.WAD almost 2,000kb bigger than PSXDOOM.WAD? Both wads contain the same number of entries (a fact also mentioned on the Doomwiki). I also compared both files in Slade side by side to be sure and couldn't find any obvious differences to account for the different file size. ⦁ The maps are stored in the same way on both the PSX and Saturn versions. This has been well documented by Kaiser in a previous thread, so I won't go into it here. One can actually use the same programs for converting PSX maps for the maps on the Saturn disc. Each map on the Saturn disc also contain the LEAFS lump, which is responsible for assigning the colored lighting and reverb effects in the PSX version. Of course, these effects go unused in the Saturn version. ⦁ The disc contains 9 folders. 7 of them store 59 levels in folders titled MAPS0 through MAPS7. However, both MAPS0 and MAPS1 contain files that don't seem to be related to map data. MAPS0 also contains a STATS.CHR and a STATS.MAP file, which I'm guessing is the data for either the intermission screen or the new HUD. MAPS1 includes several really interesting files. The first is a 10 byte file called DOOMMAP.BIN. The second is DOOMTONE.BIN, and the third is SDDRVT.TSK. I'm not sure what the first one is for, but I'm thinking that the second and third files have something to do with the games sound. Perhaps DOOMTONE.BIN is all the game's sound effects, and SDDRVT.TSK is the game's sound driver? ⦁ SCRS is the folder that appears to hold the files to the game's opening sequence. Curiously enough, the four screens that pop up when you start the game are all listed as screen savers as the file type. Sadly they don't work on my computer. ⦁ SKYS is the last folder, and is pretty self explanatory. It contains both .CHR and .MAP files for the game's 7 skies, plus mysterious SKY20 and SKY21 files as well. Also contained in this folder are the four .lmp files used for the game's demo sequence. It's interesting how the sky textures are given their own folder, as all 7 of them are also included in JIMSDOOM.WAD. ⦁ The rest of the files are contained in the disc's main directory. The one file that attracts my interest is a 400 kb file called 0.BIN, sadly it's mysterious file name doesn't give any hint as to it's purpose. I'm wondering if this is where the game's main .exe file is stored. Personally, I think it was Rage Software's intention to make Saturn Doom as much like PSX Doom as possible. But when John Carmack shut down their original plan to use a hardware-accelerated renderer, all those ideas were thrown out the window. I wonder how late in the development cycle the change from a hardware to software renderer was made, and if they had to rush to get the game out the door after the change was mandated. Plus, why was Carmack so picky about Doom, yet he let Lobotomy Software port Quake to the system using an entirely new game engine? There are still many questions about this port... So why am I doing this? Well, it's partially because I think the Sega Saturn is an underrated system, and also seeing the background behind 3DO Doom made me want to look into the other very well-known poor port of Doom. I wish there was a way to examine the source code for this port, but sadly hacking for the Sega Saturn isn't really well documented on the internet. If anyone else has anything to add, it would be well appreciated.
  3. Mattfrie1

    Dissecting Sega Saturn Doom

    I've managed to somewhat fix the issue this port has with displaying the Doom II city sky for levels that originally had the animated fire sky in the PSX version. SKY3 from Ultimate Doom was converted to the new sky format for this version as well but never appears normally during gameplay (Stored as SKY03.CHR and SKY03.MAP). By switching around the order that the sky files are ordered in the system's memory will allow the previously unseen SKY3 to take the place of another sky texture. I'm assuming that the Doom II Cityscape texture appears on the fire sky levels due to a simple programming error. The devs probably meant for the Inferno sky to take the place of the animated fire sky, but probably mistakenly point to the cityscape sky when loading in the level (SKY05 instead of SKY03 to %s.CHR and %s.MAP after P_LoadSectors). I've also been looking more into why this version doesn't display colored lighting despite all the files and code still being in place: - As mentioned in the previous post, Saturn Doom has it's own separate PLAYPAL file that it loads outside of the main IWAD. However when comparing this file with PLAYPAL extracted from the PSXDOOM.WAD shows absolutely no differences between the two files at all. - Saturn Doom also has additional .PAL files for the fire sky that appears on the title screen, the title screen itself, the background of the cast sequence at the end of the game, the three legal/logo screens at the start of the game and unused files for IDCRED1 and IDLOGO. The aforementioned SKY20 and SKY21 also have .PAL files. - I'm wondering since the LIGHTS lump wasn't included as it's own separate .PAL file could be a reason as to why colored lighting isn't displayed in-game, but it's only a theory at this point. Finally as a random side-note, both DEMO3.LMP and DEMO4.LMP are identical files, which is why one of the demos appears to repeat itself twice.
  4. Mattfrie1

    Dissecting Sega Saturn Doom

    Thanks for the heads up @mr-around. Not surprising to hear the same thing happens in PSX Doom. I've been looking around some more in a Saturn emulator to try to figure out some more clues as to how the game operates: - Level rendering appears to be handled in the same way as the PSX version as described on the last page, but instead of using quads the system is using distorted sprites to draw each individual column. This was a very common practice that Saturn programmers used in many 3D games on the system, and rendering of these sprites is handled by the Saturn's VDP1 graphics chip. Keep in mind however Saturn Doom emulation is still very buggy, so I'm assuming this is actually how the system operates and not a bug of the emulator. - There's a few Action Replay / Gameshark codes for the Saturn port floating around the web. Most of the codes are for rather simplisitic things such as maxing out your ammo or giving certain inventory items, but one is for changing the firing speed of your weapons which I found rather interesting. I messed around with the values on my actual console and found that setting the bytes to all zeroes cause the weapons to not load in at all, leaving you running around the level helpless. Setting to any other value besides 0001 causes weapon behavior to become very glitchy and hang up on random firing frames. Using the Saturn emulator's memory editor for reference and the Action Replay I've been able to edit a few things here and there in memory without making the game crash. I'm trying to cross-reference with the PSX port as well (PSXDOOM.EXE from the game disc) to see any noticeable differences between the two. - Changing the two bytes between LIGHTS and PLAYPAL change the overall intensity of the lights in a level. The higher the value entered, the darker the lighting becomes overall. - In regards to this, the Saturn version looks like it could be using it's own unique PLAYPAL file instead of the one supplied in the main resource WAD. There is an extra file on the Saturn Doom disc called PLAYPAL.PAL which is referenced after LIGHTS in memory. Keep in mind that PSX Doom's PLAYPAL is still on the disc in the overall resource WAD (JIMSDOOM.WAD).
  5. Mattfrie1

    Dissecting Sega Saturn Doom

    I've gotten a new capture card setup recently, so I figured I'd revisit my old friend Saturn Doom. As stated on it's Doomwiki page, PSX Doom has a bug where lost souls outside of level boundaries can cause a level to get corrupted. I figured that since many aspects of PSX Doom are mirrored in the Saturn port, the bug would be possible to duplicate in this version as well. The video features two instances of the bug happening. Perhaps the most interesting event occurs at the 3 1/2 minute mark where I look on the other side of a transparent gate texture. The game draws a bunch of random colored pixels on the other side of transparent textures. Although it is distorted, you can see some of the blocks of color flashing to different colors in a fixed pattern. The way they are laid out remind me of a color palette, but I have no way of proving exactly what it is at this time. The same effect can be spotted again for a split second right before the 9 1/2 minute mark on the other side of the cages where the pain elementals spawn in the final area. Not sure if this same thing happens when the glitch is done in PSX Doom, but I couldn't spot it from the one YouTube video that exists of the glitch. I actually manage to exit the level on the first attempt shown in the video, but the game freezes on the other attempt. No error message or black screen like PSX Doom however (even though all the error messages remain in the Saturn version's code), just the screen freezing with the game's music still playing unaffected in the background.
  6. Mattfrie1

    What Video Game Are You Currently Playing?

    I've been on a binge lately of playing all the PS3 games that have come out in the past year and a half or so. It's hard to believe that the system just had it's 11th birthday this past Fall, and there was still a rather healthy amount of games (mostly indie digital titles) that were released for it last year. I just recently grabbed Persona 5 as well as a part of picking up recent PS3 titles, and I've been blown away at how good it is. One of the indie titles that I've put some time into is called The Surfer. It was released back in December and surprisingly is only available on PS3, quite crazy to see an exclusive title this late in the system's lifespan. Just for the hell of it, I put together a gameplay video since there doesn't seem to be any other comprehensive videos of the game currently on the web:
  7. Mattfrie1

    Dissecting Sega Saturn Doom

    I'll just post a screen grab of what I'm seeing in the hex editor, I'm pretty sure this is what you're looking for. https://imgur.com/68uuEbx Aside from that, I did another comparison of the source WAD files (PSXDOOM.WAD and JIMSDOOM.WAD) between the two ports in Slade. Both of these files are ALMOST identical, but there are several entries which appear to be corrupted in JIMSDOOM.WAD. BSPIC2C8 (an arachnotron walking sprite) is only 5.52 kb in JIMSDOOM, whereas it's 7.02 kb in PSXDOOM. SKELG2 (A revenant punching sprite) also doesn't display in JIMSDOOM, but is the same file size as PSXDOOM. Both of these sprites still display correctly in game however. Just for the hell of it, I put both PSXDOOM.WAD and JIMSDOOM.WAD through the hex editor, even though I already know that JIMSDOOM is a lot bigger in file size than PSXDOOM. I've attached screen grabs of the end of both WADS in hex below. https://imgur.com/pYzAzZS https://imgur.com/7a1LWHp
  8. Mattfrie1

    Dissecting Sega Saturn Doom

    So I've decided to do a little digging into Saturn Doom again to see if I can uncover any other fascinating things about this flawed port. Here's a few more interesting things that I missed on my first examination: - The DOOMTONE.BIN file is indeed the file that houses all of the game's sound effects. Opening the file as raw data in Audacity under the correct settings reveal all the sound effects laid out in one long "chain". Sounds are also sampled at the extremely small sample rate of 2500 hZ. I'm assuming that the DOOMMAP.BIN file serves as an indexing file, telling the system where each specific sound effect starts and ends in the DOOMTONE file, as well as each sound's duration. This is yet another way that this port inefficiently utilizes system memory, since the game most likely has EVERY in game sound stored in memory at all times. - I also feel the need to point out that since the Saturn uses an entirely different sound engine from the PSX version, there was no possible way that this port could have supported sound reverberation effects, especially since the reverberation effect was a feature of the PSX's sound processor. As far as I know, the Sega Saturn's sound processor had no equivalent feature. - Right after P_LoadSectors is mentioned in 0.BIN (the game's main program file), the code makes mention of F_Sky immediately followed by %s.CHR and %s.MAP. This shows how the Saturn port has extra code added in for the "new" skies utilized by the Saturn's VDP2 chip that appear in the SKYS folder. This of course means that the sky textures included in JIMSDOOM.WAD are redundant since they appear to be coded to never appear in game, and are overridden by the new sky files. - All of the .CHR files are in the tile format of 8BPP, which is common for tiling backgrounds and such. Sadly not many tile editors currently support 8BPP, but the tile editor in the Windhex program can display a garbled view of the file. I still can't tell what SKY20 and SKY21 are supposed to be, but the STATS.CHR file is where all the tile data exists for the new status bar, the status bar face, the font for all in game text and the loading graphic. INTERPIC.CHR (in the disc's main directory) is used for the the game's main menu and intermission screen, and is scaled slightly differently from the very similar image used for the PSX's main menu. - All of the map files for the Saturn port are the same exact file size as the map files for the PSX port, and examining the files in a hex editor reveals absolutely NO difference between the files as well. Since the files are an exact match, I wonder if all the information about colored lighting and sound reverberation are still included in the Saturn files... - All of the files on the Saturn Doom disc contain the date of 1/29/97. GameFAQs states that Saturn Doom was released in the US on 3/31/97, only a 2 month period from the game being compiled to it being out in the stores. - In a previous post I made specific mention to the NIN secret in Hell Beneath and how the walls after the secret is activated are almost always buggy. Ultimately, I believe I've discovered a reason and a pattern to this phenomena. First off, the walls to this secret are NEVER drawn correctly in this version. Instead, the game seems to texture the wall with what ever texture data was last "occupying" the area of memory that the correct texture is supposed to be in. Curiously enough, loading the level from scratch after you start the system via password yields the game to draw a blank wall that is completely see-through. Otherwise, the game will draw a texture from the previous level that was loaded. - I've compiled a video sampling what this bug looks like. The first clip shows what the blank wall looks like, and the second clip shows what the wall looks like after warping to the level from Club Doom. After that shows some of the "highlights" that I found messing around with this bug, enjoy:
  9. Mattfrie1

    Flaws in official DOOM ports.

    Many of those same issues with software rendering are also in the PSX port of Hexen as well. The PSX port of Hexen also utilizes the LEAFS map lump in all of it's levels as well, so that might have something to do with it. The imp alert sound is due to how the sound is "recorded" in the .LCD file for certain levels. Each level has a .LCD file associated with it which includes all the sound effects that the level will use as a way to better utilize system RAM. One can listen to all the sounds in these .LCD files by using a program like PSound, and you can hear how the sound is "cut off" in the source file as well, it probably has something to due with how it was compiled into the file. On a similar note to this, all the Lost Souls that the lone Pain Elemental in E1M1 on UV spawns are silent when attacking you. This is due to their attack sound being mistakenly not included in the level's .LCD file. Lastly, the music track for Minos also only plays once. A similar error also occurs on several levels in Doom 64 as well.
  10. Mattfrie1

    would you like to see PSX Doom ported to PC?

    MAP60.LCD is actually the sound file for the end screen that goes through the entire cast of enemies in the game, thus the reason why it contains all the sounds. The same MAP60.LCD file is also retained on the PSX Final Doom disc (Even though that game has only 30 levels) for that game's ending screen as well. The Saturn port also contains files for a MAP60 as well, but those files appear to be for all the monster sprites for the ending screen instead.
  11. Mattfrie1

    would you like to see PSX Doom ported to PC?

    The Sega Saturn port also has all the same error screens as the PSX version coded into it, although there seems to be no way to actually trigger them in game. I've tried numerous times to get the "Texture Cache Overflow" error to trigger on The Citadel but the game simply won't do it.
  12. I attempted to look into the workings of the PSX port of Hexen last year in this thread. Ultimately, I believe that the port is crippled because of the combination of using the LEAFS lump to render levels and Hexen's own ACS. The game notably slows to a crawl whenever any large scripting event takes place while a lot is being rendered on screen, yet opening the automap or turning to face a wall will speed up the scripting process to it's regular speed. The fact that the developers used the retail beta version as the source to work from instead of the finished retail version could be a factor as well.
  13. Mattfrie1

    PSX Doom/Final Doom TC (Version 2.135 now released!)

    I know I'm a bit late in responding to this, but I don't come around these parts as often as I used to. I just edited the OP to remove the broken link and to clean it up a bit. Anybody can feel free to message me if any more links become broken or to add any project updates to the post, I'll try my best to add them as soon as possible.
  14. So I've recently bought an Atari Jaguar, and with it both the ports of Doom and Wolfenstein 3D. The source code of Jag Doom has obviously been available for a long time now, but the Jag port of Wolfenstein 3D has been a little bit harder to get information on. As we know, the Jaguar port of Wolfenstein 3D came before the port of Doom, and was ported by id as a way to test the abilities of the Jaguar to see if it would be able to handle Doom. The Jaguar port of Wolfenstein 3D is noted for having numerous similarities with Doom. The sprites for the pistol, chaingun and rocket launcher are all borrowed from Doom, the lives/treasure system is completely removed and those items now act like the health potions and soul spheres from Doom, and higher difficulties randomly have treasure pieces removed and replaced with enemies. Like I've done with previous games in the past, I figured to open up the ROM of my copy of Jaguar Wolfenstein 3D in a hex editor just to poke around and see if there was anything unusual in there. I'm not sure if any of this has been documented any where else on the web, I've done a quick google search about the Jaguar port of Wolf 3D, and I haven't really found all that much info about the port. Perhaps if someone has some knowledge about this they can come forward about it. Anyway, the first thing that I noticed right away towards the beginning of the ROM were some of the same "error messages" that I've been seeing in pretty much every Doom console port that I've viewed in a hex editor. Upon also looking at the Jaguar port of Doom and the SNES port of Wolf 3D in a hex editor, here is how Jag Wolf 3D is broken down: Starting at memory address 00011310 in the ROM of Jag Wolf 3D are the same set of info/error messages that also appear in Jag Doom, these messages are: -NuIWAD.Wad file doesn't have IWAD id -NuW GetNumForName -NuILumpLength -NuIReadLump -NuiCacheLump Then, several error messages (I'm leaving out some of the descriptions here): -NuZFree -NuZMalloc -NuZCheckHeap -NuZChangeTag Following these are several error messages that have been brought over from SNES Wolf 3D, and generally relate to both actor and door behavior ingame, as well as a message for static overload, actor overload, door overload, etc. In Kaiser's extremely old thread about Console Doom Hacking, he stated that the IWAD address of Jaguar Doom was at 0X4000 in the ROM. Upon doing a search in Jaguar Wolf 3D, this port ALSO has an IWAD, and it starts at 0X2000 in the ROM. The difference in values is likely due to Jag Doom being a 4 meg cartridge, whereas Jag Wolf 3D was only a 2 meg cartridge. The rest of the ROM is rather uneventful, but the end of it reveals another curiosity. Starting at Address 001ED670 is what looks very much like how a Doom IWAD file is laid out: The first "category" features a list of all the maps in game (numbered from 0-29). The second category lists out all the sprites (1-154). The third category lists out wall textures (1-36). Following that is what looks like the information for the intermission screen, followed by information for the main menu(?). Other stuff that I'm able to distinguish here include what look like the references for the 3 demos (listed as DEMO1, DEMO2, DEMO3), a list of all ingame sound effects (ex. D BONUS, D OPENDR, D FTHROW, D KNIFE) and a list of all the songs ingame. For comparison, Jaguar Doom has the list of all it's data at the end of the ROM as well, and it's arranged in a very similar way (Sprites, then textures, and ending with sound effects and music). To wrap this up, I think it can be said that Jaguar Wolfenstein 3D is a hybrid which uses elements from both the Jaguar Doom engine and SNES Wolf 3D engine. Again, I'm not sure if any of this information is common knowledge, but it is fascinating none-the-less. Any thoughts? EDIT: Fixed some grammatical errors, guess that's what happens when you post while half-asleep. :)
  15. I feel like streaming some glitchy SNES Mortal Kombat over on Mixer, come check it out if you are bored: https://mixer.com/Mattfrie1

  16. Mattfrie1

    PSX Doom HD cover art?

    Wow, nice find! I was extremely surprised to see that he was also responsible for the cover art to "Powerslave", another rather obscure FPS for the PS1/Saturn:
  17. Mattfrie1

    Doom Streams

    I'm gonna be streaming some SNES Doom from the actual hardware: https://mixer.com/Mattfrie1
  18. I consider myself extremely fortunate to have gotten a legit copy of GBA Doom II off of eBay about 5 years ago or so. It was in a lot along with Duke Nukem Advance and 007: Nightfire, and I ended up paying about 20 bucks for the entire lot. I also managed to get the original Doom and Wolf 3D for GBA around the same time for pretty reasonable prices, so I'm guessing this is before the prices on them really skyrocketed. I thought all the ports were really enjoyable. They aren't really my go-to versions to play, but they are very good nonetheless. That being said, even though I own my original Game Boy Advance I find that I get more enjoyment by playing all my Game Boy games through the Game Boy Player add-on for the Gamecube. I've never been too big a fan of portable gaming, so the Game Boy Player gives me a chance to play these games without having to strain my eyes.
  19. Hmm, that's pretty interesting since MacWolf was coded by Burger Becky and was released AFTER both SNES and Jaguar Wolf 3D. It pretty much seems like Carmack back-ported the game behavior of Wolf 3D into the Doom engine to make this version work from what I can tell so far. The GBA version of Wolf 3D was actually handled by ONE programmer. Pretty crazy that it's the most accurate of all the ports as well...
  20. Did you also have Cybermorph and Kasumi Ninja by any chance? Those were the other two games with the listing. I bought it on eBay earlier this month, and was primarily interested because the listing included Doom, Wolf 3D and the composite cable (most other listings only had the RF cable, which mine also came with).
  21. Looking into the "IWAD" data at the end of the ROM a little bit more, I've also managed to figure out that the definitions for each of the midi "instruments" appear to be stored right at the end after the music. Along with that, there also appears to be several color palettes scattered about around as well, including RGBPALS, CRYPALS, PALMAP, and BRIEFPAL. I also see what looks like the info for BJ's face in the status bar (FACE 1-25, plus FACEL and FACER as well), and also the definition for the logo screen at the start of the game (called BALLMAP).
  22. Mattfrie1

    Doom Streams

    Gonna be streaming some PSX Doom from the actual hardware on Mixer (formerly Beam), come check it out: https://mixer.com/Mattfrie1
  23. Not too often honestly. I played some Skulltag a little bit back in the day before it folded but that's about it. I've been meaning to re-download Zdaemon to get back into the hobby though.
  24. http://steamcommunity.com/id/mattfrie64 I don't have too many games at the moment, but I do play the first three Quake's every now and then.
  25. Mattfrie1

    Roger Moore dead at 89

    Roger Moore was also great in 'The Saint' television series (Not to be confused with the terrible late 90s movie remake). If you enjoyed his Bond films, then I would highly recommend watching the series: