DRD Team

I have noticed that the ThrustThingZ physics has changed recently within the dev-builds, to where the players current momentum before ThrustThingZ takes effect - gets reset to nothing automatically.

Due to over-flowing exams and a lot of things going on, I couldn't give you a stripped down example. I hope a 30MB will be fine, otherwise - I don't know when I'll be able to make such a PWAD.

File: TGRDM3
Instructions:

• Load GZDoom [1514-gf2f3fa6] with TGRDM3 archive data file
• Goto: MAP MAP04
• Goto Coordinates in the Cartesian plane: (134, 2049, -48)
  • There is more jumping pads that behave this way as-well, but this alone is obvious. But if needed, I can also provide them - when asked.
• Face the white sparkly jumping pad
• Run towards it and notice the players momentum isn't applied once ThrustThingZ takes effect.
• Notice the differences when using GZDoom 2.1.1 when it comes to that very same jumping pad.

fixed.

But why are you so in love with those sector actions? That part of the map was nearly impossible to analyze due to them.
And the bug wasn't with ThrustThingZ but with ThrustThing, which was also buried in the mess of sector actions in those sectors.

Graf Zahl wrote: fixed.

Thanks!

Graf Zahl wrote: But why are you so in love with those sector actions? That part of the map was nearly impossible to analyze due to them.
And the bug wasn't with ThrustThingZ but with ThrustThing, which was also buried in the mess of sector actions in those sectors.

There's part of the physics that I purposely exploit - and in this project they are used for achieving secrets. When using those exact triggers, you can jump on them to reach nearly *2 of the Z-height. However, if I use a script, that behavior does not work. I can make a video demonstrating this if you would like to see it.
Aside from that, I also hit a snag with the ACS arguments limitations.