Editing RORDoom
From DoomWiki.org
Your changes will be displayed to readers once an authorized user accepts them. (help) |
Warning: You are not logged in. Your IP address will be recorded in this page's edit history.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 6: | Line 6: | ||
|platform = DOS | |platform = DOS | ||
|license = [[Doom Source License]] | |license = [[Doom Source License]] | ||
− | }}'''RORDoom''' was created by [[Julian Aubourg]] and was the first [[Doom]] source port to have [[room-over-room]] capabilities. Based on [[Boom]], it was released in 2000 shortly before [[EDGE]], which provided | + | }}'''RORDoom''' was created by [[Julian Aubourg]] and was the first [[Doom]] source port to have [[room-over-room]] capabilities. Based on [[Boom]], it was released in 2000 shortly before [[EDGE]], which provided a similar feature. EDGE gained in popularity, and RORDoom's authors stopped their effort. |
In RORDoom, level designers could create [[sector]]s on top of other sectors, thus breaking the rule of non-overlapping areas. [[Doom rendering engine#Node building|BSP]] tree pre-compilation was done as usual through a fork called ''RORBSP'', and RORDoom's engine detected [[subsector]]s that belonged to several [[sectors]] at loading time. | In RORDoom, level designers could create [[sector]]s on top of other sectors, thus breaking the rule of non-overlapping areas. [[Doom rendering engine#Node building|BSP]] tree pre-compilation was done as usual through a fork called ''RORBSP'', and RORDoom's engine detected [[subsector]]s that belonged to several [[sectors]] at loading time. |