Difference between revisions of "Noclip bug"
From DoomWiki.org
| [checked revision] | [checked revision] |
m (Fix compet-n link) |
m (→External links: fix link to old site) |
||
| Line 6: | Line 6: | ||
==External links== | ==External links== | ||
| − | *[http://www.doom2.net/ | + | * [http://www.doom2.net/compet-n/index.cgi?action=nostalg&page=e3m1 Compet-N page about the "E3M1 shotgun trick"] |
| − | *{{competnftp|tnt/speed/ev31-030.zip|A demo from the Compet-N database illustrating a more typical encounter with the noclip bug}} (See the file BLOOPER1.LMP) | + | * {{competnftp|tnt/speed/ev31-030.zip|A demo from the Compet-N database illustrating a more typical encounter with the noclip bug}} (See the file BLOOPER1.LMP) |
[[Category:Errors and bugs]] | [[Category:Errors and bugs]] | ||
[[Category:Doom engine]] | [[Category:Doom engine]] | ||
Revision as of 04:09, 25 February 2017
The noclip bug can occur whenever the player crosses a tagged linedef (e.g. a teleporter, a trap which opens or closes a door, or a trigger for a lift) while moving at a very high speed (such as Strafe50, or through Wallrunning). The player moves fast enough that the game engine never detects the line trigger as having been crossed.
This anomaly has occasionally been exploited in speedruns as a time-saving tactic (i.e. by recording many abortive demos of the same level until the bug occurs in the desired location).
This should not be confused with a separate bug which causes W1 linedefs to fail activation due to their target sector being busy when crossed. See Single-use line actions can fail for information on that phenomenon.
