JAMAL JONES TRILOGY - Old development thread - [Doomkid's 20 Years Mapping Contest]

My map is finally ready for playtesting!

Title: Charred Remains

Slot: MAP13

Music: Bleeding Grounds by Jimmy

Tested on: GZDoom, PrBoom+, Chocolate Doom

Skill levels implemented.

Download

Screenshots:

Made a quick update fixing up some stuff, mainly including the teleport closets, and also extending the exit.

https://doomshack.org/uploads/Running_Down (quick update).wad

On 9/18/2022 at 3:52 AM, jacnowak said:

And just as an interesting curiosity (and maybe advice for people making vanilla maps so that they don't make the same mistake as me):

I used "zokumbsp - Optimize for vanilla" build configuration in Ultimate Doom Builder...

Don't do that :)

Unfortunately it passes "z=0" argument to ZokumBSP which according to its documentation does the folllowing:

 

"This option produces a smaller blockmap. This works flawlessly, in fact
better, when maps are played in the original engine and Chocolate Doom. There
is however a known bug in some ports, like MBF, and those based on this port
where a poor optimization will skip this header without actually checking that
it is a zero-header. Such ports will have very faulty collission detection in
every area in the map. If one is aiming for newer ports where this has been
fixed, classic Doom or Chocolate Doom, this option is generally safe. There is
a fix for this header in newer versions of the Eternity Engine. GZdoom
generally ignores the blockmap, and should work fine with or without this
option."

 

It was working fine for me as I was testing in Crispy, Eternity and GZDoom.

It looks that the bug has also been fixed in DSDA-Doom.

But I checked with prBoom+ 2.5.1.4 and the map indeed has a ton clipping issues everywhere...

 

Sorry for the trouble @Doomkid  - hopefully it's not too late to apply the fix!

E1M13_damneddam.zip

Just now saw this post - it’s no trouble at all, good job identifying what happened!

Here's my review / thoughts on the new map (UV)!

MAP13: Charred Remains - @ChippiHeppu

Thank you for the feedback @Arsinikk! I went back and addressed the issues.

The Google Drive link has been updated with the latest version.

This is a really good map, I'm very pleased with the quality maps everyone is submitting!

@NiGHTS108 and @NeedHealth, it's no rush at all, but just wanted to check on your map progress.

Sorry for keeping you waiting so long DK, I'm kinda a massive procrastinator but I can promise I'll have the map done by the deadline!

Anyway here's a screenie of MAP17: Thunder Siege

Really cool looking map there, NiGHTS! As only you and NeedHealth haven’t submitted a map yet, don’t stress about meeting the exact deadline. Everyone else has a basically-complete map submitted so most of the hard work is done!

After your maps are in, I can get to the more nitty-gritty stuff like final bug fixes, creating a MAPINFO for custom skies in some maps, and making minor changes to each episode’s DeHackEd for map names and story screens. Then this wad trilogy will be just about complete! 

Hi all,

Did a quick sweep through my map and tided up some textures and crusher linedef actions.

I think it's help create a better ambience.

https://wadhosting.com/Wad/C3990412F98590CD982BAB2995F44B70176698DF

Cheers,

That's really messed up. Is this something a sourceport developer supposed to address or rather the person behind ZokumBSP?

This is far from the first time I've experienced this issue as well.

Second version. Fixed all known bugs

no_man_village_v2.rar

14 hours ago, Firedust said:

That's really messed up. Is this something a sourceport developer supposed to address or rather the person behind ZokumBSP?

I think build configuration supplied with Ultimate Doom Builder should have this flag removed. It is misleading as it says "Optimize for vanilla" so it's easy to assume it's the best option to choose whenever you are making a vanilla map. And this is not the case. In fact, the only scenario I can think of when you would want this flag on is when you hit blockmap limit - you can go a bit further with your map size when you switch this on, at the expense of compatibility with some ports. In all other cases it doesn't make sense to set it, particularly when you are making a vanilla map because you want maximum compatibility. But there is nothing wrong with ZokumBSP offering this optional flag. It's turned off by default and documented.

Technically it is a bug that source port developers should address - the bug has been introduced in MBF so all ports that derive from it have it unless they fixed it. Eternity and DSDA-Doom fixed it, GZDoom is not affected at all as it has its own blockmap handling, not sure what is the status of Woof! or Doom Retro for example. But we can't expect this to be fixed in ports that are no longer actively developed and some people use those and they logically assume that vanilla maps should work in them as vanilla maps should work in every port.

I've done quit a bit of rebalancing for my map, gonna post a complete update of the whole project soon with all the latest maps included to make further playtesting and bugfixes that much easier to find.

@NiGHTS108 and @NeedHealth, could I get an update on where each of you are at with your map? Again not rushing, I'd just like to see/hear what you've got cooking so far :)

EDIT: Here's that new beta I promised! https://doomshack.org/uploads/JamalJones_ver_5_WIP.zip

Hey man, I'm not sure exactly how to increase compatibility of my map with other ports (the issues with your DSDA playthtough vs. my GZdoom playtesting leading to faulty doors, etc.). 

What are the main issues usually, considering my map is in Doom II format, with no ACS coding or other Vanilla incompatible resources (ignoring visplane limits)?

Thanks for the new beta. I'll give this a playthtough now the song is complete and I have more spare time.

Hey TVdinner, I think all that’s happened here is that some select Doom1 textures somehow got into the mix in your map, which are the ones that weren’t showing up - I can easily replace those in Doom Builder, or add the missing textures in, that’s no problem. As for things not working that do work in ZDoom - usually stuff left unintentionally tagged 0. ZDoom will still allow it to work unlike other ports. I think that’s all that’s wrong, the map is actually very close to being perfectly functional in all ports, last I checked!

Just a small update;

https://www.dropbox.com/s/j33ckn3lz92sk5n/Peyote ugly.3.wad?dl=0

I have moved some ammo around as per the suggestion made above that gave away the final fight. I had left this update to see if any other suggestion were going to be made to improve this. Unless there are some unexpected issues then this could be close to the final version.

On 10/5/2022 at 2:57 AM, Doomkid said:

only 2 maps shy

Minor update: Yeah, I'm getting there, you ever have this banger idea for a map but then just have no time with UDB? That's me right now

3 hours ago, Doomkid said:

Hey TVdinner, I think all that’s happened here is that some select Doom1 textures somehow got into the mix in your map, which are the ones that weren’t showing up - I can easily replace those in Doom Builder, or add the missing textures in, that’s no problem. As for things not working that do work in ZDoom - usually stuff left unintentionally tagged 0. ZDoom will still allow it to work unlike other ports. I think that’s all that’s wrong, the map is actually very close to being perfectly functional in all ports, last I checked!

That makes sense. My first experience of Doom was the PS1 version, which came with Doom 2, Master Levels, TNT and Plutonia, with Doom on another disk I think.

Until a few months ago, I always thought all those maps were part of, or expansions of the original game, so added them all as resources when building the map.

If you'd rather replace the textures to have it  with Doom 2 textures only, I'm fine with that. Whatever is easiest for you mate.

I'll keep the sector tags in mind when designing maps in the future, thanks.

I don't have much time or energy to code much these days, but I do try to provide a bit of 'support' for zokumbsp when people encounter issues.

In more recent versions I have set most of the potentially troublesome options in zokumbsp as disabled as the default setting. This includes some things that Zennode had on as default. The tool should now act more like other node builders in that regard.

As for the vanilla-compatible, that's a bit more complex. The vast majority of ports have poor compatibility with vanilla doom2.exe. The ports will run doom2.wad and doom.wad etc just fine, but they will often fail on custom maps. They're only vanilla compatible on the smaller feature set used in the original games. They are basically vanilla wads compatible, not vanilla executable compatible nor fully pwad compatible.

I have a fair amount of unpublished data about very esoteric stuff that is broken in some ports. It's not in any file or sensible format, I just managed to trigger weird behavior with test maps. I did publish one map set, Block Rocking Bytes to let port authors test more advanced blockmap stuff that doom2.exe handle just fine.

The nasty blockmap bug was added in Boom or MBF and it is clearly a bug (faulty optimization). Maps built with that setting in zokumbsp work on a lot more ports if you turn on some sort of compatibility setting. Without the fix/compatibility setting on, there's a good chance that vanilla lmp demos will desync, so any setting you use for demo playback should work better with these blockmaps. I think PRBoom(+) has settings that allow you to play the maps just fine.

You can find posts and probably web pages that describe why the bug happens in boom/mbf-derived ports and why they most likely added this piece of code.

Update: Should have map done in the next few days (For real this time, sorry DK)

Something tells me @NeedHealth went silent since Sep 9th. Wonder where they've gone?

If they don't respond soon, somebody else might have to take their place.

On 10/26/2022 at 7:36 PM, Vladguy said:

Something tells me @NeedHealth went silent since Sep 9th. Wonder where they've gone?

If they don't respond soon, somebody else might have to take their place.

I'm available in case if no one else want. I'm checking posts almost daily, but sign in only to write something.

On 10/26/2022 at 2:35 PM, NiGHTS108 said:

Update: Should have map done in the next few days (For real this time, sorry DK)

 

Second update: I may or may not be a day or two late but it is genuinely just about done, all I need to do is get one small area finished and then I'll be handing this to you and some playtesters, again sorry for holding this up big time

Don’t worry, you’re not holding anything back! I felt kinda garbage last week and I’ve been working out of town this week, so I’m a little backed up in terms of getting JJ stuff done.

Since NeedHealth has sadly not appeared in over 2 months (hope he’s ok…) I’m going to have to free up his slot. In the interest of doing this as diplomatically as possible, I’ll start by offering the slot to @Mark Bloom as he was the first one to express interest in making an E3 map when Cammy first floated the idea of extending the campaign :)

I would like to express my excitement in the prospect of another Mark Bloom map, considering the exceptional quality of his first one. :)

That reminds me, I have some fixes to my own map I'd like to make...

On it! Will report progress on the weekend. I'll try to do a short map resembling Gusta's PL2 maps.

Hey @Doomkid, just noticed that in Beta 5 the old version of MAP14 is used. Could you fix that? Thanks.

12 hours ago, Mark Bloom said:

On it! Will report progress on the weekend. I'll try to do a short map resembling Gusta's PL2 maps.

Sounds really cool!

The layout is almost done, then detailing and placing stuff. @Doomkid Is "KeenDie" state is unused? I cannot use tag 666 to open doors? Not that it'll stop me, I'll just have to re-arrange some switches, but with Keens it'll be much easier