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

SaladBadger

Members
  • Content count

    1349
  • Joined

  • Last visited

About SaladBadger

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. SaladBadger

    Chocolaate Doom crashed on Chex Quest

    There are a fair amount of visplane overflows possible in the last level boss arena. All I can recommend is not looking into the main area when too many doors are open at one moment.
  2. SaladBadger

    Which game currently destroys you?

    I think I've played Descent long enough that I'm completely used to it's bullshit. Even the sluggish turning isn't too bad for me (though maybe I should finally get a good flight stick for constant turning...) A zero life loss run on even Hotshot is out of my grasp, but I can beat the game pretty effectively on Ace at this point. The later skills are odd because while you're much more likely to die, you're almost always getting at least one extra life every level simply due to the skill level based modifier applied at the end of each level. It kinda reminds me of an early arcade game, though much more generous with the 1-ups.
  3. SaladBadger

    Differing id Tech 3 consoles

    Licensees of the engine have full reign over the engine and can transform it how they want. All id ever did with the console officially was create the simple one. I wouldn't be surprised if the developers of MOH:AA spent time creating a new UI library and they decided to make the console use it for convenience. It was in style, Unreal Tournament did it, the steam versions of HL did it.
  4. SaladBadger

    Doom 0.5 reverse engineering project

    I made a replica of romero's map a while back, so I could probably convert it to alpha format and look at it. Sadly a lot of the maps shown in screenshots are somewhere in between the various alpha releases we have (which is annoying, since the screenshot set that shows one of the first ever maps made with the sector iteration algorithm has a lot of flats that are not present anywhere in any released data set) From looking at the images though, it's possible to see where the problems lie. The ring structure would be stepped into by either 2 or 3 portals based on how you're looking at it. Based on your view angle, the portals within the rings would be stepped into multiple times (IE, if you were staring into the ring dead on from a cardinal direction, I could see there being five iterations into the second step depending on perspective). Stepping into a sector multiple times isn't always too bad, since lines that weren't clipped by the left/right bounds should be cached, but any that were rejected in a previous step will have to be reprojected again. EDIT: Just looking at E1M8 in the Alpha confirms some of the things I was thinking. Indeed, the innermost steps are entered 5 times each.
  5. SaladBadger

    Doom 0.5 reverse engineering project

    Trying some ways to visualize the recursive rendering for the Article I Want to Write On The Alpha Doom Renderer. I think this works out quite nicely, and indicates some of the fun aspects of the recursive stepping problems John Romero brought up, like how sector 10 is stepped into twice and sector 1 is stepped into 4 times in this view. The lines that appear before each iteration are the clipping bounds for that pass.
  6. SaladBadger

    Shooting Down Revenant Missiles

    it was mentioned the last time this came up, but giving the projectile enough health to survive a hit doesn't work because whatever shoots the projectile first will claim ownership of the projectile because of the reused target field. Maybe you can implement maes idea of capturing revenant projectiles as "shields", but that's probably not the intended idea here. It's generally safest to just give them 1 HP so they die instantly.
  7. SaladBadger

    idgames archive problem with google chrome

    web browsers aren't the only things capable of downloading from a FTP server. Specialized FTP clients like Filezilla are still a thing if you need to download from a FTP server. Browsers are just canning it because it's not a common use for them anymore. FTP itself is a bit of a dinosaur protocol, with the web increasingly pushing for "secure by default" and FTP offering no security features whatsoever. It's not really a huge deal for a little Doom archive, but with the overall support for it plummeting, that bridge will have to be crossed at some point.
  8. In theory it should be saved relative to whatever is mapped as the user's home folder, which I guess you overridden and placed on the F drive. Usually when someone says C:\Users\<username>\whatever they do mean the home folder, but use the C:\Users as a convenience because that's what the vast majority of users use.
  9. In certain cases, I can see that. From what I understand, Doom 64 under load tended not to be as "well defined" as PC doom is (where the game will always execute tics the same regardless of whether it's running at 10 FPS or 35 FPS or whatever). Things like this though really can't be simulated effectively without emulating the entire console, which would be a lot more work, so the source code won't provide much on that front.
  10. they wouldn't have to use this, because the official port achieves demo-sync level compatibility already. It's based off of Kaiser's own efforts to reverse engineer the game.
  11. SaladBadger

    Here's an idea: Doom Builder Online

    Apparently during Doom's development Romero was playing with some NeXT features in DoomED like shared objects, which allowed for DoomED to be networked. I can't remember the source on it, but there's a story of it where one person's laying down lines while someone else is busy placing things in the level. I assume in practice it didn't get too much use, but it did exist apparently.
  12. SaladBadger

    EXE hacking

    this is some good sleuthing, but it is frustrating there's very little documentation. My own searches turned up the potential phar lap connection, but also got caught up in a red herring in the form of an obscure gcc port that also used the "xm" prefix and had a dos extender named "xm" with similarly named modules like "xmdos", but the dates on all of the files I found are from 1990, so it's too early. Phar Lap does come up a lot seeing as it's one of the earliest DOS extenders, but I don't think I've ever seen any DOS binary use it or any actual documentation on using it, so that's annoying. ed: re: floating point usage: The only floating point use I have found so far is creating the sine LUT. I haven't turned up anything that occurs in the game logic.
  13. SaladBadger

    EXE hacking

    I dunno if anyone's too interested in hacking the 0.2 and 0.3 alphas, but I've found a brute-force way to generate a flat executable that can be loaded into a disassembler. I've tried Ghidra, but it should hopefully work with IDA Locate the start of the code section (I dunno, I think it's a code section). this has the signature EB 0E 64 62 67 6F 74 6F 20 3D 6D 61 69 6E (ë dbgoto =main in ansi) Nuke every byte in the binary before the EB Add more bytes at the end for the data. How much? I dunno, there's probably a field somewhere in the header that says. I padded my executable to one meg to be safe. Load that mess up in Ghidra as a flat binary. Can specify x86, 32 bit, GCC and it seems to work just fine. Stare at that mess in the code browser. This seems to work. Mostly (I've only tested it with 0.2 atm, since that has extensive debugging symbols). The compiler and linker used for Doom 0.2 and 0.3 is weird (does anyone know for certain which compiler was used to begin with?) and seems to group string and other literals by input file with its functions, and starting the flat binary at the start at the segment seems to align accesses to these literals properly. I wanted to figure out more about the executable format itself, which would probably be vital for any extensive hacks, but I honestly couldn't make heads and tails of the dos extender binary involved. It's pretty tiny, especially compared to DOS4GW, but still beyond my scope. There are some problems I've observed with this. Some functions don't seem to get called right, and the main function isn't properly detected so it needs to be added manually, but unless I could figure out what sort of relocation data is present, this is the only way I've been able to make anything work.
  14. SaladBadger

    Doom 0.5 reverse engineering project

    I'm somewhat familiar with xttl and Quasar's work, and I remember many years ago Quasar talking about architectural differences in the pre-beta release. It's all very neat, and I admire the things the two have managed to pull off. So far as I'm aware though there's never been much work done with any of the earlier alpha versions, which is a shame since they bury lots of interesting secrets and tell a tale of the game's evolution, especially on the rendering front.
  15. https://github.com/InsanityBringer/Doom05RE I've finally gotten my Doom 0.5 RE project to a point where it's basically feature complete, so I've created a repo for it. The port I've developed is extremely barebones, and mostly exists just to verify that things are functional, but it does the job. I dunno what else to do with this. My main intentions are to write an article similar to Fabien's article on how the BSP based Doom renderer works, and try to delve deep into why the original recursive algorithm was so slow. Additionally, I'd like to also possibly port it on top of Chocolate Doom's gameplay code and see if it would be possible to make it work with features like Build-like moving sectors. In practice, any serious port would be better off adopting Eternity like portals and clever use of portals and polyobjects for complicated moving things, but it might be neat to see what was originally possible. Beyond that, there's not much of interest in an engine derived from alpha-quality game code, beyond being a time capsule of what Doom's code was once like.
×