You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Have you checked that no other similar issue already exists?
I have searched and not found similar issues.
A clear and concise description of what the bug is.
After filing #2830 , I realized this is not just for silent teleports in myhouse.pk3 but for regular teleports in vanilla Doom. I tested the original doom2.wad, the BFG doom2.wad, enhanced doom2.wad, and kex doom2.wad. Walking into a teleport does not trigger them immediately, but instead keeps you in the same location usually. Walking back and fourth through them, or with momentum sometimes randomly does trigger the teleport, but this seems to happen entirely random.
Steps to reproduce the behaviour.
Explain how to reproduce
Launch any vanilla Doom2 wad (original, BFG, enhanced, kex)
Go to MAP04
Walk through the teleporters in the end of the map
Your configuration
completely vanilla config, not even key bindings
Provide a Log
No response
The text was updated successfully, but these errors were encountered:
GZDoom version
4.14.0
Which game are you running with GZDoom?
Doom 2
What Operating System are you using?
Linux ARM (Raspberry Pi)
Please describe your specific OS version
Debian 13 (trixie)
Relevant hardware info
Apple M2
Have you checked that no other similar issue already exists?
A clear and concise description of what the bug is.
After filing #2830 , I realized this is not just for silent teleports in
myhouse.pk3
but for regular teleports in vanilla Doom. I tested the original doom2.wad, the BFG doom2.wad, enhanced doom2.wad, and kex doom2.wad. Walking into a teleport does not trigger them immediately, but instead keeps you in the same location usually. Walking back and fourth through them, or with momentum sometimes randomly does trigger the teleport, but this seems to happen entirely random.Steps to reproduce the behaviour.
Explain how to reproduce
Your configuration
Provide a Log
No response
The text was updated successfully, but these errors were encountered: