Not really voxels, but just a textured height field.
What about next one, including GPU depth adaptive tessellation (still) very fast, long before (2003) that was in hardware.
http://users.belgacom.net/xvox/
Last edited:
Graphical effects that were ahead of their time
- Thread starter OCASM
- Start date
Not really voxels, but just a textured height field.
What about next one, including GPU depth adaptive tessellation (still) very fast, long before (2003) that was in hardware.
http://users.belgacom.net/xvox/
There were plenty.
Like Dark Forces being first FPS game with up and down looking.
Perhaps he didn't account games that weren't post doom shooters.
We had games like FPS shooter Driller from 1988. (better environment and less shooting in Castle Master 1989.)
If he meant textured games we had Ultima Underworld released before Wolfenstein3D.
Doom being heightmap renderer. (Old voxel renderers would fit the naming somewhat, as they were heightmap ray-caster/marchers. (Doom is not.).)
Descent being first game to populate world with 3D enemies. (There were plenty of games before it, Starglider 1&2, Midwinter, Elite Frontier and so on..)
Last edited:
Doom is still kind of heightmap, as you can not be on 2 different heights (z0 or z1) at the same (x0, y0) coordinates.
Quake was real 3D as using full binary space partition based on random planes.
A software based renderer can be found at the bottom of: http://users.skynet.be/fquake/
This actually being an enhanced port to PC (including bilinear / persp correct texture sampling on the CPU), of an original version that was running on ARM.
(Note ARM didn't even at the time have an instruction for division)
Last edited:
It's not correct even if we restrict the discussion to post-Doom shooters. Marathon supported a very modern mouse free look scheme in late 1994, for instance.
Jlippo isn't talking about how the geometry is defined, but rather rendered. Doom is not heightmap-rendered, it's forward-rendering clipped polygonal geometry as it traverses a BSP tree.
"Heightmap" is also a pretty imprecise way of describing the level geometry format. There are arbitrary polygonal 2D regions with defined heights, the representation isn't a texture.
Fact is that the BSP planes in doom are perpendicular to the xy plane. Imagine putting a bunch of cards on a table straight up.
That makes texturing pretty easy as you map only straight vertical lines (very similar to prior height map renderers).
(Textures for ie floor/ceiling in the xy plane are rendered with a different algorithm)
Last edited:
Yes, it certainly made it more feasibly to have fast texturing.
Not entirely sure which games could be called heightmap renderers. (First time hearing the term for texturing.)
Wolfenstein?
It was by my understanding a raycaster one ray per column, distance used to determine wall height etc.
I'm aware of how Doom's geometry constraints aided in texture projection, I'm not understanding what that has to do with it being a heightmap renderer.
I think you're using "heightmap renderer" in a very different way from how I'm envisioning what the term means. I'm imagining something like Outcast, where a ray-casting method is used to render terrain geometry that's defined by a heightmap texture.
When I hear the term "heightmap" I think of a texture where the data at each texel specifies the magnitude of an offset at that sample location.
Outcast is using different methods for texture mapping, one is for the bumpy floor, another one is for vertical walls...
The height map is actually two textures, one specifying a height offset, another one is the actual texture.
If by "the actual texture" you mean the diffuse/albedo/whatever, I wouldn't consider that to be part of "the height map." It's an attribute of a surface whose geometric shape is defined by the heightmap. The height map itself is the texture containing the height offset.
Still they are very closely related, like with prebaked shadows etc, a small shift between them would make the world look completely wrong.
Yes, they usually share uv.
You can have detail textures and so on if needed.
Outcast also had map which told which voxels were verical and had information of wall direction, so it can be properly textured.
This reminded me, do you know how the voxel character tech worked?
I have basic understanding of possibilities, but no idea how it would be fast enough or what limits it would have.
Last edited:
No idea, I was not part of the development team, but did some experimental work based on GPU polygons (as shown in the video)
Yes, pretty evident from the video, especially if they are point sampled.
Ups, jumped a bit from subject there.
And yes, Outcast had some gorgeous polygonal characters and other objects.
Meant the tech used in Blade runner, Lands of Lore 3 and some other games.
It was axis aligned, but rotation was it quite efficient and cost in storage was quite close to traditional sprite.
I do suspect it was stored as a array around Y axis, but never got the idea how to make it fast enough or what the limitations were in terms of shape.
I leave for a month and the thread flourishes 
Another one is fur shading in Star Fox Adventures (2002). Still a rarity these days:
It was also used for grass (it even has some movement):
The cutscene at 24:04 - 25:45 shows all of this (bonus grassy area at 28:45):
2008:
Another one is fur shading in Star Fox Adventures (2002). Still a rarity these days:
It was also used for grass (it even has some movement):
The cutscene at 24:04 - 25:45 shows all of this (bonus grassy area at 28:45):
Similar threads
- Locked
