Difference between revisions of "Engine bug"
From DoomWiki.org
[checked revision] | [checked revision] |
(I've recently found this when playing a demo. It occurs with the pistol (and maybe other weapons) and appears on the screen for only a fraction of a second. I might need to do a slow-motion video.) |
|||
(18 intermediate revisions by 6 users not shown) | |||
Line 15: | Line 15: | ||
** The Doom engine includes few safeguards against [[Wikipedia:Arithmetic overflow|''overflow'' conditions]]. | ** The Doom engine includes few safeguards against [[Wikipedia:Arithmetic overflow|''overflow'' conditions]]. | ||
** Line-of-sight calculations, [[Doom rendering engine|rendering]] algorithms, and the [[Doom rendering engine#Node building|BSP tree]] are also susceptible to [[Wikipedia:Floating point#Accuracy problems|''roundoff'' errors]]. | ** Line-of-sight calculations, [[Doom rendering engine|rendering]] algorithms, and the [[Doom rendering engine#Node building|BSP tree]] are also susceptible to [[Wikipedia:Floating point#Accuracy problems|''roundoff'' errors]]. | ||
− | ** The engine imposes a number of ''static limits'' on [[Thing]] placement and map construction, which sometimes fix one problem by creating another. | + | ** The engine imposes a number of ''[[static limits]]'' on [[Thing]] placement and map construction, which sometimes fix one problem by creating another. |
* '''Fatal''' bugs are those where the engine crashes (often with the [[Venetian blind crash|Venetian blind]] effect) or else exits the game in a controlled fashion, usually with an [[error message]]. '''Y*''' means that termination is possible, but not inevitable. '''N*''' means that the program keeps running, but that rendering or character behavior may be sufficiently compromised that meaningful gameplay becomes impossible. | * '''Fatal''' bugs are those where the engine crashes (often with the [[Venetian blind crash|Venetian blind]] effect) or else exits the game in a controlled fashion, usually with an [[error message]]. '''Y*''' means that termination is possible, but not inevitable. '''N*''' means that the program keeps running, but that rendering or character behavior may be sufficiently compromised that meaningful gameplay becomes impossible. | ||
Line 41: | Line 41: | ||
! N | ! N | ||
! Y | ! Y | ||
+ | |- | ||
+ | | [[Absurd texture name in error message]] | ||
+ | | Undisputed | ||
+ | | Algorithm | ||
+ | ! Y* | ||
+ | ! N | ||
+ | ! N | ||
+ | ! N | ||
|- | |- | ||
| [[AASTINKY|AASTINKY and AASHITTY]] | | [[AASTINKY|AASTINKY and AASHITTY]] | ||
Line 59: | Line 67: | ||
|- | |- | ||
| [[Arch-Vile fire spawned at the wrong location]] | | [[Arch-Vile fire spawned at the wrong location]] | ||
− | | | + | | Undisputed |
− | | | + | | Typo |
! N | ! N | ||
! N | ! N | ||
Line 105: | Line 113: | ||
! N | ! N | ||
! Y | ! Y | ||
+ | |- | ||
+ | | [[Blockmap overflow]] | ||
+ | | Undisputed | ||
+ | | Overflow | ||
+ | ! N | ||
+ | ! N | ||
+ | ! N | ||
+ | ! N | ||
|- | |- | ||
| [[Broadcast packet meltdown]] | | [[Broadcast packet meltdown]] | ||
Line 187: | Line 203: | ||
|- | |- | ||
| [[Elastic collisions with walls]] | | [[Elastic collisions with walls]] | ||
− | | | + | | Undisputed |
− | | | + | | Roundoff |
! N | ! N | ||
! N | ! N | ||
Line 212: | Line 228: | ||
| [[Final Doom teleporters do not set Z coordinate]] | | [[Final Doom teleporters do not set Z coordinate]] | ||
| Undisputed | | Undisputed | ||
+ | | Algorithm | ||
+ | ! N | ||
+ | ! N | ||
+ | ! N | ||
+ | ! N | ||
+ | |- | ||
+ | | [[Firing frame position not updated when the player dies]] | ||
+ | | | ||
| Algorithm | | Algorithm | ||
! N | ! N | ||
Line 456: | Line 480: | ||
! N | ! N | ||
! N | ! N | ||
+ | ! N | ||
+ | |- | ||
+ | | [[Manual doors on 1S lines cause an illegal operation]] | ||
+ | | Undisputed | ||
+ | | Linedef | ||
+ | ! Y* | ||
+ | ! N | ||
+ | ! Y | ||
! N | ! N | ||
|- | |- | ||
Line 605: | Line 637: | ||
| | | | ||
| | | | ||
+ | ! N | ||
+ | ! N | ||
+ | ! N | ||
+ | ! N | ||
+ | |- | ||
+ | | [[Pause bug in menus with scroll bars]] | ||
+ | | Undisputed | ||
+ | | Algorithm | ||
! N | ! N | ||
! N | ! N | ||
Line 682: | Line 722: | ||
! | ! | ||
|- | |- | ||
− | | [[PWAD size limit] | + | | [[PWAD size limit]] |
| Undisputed | | Undisputed | ||
| Algorithm | | Algorithm | ||
Line 704: | Line 744: | ||
!N | !N | ||
!Y | !Y | ||
+ | !N | ||
+ | |- | ||
+ | | [[Random sound pitch removed]] | ||
+ | | | ||
+ | | | ||
+ | !N | ||
+ | !N | ||
+ | !N | ||
!N | !N | ||
|- | |- | ||
Line 712: | Line 760: | ||
! N | ! N | ||
! N | ! N | ||
+ | ! Y | ||
+ | |- | ||
+ | | [[Blast damage#Non-reentrancy|Recurrent blast damage]] | ||
+ | | Undisputed | ||
+ | | Algorithm | ||
+ | ! N | ||
+ | ! N | ||
+ | ! S | ||
! Y | ! Y | ||
|- | |- | ||
Line 719: | Line 775: | ||
! Y | ! Y | ||
! Y | ! Y | ||
+ | ! N | ||
+ | ! N | ||
+ | |- | ||
+ | | [[Revenant tracers desync internal demos]] | ||
+ | | Undisputed | ||
+ | | Algorithm | ||
+ | ! N* | ||
+ | ! N | ||
! N | ! N | ||
! N | ! N | ||
Line 760: | Line 824: | ||
! N | ! N | ||
! Y | ! Y | ||
+ | ! N | ||
+ | |- | ||
+ | | [[Secret#Bugs|Secret sectors appear or disappear]] | ||
+ | | | ||
+ | | Algorithm | ||
+ | ! N | ||
+ | ! N | ||
+ | ! S | ||
! N | ! N | ||
|- | |- | ||
Line 774: | Line 846: | ||
| Static limit | | Static limit | ||
! N | ! N | ||
+ | ! N | ||
+ | ! N | ||
+ | ! Y | ||
+ | |- | ||
+ | | [[Single-use line actions can fail]] | ||
+ | | Undisputed | ||
+ | | Algorithm | ||
+ | ! N* | ||
! N | ! N | ||
! N | ! N | ||
Line 909: | Line 989: | ||
| Disputed | | Disputed | ||
| Algorithm | | Algorithm | ||
+ | ! N | ||
+ | ! N | ||
+ | ! Y | ||
+ | ! N | ||
+ | |- | ||
+ | | [[Starting on a vertex between visplanes causes illegal memory access]] | ||
+ | | Undisputed | ||
+ | | | ||
! N | ! N | ||
! N | ! N |
Revision as of 18:40, 16 September 2014
A Doom engine bug is a limitation or an oddity present in the Doom engine. For errors in map design, even those related to a specific item below, see the article about that map.
Note that playing with a source port may, while removing some or even the majority of the bugs listed below, introduce other bugs which are not listed here (although details may be present in the article about the source port in question).
Key
This table classifies anomalies in a very broad way; see the individual articles for details.
- Canonicity — A bug is verified only when a current or former id Software programmer has called it a bug in a public medium. An unverified bug may still be undisputed if it is generally accepted as an error or issue by the fan community under a consensus involving thorough playtesting and research on the corresponding phenomenon and any associated binaries or source code. A bug is disputed if it can be argued to be a harmless and possibly intentional feature.
- Cause — The general category of underlying problem:
- Most bugs are due to algorithms which fail to account for all possible inputs, apply conditional statements in an illogical sequence, or have unforeseen consequences in particular game situations.
- A few of these arise from simple typos in the source code.
- Improperly constructed linedefs (with orphaned tags or incorrectly placed textures) or sectors, can also induce various strange behaviors.
- The Doom engine includes few safeguards against overflow conditions.
- Line-of-sight calculations, rendering algorithms, and the BSP tree are also susceptible to roundoff errors.
- The engine imposes a number of static limits on Thing placement and map construction, which sometimes fix one problem by creating another.
- Most bugs are due to algorithms which fail to account for all possible inputs, apply conditional statements in an illogical sequence, or have unforeseen consequences in particular game situations.
- Fatal bugs are those where the engine crashes (often with the Venetian blind effect) or else exits the game in a controlled fashion, usually with an error message. Y* means that termination is possible, but not inevitable. N* means that the program keeps running, but that rendering or character behavior may be sufficiently compromised that meaningful gameplay becomes impossible.
- A bug has a workaround if it can be avoided by reasonable compromises in map design, such as when matching every linedef tag to at least one sector, but not when removing invulnerabilities from every level containing a sky texture, or also by convenient precautions and other measures taken by the program user, such as when increasing the mouse sensitivity through the configuration file directly, instead of using the menu. S means that the bug can be avoided only by making one's map smaller or less complex.
- A bug is a loophole if it can be abused to the player's advantage (especially during speedruns or deathmatches).