/vr/ - Retro Games

>>10488882
Actually, as long as the limitation that you can't see both at the same time is upheld, the renderer doesn't care.

>>5101176
2.5D engines like in Marathon/Doom/Duke3d and such work on BSP trees and render flats, slopes and walls instead of polygons, which works much differently on fundamental level and allow such "bent space" transitions much easier than actual 3D engines. ALL of BSP engines allow it if you have a tool for editing a BSP tree.

>>5101259
In vanilla Doom, data is NOT precompiled and it is possible to do the very same trick in exactly same way, it's just that the feature was not included in the editing tools, as id Software made deliberate steps to avoid making their maps confusing, including specific guidelines to povide players with landmarks and points of reference so it was harder to get lost, unless you REALLY not paying attention

>>5101546
Silent teleport is a bit different thing. You cant shoot through it for one, and you cant see what's actually going on behind the teleport line so bodies/marks/enemies left behind would disappear, which is why mapers do them in (usually bent) corridors with no enemies or pickups around so you dont notice the transition.

This 5D geometry is still totally possible in Vanilla Doom though, via the very same kind of BSP fuckery.
It's just such feature was not included in the editing tools, and you had to know pretty well what are you doing to edit the generated BSP tree manually, which is why nobody done it until Linguica discovered it in 2015.

This can be done only in engines that render BSP directly, so it does not work in source ports that recompile BSP into actual 3D space (i.e. most of them). GZDoom allows you to do virtually same in actual 3D space via render portals.

Actually, Duke Nukem 3D uses exactly same thing to render multi-floor architecture, and has some 5D fuckery of its own in secret levels, but does not use it in regular levels for same reason Doom doesen't - to avoid making levels too confusing.