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

Shadow Hog

  • Content count

  • Joined

  • Last visited

About Shadow Hog

  • Rank
    Senior Member

Recent Profile Visitors

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

  1. Shadow Hog

    4800 Hell Knights. We dumb, MegaBlast smart. Alpha 3

    (I have no idea how y'all are doing those name highlights.) Watching MegaBlast's first stream made me suddenly realize the smaller spotlights in my map were completely non-functional. I'm somewhat impressed you were still able to navigate that mess with half the lights that were supposed to navigate you not being present! It turns out that the name of my decoration, "Spotlight", is now reserved for an actual built-in GZDoom object, when that hadn't been the case when I made the map. Whoops. Well, better we find that out now than later, so I can more readily fix it! Basically, whoever it is that's in charge of compilation at this point is gonna need to change the end of the DECORATE file from to I've also updated the PK3 on my Dropbox, if you'd rather copy it from that. Same URL as before, but here it is again anyway.
  2. Shadow Hog

    4800 Hell Knights. We dumb, MegaBlast smart. Alpha 3

    The mapset's designed for GZDoom, though.
  3. Shadow Hog

    Glitched skies in prboom

    I'm pretty sure you can use a texture of any size for the Replace Sky linedef special...
  4. Shadow Hog

    Glitched skies in prboom

    Looks to me like you might be using patches greater than 255 pixels tall? At least, I vaguely recall tutti-frutti appearing when I cross over to anything 256 pixels or taller. Gotta break it up into multiple patches of 128 pixels tall in that case. Of course, I'm not 100% sure if that's the case for the latter image, which I think is just a stock Plutonia sky. Not entirely sure what went wrong there; I'd guess that it was >256 pixels wide (another barrier for patch size, though unlike height, 256 pixels is non-inclusive for causing the bug and is, in fact, the recommended maximum width), but I don't believe that texture is wider than 256 pixels? (I don't have Plutonia on-hand to check it, I'm at work.)
  5. Shadow Hog

    4800 Hell Knights. We dumb, MegaBlast smart. Alpha 3

    Which my map does, so good luck with Zandronum. It might still be completable; I forget if I put any switches behind portals. I kinda suspect I did, though, in which case you can't win without noclip.
  6. Shadow Hog

    4800 Hell Knights. We dumb, MegaBlast smart. Alpha 3

    I always just figured it'd stick with the original thread title, 150 Hell Knights and a Megasphere. Sort of like how Snakes on a Plane stuck with that title.
  7. Shadow Hog

    Neural nets sort of generate Doom maps but not really

    Don't forget nuts.wad, gotta have it learn that more monsters = better monsters
  8. Shadow Hog

    4800 Hell Knights. We dumb, MegaBlast smart. Alpha 3

    After a cursory look over what your PK3 has, here's a few steps to make things a bit better (though I make no guarantees that this is everything that needs fixing, cuz I'm at work): First off, delete my PK3 from within your PK3. You've already extracted its contents and put them in the root of your own PK3; there's no reason to put the PK3 itself in there as well. It'll never be read, so you're just bloating the file size. Second off, remove any content inside the map WADs that isn't a map lump (so keep the header, SECTORS, LINEDEFS, etc., but not the rest). Move it to the relevant folder of your PK3 as needed if you haven't already. Be sure to rename things as needed (since I can already see two separate D_RUNNINs, each in their own map WAD, and that's not gonna do). Third, make sure the name of the map header inside the map WAD matches the name of the map WAD it's in (so MAP02.WAD needs to have MAP02 in it; you can't have MAP02.WAD contain MAP01). They don't have to fit the "MAP##" format, given this is a ZDoom mapset. If there's more than one map inside a map WAD, split it into multiple map WADs such that each map is its own WAD. That should help your PK3 be more well-formed than it currently is.
  9. Shadow Hog

    Post your Doom video! [but don't quote video]

    I got bored last night while adding loop points to a MIDI I was gonna use in a project.
  10. Shadow Hog

    "UMAPINFO" discussion

    Belated response, but yeah, it looks like it's the curly-brace syntax that was settled upon. Graf's SVN has a listing of all the tags that are implemented, as far as I know.
  11. Shadow Hog

    "UMAPINFO" discussion

    I know that stable releases of [G/Q]ZDoom have had it in place for a while now. I'm not sure if anything else has implemented it; people aren't really using it yet, though I'm not sure if it's because they don't care, or if they're waiting for broader support from Boom-format engines (who are probably waiting for maps that require it to force their hand, creating a bit of a Catch-22).
  12. Shadow Hog

    Any cool mods?

    No. There are absolutely no cool mods for Doom. None whatsoever. (But really go check out Samsara or ww-cola or Reelism or something I dunno)
  13. Shadow Hog

    Wavy Water

    Also, you could put the water on a 3D floor, and then use Ceiling_Waggle on the 3D floor's control sector to have it bob up/down. Almost certainly not what you were asking for, but it's an extra thing ya can do if ya want. Could even make it swimmable while you're at it.
  14. In which case, we only need to make 77.44 maps in order to reach 1.21 gigawads. Great Scott!
  15. Obviously, given we're using SI notation, we need to start using it correctly. Ergo, a WAD can only be called a MegaWAD if it contains 1,000,000 maps. If it contains 1,000,000,000, it is a GigaWAD. 1,000,000,000,000 is a TeraWAD. For map counts that are more likely to be seen in reality, 1,000 is a KiloWAD, 100 is a HectoWAD, and 10 is a DecaWAD, with 32-map WADS being just over three DecaWADs large.