Forum rules Please construct and post a simple demo whenever possible for all bug reports. Please provide links to everything.
If you can include a wad demonstrating the problem, please do so. Bug reports that include fully-constructed demos have a much better chance of being investigated in a timely manner than those that don't.
Please make a new topic for every bug. Don't combine multiple bugs into a single topic. Thanks!
I was playing Vanguard with GZDoom 4.11.3 and noticed some walls were refusing to lower when either activated by a walkover line or a switch. This looks very strange and softlocks the player by making areas of the map inaccessible.
Spoiler:
See these screenshots - the first one shows that these sectors in Vanguard MAP02 are not lowering, with Imps stuck in the ceiling, perhaps causing the sectors to be jammed.
This occurs in other places such as this square area also in MAP02, that has a vital switch in it needed for progression.
Similar deal to this area in Vanguard which is meant to lower to reveal a Yellow Key with a mancubus on it, problem being... it doesn't.
You can hear the wall lowering sound by standing close to these sectors, but they won't move.
In all of these examples, it appears that the blockage is caused by monsters being too close to the lowering sector.
On further inspection, compatflags is also a factor because I was in Boom compatibility mode when this happened. Changing the compatflags will cause the sectors to react differently. Changing the compatflags from Boom to Doom (Strict) makes the sector on the right lower, but not the left, with the Imp slightly closer to the wall.
This only seems to happen with Doom and Doom (Strict) modes. (It was happening consistently for Boom format too, but I checked it again on Boom compat and couldn't replicate it, but I CAN replicate it when in Doom Strict compat. Yeah, I don't know.)
Spoiler: My Computer Specs
------------------
System Information
------------------
Time of this report: 1/19/2024, 22:57:10
Machine name: DESKTOP-8FOLNH1
Machine Id: {B9C00BC0-6ED1-4DFE-99E7-4C46A7211125}
Operating System: Windows 10 Home 64-bit (10.0, Build 19045) (19041.vb_release.191206-1406)
Language: English (Regional Setting: English)
System Manufacturer: To Be Filled By O.E.M.
System Model: To Be Filled By O.E.M.
BIOS: P7.30 (type: UEFI)
Processor: Intel(R) Core(TM) i5-7400 CPU @ 3.00GHz (4 CPUs), ~3.0GHz
Memory: 16384MB RAM
Available OS Memory: 16340MB RAM
Page File: 16841MB used, 3850MB available
Windows Dir: C:\WINDOWS
DirectX Version: DirectX 12
DX Setup Parameters: Not found
User DPI Setting: 96 DPI (100 percent)
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
Miracast: Available, with HDCP
Microsoft Graphics Hybrid: Not Supported
DirectX Database Version: 1.0.8
DxDiag Version: 10.00.19041.3636 64bit Unicode
Card name: Radeon RX 580 Series
Manufacturer: Advanced Micro Devices, Inc.
Chip type: AMD Radeon Graphics Processor (0x67DF)
That Doom2 MAP28 stuck floor occurred in GZDoom 4.11.0 - 4.11.3.a but only on Doom or Doom (strict) compatibility modes. It doesn't happen in the 4.12 devbuilds now.
In both Doom2 MAP28 and Vanguard MAP02 stuck floors there are items partly inside a wall on the lowering floor or on a sector next to it. The Doom2 MAP28 blocking didn't seem to occur on any other compat modes.
