doomretro
doomretro copied to clipboard
bradharding
[Bug Report?] Doom Retro and Barrels/Objects not getting stuck in decorations
So I have a pretty specific use case of forcing barrels and monsters to be stuck in decorations for some kind of "coding" for a MAP07 of the megawad I'm working on.
I have a set up that is very specific in the map, that if the player shoots 4 "double barrel" explosive objects, they will teleport into being stuck in a decoration around a arachnotron... and when all 4 objects are teleported and explode, the arachnotron should die causing a bridge to raise because of it being MAP07.
However in Doom Retro, the physics of barrels seem really weird and I think it's that which is causing the vanilla "scripting" to not work correctly.
Here is a video that shows the issue more in depth (also shows some other minor Doom Retro issues): https://www.youtube.com/watch?v=C8DudE6tfHk
Hey man. Thanks for the video. Just watched it through, and it's very helpful in explaining what the issues are. My first thought is there's some "unstuck" code that I borrowed long ago from ZDoom that may be causing the barrel problem. Is there any chance you could link to (or email me, if you prefer) a copy of the wad? I think that'd be the best way for me to deal with this. (Also for the random pinkie gibbing issue.)
I've sent a message via Doomworld message with the link to the WIP megawad you can use for testing.
I wanna circle around to what I think the exact issue that breaks the map07 with Doom Retro.
I think it's the way Doom Retro deals with barrels. Basically if barrels are stuck in a decoration they should be stuck even when exploding in that decoration. I think you have the barrels move around more when shot in Doom Retro.
Perhaps it may be better to come up with some MAPINFO command to turn on and off this behaviour?
Hmm... I think you may be right. Barrels are being treated the same as corpses while they explode (and in DR corpses can shift around a lot). I think I have a fix. I don't think I'll need to toggle this behavior, but I'll continue to look into it...