Difference between revisions of "Chocorenderlimits"
From DoomWiki.org
[unchecked revision] | [unchecked revision] |
m (I guess this is it) |
|||
Line 7: | Line 7: | ||
* Number of moving platforms (see [[Moving platforms limit]]) | * Number of moving platforms (see [[Moving platforms limit]]) | ||
* Number of visible sprites (see [[Visible sprites limit]]) | * Number of visible sprites (see [[Visible sprites limit]]) | ||
− | * Number of [[openings]] | + | * Number of [[Static_limits#Openings.2FSolidsegs|openings]] |
* Number of drawsegs (see [[Seg#Drawsegs overflow|Drawsegs overflow]]) | * Number of drawsegs (see [[Seg#Drawsegs overflow|Drawsegs overflow]]) | ||
* Current number of [[visplane]]s and maximum number of them in this playing session (see [[Visplane overflow]]). As this is most commonly exceeded limit which is fatal, Chocorenderlimits increased the internal limit. | * Current number of [[visplane]]s and maximum number of them in this playing session (see [[Visplane overflow]]). As this is most commonly exceeded limit which is fatal, Chocorenderlimits increased the internal limit. |
Revision as of 02:49, 6 October 2011
This article or section is a stub. Please help the Doom Wiki by adding to it. |
Chocorenderlimits is a fork of Chocolate Doom by GhostlyDeath, designed for playtesting levels for vanilla Doom. It displays count of visplanes, drawsegs etc. to help determine if and where in the level, vanilla Doom static limits were exceeded.
What is displayed
- Player position and orientation
- Number of moving platforms (see Moving platforms limit)
- Number of visible sprites (see Visible sprites limit)
- Number of openings
- Number of drawsegs (see Drawsegs overflow)
- Current number of visplanes and maximum number of them in this playing session (see Visplane overflow). As this is most commonly exceeded limit which is fatal, Chocorenderlimits increased the internal limit.