Floors/ceilings moving to incorrect floor/ceiling height in Crispy Doom

[Stupid Bunny]

I've once again resumed work on my Map Project That Will Not Die, and from the beginning I've been set on making it compatible with as many limit-removing sourceports as I can.  Unfortunately I've found that on one map in particular there are a number of features that don't work properly when I test the map in Crispy Doom--although it works fine in PrBoom+ and GZDoom, at least.

 

In two separate spots on the map, sectors tagged with 40-W1 Ceiling Raise to Highest Ceiling will continue to rise way higher than any adjacent sector; they do eventually stop, although I can't tell where or what they're actually rising to.

 

In another instance, a sector tagged with 102-S1 Floor Lower to Highest Floor will not slowly lower to the floor, like it's supposed to, but instead instantaneously rise to some unknown point way inside the ceiling that, again, corresponds to no adjacent sector that I can see.

 

Is this just a bug with Crispy Doom?  Should I be testing this with a different limit-removing port?  Or is there something else I actually need to fix?

 

I haven't seen this happen in any of the other maps in the WAD but I'll keep poking around to see what else breaks.

[TimeOfDeath666]

For those linedef actions in vanilla compatibility, the ceiling will only raise until its height is 0 or higher, and the floor will only move until its height is -500 or higher, so I would select all sectors and raise their ceiling/floor heights until it works.

Edited December 14, 2020 by TimeOfDeath666

[Stupid Bunny]

Thanks, that did it.  I guess this is what happens when basically the entire map is deep underground.  Amazing the things I'm still learning after all these years.

 

I've got a problem to fix with floors lowering and not changing textures now, but I think I've found an answer to that in another thread.