News for hackers. Stuff that matters.
Re:Why 3dfx 1 cards had such a washed out color output? by cyberax on Tuesday November 17, 2026 @12:27AM (#50527795)
Another interesting question: I remember getting a 3D accelerator (some Riva card?) and getting surprised how everything started looking reddish in Quake 2, compared to software rendering.

Does anyone know the reason for that?

Re:Why 3dfx 1 cards had such a washed out color output? by nopurpose on Tuesday November 17, 2026 @02:16AM (#50528445)
I explained to myself at the time that it is because skybox light start to tint everything underneath it.
Re:Why 3dfx 1 cards had such a washed out color output? by fredoralive on Tuesday November 17, 2026 @02:26AM (#50528499)
IIRC the software renderer in Quake 2 doesn't do coloured lighting.
Re:Why 3dfx 1 cards had such a washed out color output? by Panzerschrek on Tuesday November 17, 2026 @03:16AM (#50528800)
Quake II uses old 8-bit approach in its software rasterizer, which isn't capable of applying colored lighting. It's a shame, that no progress was made since original Quake. Half-Life (also derived from Quake) did better job and supports colored lighting in software mode.

In OpenGL mode colored lighting is there. But map designers overused it too much, especially in outdoor locations having yellow sky lighting, which looks somewhat depressive.

Re:Why 3dfx 1 cards had such a washed out color output? by anthk on Tuesday November 17, 2026 @09:38AM (#50531993)
Could Unreal do that in software rendering?
Re:Why 3dfx 1 cards had such a washed out color output? by neckro23 on Tuesday November 17, 2026 @10:19AM (#50532555)
Pretty sure it could, the original Unreal engine was quite impressive for its time. In fact if I'm recalling correctly, it had some omissions when accelerated (detail textures?) that worked fine in software mode.

Half-Life 1 could also do colored lighting in software, the software-rendered and accelerated versions looked almost identical aside from the texture filtering.

Re:Why 3dfx 1 cards had such a washed out color output? by stoltzmann on Tuesday November 17, 2026 @11:09AM (#50533453)
Unreal had detail textures with 3D acceleration, but IIRC in software mode it used a dithering step for sampling textures to break them up, instead of directly point sampling.

Big difference from what I remember was water rendering with the software mode having some fun effects.

Re:Why 3dfx 1 cards had such a washed out color output? by magicalhippo on Tuesday November 17, 2026 @07:51PM (#50540435)
Yes. And it had a very distinct dithering pattern which I can't say I've seen in any other games or such.
Re:Why 3dfx 1 cards had such a washed out color output? by Sohcahtoa82 on Tuesday November 17, 2026 @02:33PM (#50536926)
Always blew my mind that software rendering in Quake was a thing.

True perspective-correct 3D texturing (as opposed to the fake 3D in the DOOM engine, or the affine texturing of the PSX) on a 90 Mhz Pentium CPU.

Sure, the resolution was low (I think we were still in 320x200?), but that still doesn't give a lot of clock cycles for each pixel. 320x200 at 30 fps is 1,920,000 pixels per second. At 90 Mhz, that's only about 45 clock cycles per pixel on an architecture that could take several clock cycles per instruction.

The software renderer didn't do colored lights, but it still did dynamic lights from rockets and grenades, IIRC.

EDIT: Just realized we were talking about Quake II, not the first Quake. Whatever, still impressive.

Re:Why 3dfx 1 cards had such a washed out color output? by magicalhippo on Tuesday November 17, 2026 @07:44PM (#50540383)
Michael Abrash talks about it[1] in his Ramblings in Realtime[2], which covers a lot of the other tricks they did which still seems quite amazing to me still.

The surface-building inner loop is particular efficient, because it consists of nothing more than interpolating intensity, combining it with a texel and using the result to look up a lit texel color, and storing the results with a dword write every four texels. In assembly language, we've gotten this code down to 2.25 cycles per lit texel in Quake. Similarly, the texture-mapping inner loop, which overlaps an FDIV for floating-point perspective correction with integer pixel drawing in 16-pixel bursts, has been squeezed down to 7.5 cycles per pixel on a Pentium, so the combined inner loop times for building and drawing a surface is roughly in the neighborhood of 10 cycles per pixel.

[1]: https://valvedev.info/archives/abrash/chap68.html

[2]: https://valvedev.info/archives/abrash/contents.html

Re:Why 3dfx 1 cards had such a washed out color output? by magicalhippo on Tuesday November 17, 2026 @04:58AM (#50529463)
[delayed]