Rendered at 07:13:09 GMT+0000 (Coordinated Universal Time) with Cloudflare Workers.
AkBKukU 18 hours ago [-]
I have two alternate observations, because VGA is an analog signal there are standards for what the voltages should be. But they were not always followed. Keep in mind that the first two Voodoo cards were also video switchers with a chip to output either the 2D passthrough or the internally generated 3D chip signal created by its own GENDAC.
1. I have a Voodoo 2 paired with an S3 Virge/DX, the Voodoo 2 output level is lower. On a CRT I always have to make the image brighter when running a 3DFX game. Additionally, the V-Sync pulse is not the same as the Virge/DX and the Voodoo 2 image is shifted up.
2. I have a Voodoo Rush which is the maligned hybrid model of 2D and 3D chipsets on a single card. It still uses the internal switching though. On this card the voltage issues are the opposite, the 2D output is significantly dimmer than the 3D which makes the 3D game clip badly when running something until the image is adjusted again.
These problems are voltage level issues with the signal, not gamma. Adjusting gamma will not change the black or white voltage level of the signal. But a lower voltage signal may seem brighter as gamma is raised and the dynamic range is compressed.
> we were so enthralled by the absolute performance of 3DFX that the color fidelity didn’t get as much attention as it should have.
I would say it's more likely that they just didn't notice and the varying outputs from different 3DFX cards, with different GENDAC's, on differently calibrated CRTs just made it a total mess to try and and dial in something as imperceptible as a gamma level. Also keep in mind that around 1995-1996 adjusting the brightness of a CRT was as easy as twisting a few knobs on the front of it.
It's pretty cool that someone can ask an interesting graphics-related question, and John Carmack of all people steps in to answer it. And then even Eric S. Raymond adds a comment further below.
Sharlin 17 hours ago [-]
Yeah, Carmack isn’t super surprising especially as it’s Sanglard who’s asking, but ESR I haven’t really spotted anywhere in a long while. Just some time ago I was thinking that he’s probably a nobody to a lot of the younger folk, or at the very least known only for some of his more terrible political opinions.
parasti 22 hours ago [-]
Fabien Sanglard isn't just someone.
alala-lala-lon 19 hours ago [-]
[dead]
odjciemdkwkdk 19 hours ago [-]
Yes he is. Everyone is “just someone”. Let’s leave the deification for actual religions, yeah?
ranger_danger 9 hours ago [-]
There can be other valid perspectives than your own
DoctorDabadedoo 17 hours ago [-]
Yes, you may call me Gary, tough.
s3graham 17 hours ago [-]
Gary Tarolli would be the perfect response to this question!
rapist 19 hours ago [-]
that applies to the parent comment too then
asveikau 15 hours ago [-]
ESR isn't an authority on this at all, and didn't really add much to the thread.
BigTTYGothGF 14 hours ago [-]
> ESR isn't an authority on this at all
That has never once in his life stopped him.
flykespice 11 hours ago [-]
Nothing stopped him from running loose with his mouth to posting racist crap or defending a pedophile:
That is one way to bury yourself into irrelevancy.
BigTTYGothGF 14 hours ago [-]
> And then even Eric S. Raymond adds a comment further below.
I see he's become a Jensen Huang truther.
throwworhtthrow 12 hours ago [-]
For a minute I confused Eric S. Raymond with Raymond Chen, and couldn't reconcile how a man with such a combative Twitter feed could also write the sedate New Old Thing blog.
Dwedit 1 days ago [-]
You might have heard about sRGB (the commonly used colorspace) not being linear, and that to get halfway between black and white (linear RGB of 50%), you get an sRGB value of around 74%.
But there is one place where sRGB is truly linear, and that is signal voltage for a CRT display. 50% of sRGB truly means 50% of signal voltage (between the minimum and maximum voltages).
thrdbndndn 23 hours ago [-]
Sorry for nitpicking, but my understanding is that the sRGB transfer function was designed to approximate CRT characteristics, not to match them exactly. So saying it is "truly" linear in terms of signal voltage sounds a bit misleading.
mrob 19 hours ago [-]
sRGB intentionally deviates from CRT characteristics to improve fidelity of colors close to black. The difference is small but noticeable in a side-by-side comparison:
Hard to believe, but Nvidia, founded by former SGI engineers, was considered an entrepreneur and challenger of 3dfx, the dominant pioneer in PC 3D hardware 30 years ago.
Edit: see comments re founders
rob74 23 hours ago [-]
Yeah, 3dfx were the pioneers in the 3D graphics space, but because of various mistakes on their side (relying on their proprietary API and on add-on 3D cards for too long, alienating board partners by starting to build their own cards) and faster development by the competitors, Nvidia (and ATI) ate their lunch.
po1nt 23 hours ago [-]
Funny. Nvidia does the same thing today.
Spalau 17 hours ago [-]
Most people believe that the benefit of competition is lower prices. That's not so much true. The real benefit is innovation. Since chip fabrication has been reduced to a small number of manufacturers, innovation in the chip industry stalled. Maybe now, with everyone building their own fabs to manufacture AI chips, we'll see more competition and faster innovation.
stateoff 20 hours ago [-]
They understood the embrace, extend part of it.
whizzter 18 hours ago [-]
Huh? 3DFX "won" initially because the Glide API was simple, lightweight and fast, but the open market pressures of gaming hardware, consumers and developers made OGL (that was "bloated" initially) and D3D (that was improved) win.
Like Glide, CUDA took off because getting started is so much easier than getting started with OpenCL,etc, so a ton of researches could do stupid prototypes without getting bogged down in implementation details and once those prototypes took off a ton of code was tied to Cuda (seriously, look at OpenCL vs Cuda hello world or simple 1d kernel examples).
Now with higher level Python bindings being popular and US export restrictions, people has put effort into stuff like PyTorch supporting other API's, because there is enough industry pressure to have alternatives, the question is how long the CUDA moat can keep giving NVidia a hardware premium.
So, CUDA really wasn't anything they embraced or extended (even if they did so with GL,etc), it's their own API thus GP's parallell to 3dfx/Glide and the question is how long they can keep milking that moat (especially, since iroincally, AI's probably makes porting to other frameworks far easier).
misnome 15 hours ago [-]
CUDA took off for that reason, early mover advantage.
CUDA stayed relevant because they stood behind it and supported it for 20 years rather than changing to a new framework every few years and only half-heartedly supporting, and because it worked on consumer cards so anyone could learn how to use it.
kgkgkkgkd 15 hours ago [-]
Nvidia’s bigggest issue today is not graphics related. It’s sex related.
rasz 23 hours ago [-]
Didnt the board specifically push for vertical integration to chase those sweet downstream margins?
tverbeure 23 hours ago [-]
It was founded by 2 former Sun engineers and 1 LSI logic engineer.
trq01758 23 hours ago [-]
3dfx founders were ex Silicon Graphics, for Nvidia - Jensen worked at LSI and AMD, others were from Sun.
The panelists talk about the lead-up to forming the company (their time at SGI) and the downfall of the company (competing with board manufacturers being a major influence).
The also recorded a Jensen Huang oral history but I haven't gotten a chance to listen to it yet so I can't speak to how interesting it is: https://www.youtube.com/watch?v=0c8i4T9BSqY
papua_is_being_ 20 hours ago [-]
> Nvidia, founded by former SGI engineers
Is that accurate? I saw some content about how Microsoft, Rick Beluzo and Jensen engineered the internal implosion of SGI and transfer of IP to Nvidia.
14 hours ago [-]
aa-jv 20 hours ago [-]
Imagine if SGI had made a titanium laptop.
Now, imaging if NVIDIA make a titanium laptop.
As far as I'm concerned, the moment DGXOS appears on a viable laptop, I'm dumping Apple entirely.
hmstx 11 hours ago [-]
One other aspect of 3dfx looking a bit washed out beyond the gamma problem is the trickery performed in the RAMDAC before it blasted those cool pixels to the VGA port.
If you remember, 3dfx screenshots were just as dithered as, say, an ATI Rage, but on screen it looked smoother (although a bit blurry) while the others looked visibly dithered still (see some 3dfx screenshots https://www.vogons.org/viewtopic.php?f=46&t=36548 )
Part of it is the gamma shenanigans mentioned, and also the blur filtering pass taking place in the DAC which "upgrades" the image (eventually claimed to be so-called 22 bit precision for Voodoo3), introducing some quite visible smudging and hints of unexpected colors as a result.
These days you just author your textures in sRGB, convert them to linear when they’re read, do all the filtering and lighting in linear space and convert the final render target to sRGB (or HDR). Of course this was much more difficult back then with fixed function hardware
dcrazy 1 days ago [-]
I remember watching John document his education about linear color blending on Twitter. I believe it was when he was adding HDR to Rage. It was amazing to me that he had had such a blind spot for so long.
oblio 21 hours ago [-]
If you read Masters of Doom and some of his blogposts/comments, you'll notice that he is laser focused in general, which also means that his blind spots are many :-)
Where he does focus, though, he goes incredibly deep.
I'm so curious what John's AI startup is doing. I got to talk to him briefly right when he was launching, and I was excited to hear about what he's building. John, any recent updates?
recently migrated to a shorter domain: https://XNotMe.com . But xxcancel.com is also still working!
iririririr 15 hours ago [-]
i was used to xcancel which was the one telling me nitter was gone :)
Cloudef 22 hours ago [-]
Thanks. Thought it would be more interesting though. This is literally what colorspaces are for.
EDIT: I think there's a good point though that the game assets should be produced to the asset pipeline losslessly so that they can be transformed to the game's own internal colorspace(s) (depending what the renderer is doing, it can make sense to have multiple colorspaces for different calculations)
masfuerte 17 hours ago [-]
You can actually read messages on twitter without JS now. But Nitter thinks I'm a bot so I can't see the rest of the thread anywhere.
bni 21 hours ago [-]
I had a Nvidia RIVA 128 card before I bought a Voodoo 2 instead.
The Riva came with the OEM PC I got. I remember HL2 looked very washed out on it and being quite unhappy with that. Funny that the 3dfx "solved" it for me.
frabert 21 hours ago [-]
Are you sure it was HL2? That seems way too recent to run on a RIVA 128 or even a Voodoo 2. I think the original HL2 needed DirectX 9 at the minimum, I don't think either of those cards supported that
intrikate 10 hours ago [-]
Half-Life 2 at launch could go down all the way to DirectX 6 if I remember correctly. You lost a lot in the process, but if you needed to, you could get it running on some gnarly cards.
ahartmetz 20 hours ago [-]
Even Half-Life 1 didn't run optimally on a Riva TNT (which I had), the successor of the Riva 128. It ran better on a friend's Voodoo 2.
justsomehnguy 20 hours ago [-]
That was because you had a dogshit CPU. Voodoo was famously 'processor independent' which means what you could get a decent framerate on a cheap CPU.. at the expense of having only 640x480 and 800x600 at best and the picture quality.
CPU was a Celeron "416" (common overclock of the 333). It had been released just a few months before Half-Life and it was maybe 30% slower than the fastest x86 you could buy at the time.
justsomehnguy 13 hours ago [-]
So a 66MHz one with x5 multiplier on a 83MHz FSB.
Well, you can go to the link in the previous comment and see how RIVA fared on P3/Celeron/K6 there compared to Voodoo 2.
bni 18 hours ago [-]
Yes my mistake meant HL1 of course
zbendefy 17 hours ago [-]
hl2's 2004 version could even run on directx 6.0 mode, but that was removed later on, but my intel integrated graphics at the time ran using that (mat_dxlevel 60 i think). It also had dx 7.0 for a while (which brought multitexturing compared to dx6), but I think thats also no longer there.
so its possible that it runs hl2, it would be interesting to see if it does.
deltoidmaximus 12 hours ago [-]
HL2 was a pretty impressive release in the wide variety of hardware available at the time that it supported. I was about to chime in I ran counterstrike:source on a DX8.1 ti4600 with the ti4x00 cards being pretty popular at the time, but am surprised to hear it even had a DX6 mode. I thought DX6 lost broad support pretty quickly whereas 7 had a lot of staying power because of the ubiquity of the Geforce Mx cards.
12 hours ago [-]
poglet 21 hours ago [-]
I suspect half-life 1 or quake 2
threeeeed 16 hours ago [-]
One compounding issue that the article is missing is that alpha blending was not performed in the correct color space on voodoo cards, was not gamma correct. This also contributed to the washed out effect.
basilgohar 16 hours ago [-]
I thought this was going to be about how 3dfx cards rendered only 16 bit color, but I was surprised that this was actually about a hardware issue. Interesting!
doe88 14 hours ago [-]
Carmack answering a question of Sanglard, you might as well train a model just on their chats :)
gwbas1c 17 hours ago [-]
> If you only have a small number of discrete pixel values, you definitely don’t want to spread them evenly from 0 to 1! If you do, you will have good precision in the brights, but very stark “intensity bands” in the dark colors.
That's probably why streaming video has so much banding in dark streams too.
kllrnohj 16 hours ago [-]
It's not. Videos are never in linear. SDR videos almost always means Rec 709 which is approximately gamma 2.4, and HDR videos are HLG or PQ. Both of which are very far from linear.
account42 15 hours ago [-]
For lossy formats, the similarity function targeted by the encoder matters a whole lot more than the bit distribution of the theoretical transfer function. And yes, video codecs have historically badly mangled darker parts of the image.
kllrnohj 12 hours ago [-]
> And yes, video codecs have historically badly mangled darker parts of the image.
Nobody said they didn't. We're talking about the why not the what. Video codecs badly mangle darks, sure, but not because they are in linear like 3dfx in this historical information nugget.
StilesCrisis 16 hours ago [-]
If your streaming video is banding in dark areas, it's possible your TV brightness/contrast need adjustment. If it's set too bright that's where you'd see it. Or it's just a cheap panel, and that's where you can most easily see the flaws.
gwbas1c 15 hours ago [-]
It's a very fancy panel, and I don't see banding from 4K UHD disks.
hmstx 12 hours ago [-]
On low precision in darker colors being a function of gamma...
There were issues in Quake/Quake 2 with bright areas not being quite right, so some measures were taken to try and achieve some form of overbright lighting [1]. Especially in Q1 where the light baking did not perform bounces/radiosity, there were a lot of black spots with adjacent highlights for dramatic effect, and you could see some banding there with the OpenGL renderers, which is more apparent with lower texture settings and pumped gamma.
But also, as a side effect of this overbright ability, lighting got flattened even more in GL [1]:
>The original quake (software) engine used overbright lighting, which means the lightmap brightness can go up to 200%. So, light.exe creates BSP files with lightmaps that go up to 200%.
>In glquake […] there is no overbright lighting, so every part of the lightmap that goes above 100% is flattened to equal 100%. This is why glquake looks just fine in darker rooms, but in bright areas the lighting looks very flat.
>[Some engines] restore the overbright feature of the software renderer, so that lighting hot-spots will actually be as bright as intended.
A similar effect was pursued further in Quake 3 with r_overbrightbits/r_mapoverbrightbits, which fakes a higher dynamic range through futzing with the hardware gamma ramp and bit-shifting/normalizing color channels [2], achieving highlights that pop a lot more... at the expense of introducing even more banding in dark spots.
He mentioned it in passing in a .plan in 2000 that touches on higher precision buffers [3]:
>Q3 hacks the gamma tables to sacrifice a bit of precision to get a 0.0 to 2.0 range, but I wanted more than that for even primitive rendering techniques.
Eventually, in his .plan dated january 29th, 2003 [4] he appears convinced,
>The future is in floating point framebuffers. One of the most noticeable thing this will get you without fundamental algorithm changes is the ability to use a correct display gamma ramp without destroying the dark color precision.
A lot of people today trying to 'be correct' and resample in linear space end up getting worse results either because of introducing banding from quarantining back to 8-bits or because the non-linear space resampling often happens to do something closer to the right thing thanks to human contrast-sensitivity function.
thrdbndndn 23 hours ago [-]
Human contrast sensitivity doesn't change the physics of light mixing/blending, which should always happen in linear space.
I do agree with you on the quantisation issues when working in linear space without taking proper care, though.
rasz 1 days ago [-]
In numbers:
VGA default gamma y = 1 aka linear
3DFX default gamma y = 1.5
You might, like I did, think wtf is he talking about, default is linear and 3dfx bends it. But CRT monitors y = 2.2! When added up (multiply exponents) 3dfx is closer to linear output than ordinary VGA. You would still have to set 3dfx to 2.2 to get perfect linear output.
TLDR: Carmack is partially right. As he says even game developers were clueless. Nobody had to change their workflows. You could call glide grGammaCorrectionValue or even easier set DOS environment variable SST_GAMMA to 1 to get Exact same color mapping as ordinary VGA.
Why did 3dfx boost that? deffo not to get linear output, if they wanted linear they would set 2.2. Probably a Color twist on loudness war, brighter better, or maybe felt bad half the bits would get wasted (crushed into near blacks) in 16bit rendering.
superjan 1 days ago [-]
Where was this applied in the 3dfx? In the analog output?
ack_complete 24 hours ago [-]
grGammaCorrectionValue() sounds like the DAC -- so during scanout.
Which by itself isn't the worst, if you have a 24-bit framebuffer and sRGB read conversion. Without read conversion and going from 565 textures to 565 framebuffer with a 1.5 gamma... blecch. Checking the curves, the banding on the low end is worse than an Atari 2600!
anal_reactor 23 hours ago [-]
A bit tangential, but in modern games with HDR I still get the fucking banding of dark colors.
Someone enlighten me what HDR actually does then.
reverheart 18 hours ago [-]
Dynamic range is luminance range. Standard dynamic range (SDR) was ~[0, 200nits]. High dynamic range (HDR) is higher, e.g. [0, 1000nits]. As John Carmack pointed out, human perception is non-linear. SDR uses color volumes that relies on Stevens' power law, which gamma correction approximates. For example, the SRGB and rec.709 TFs are pretty much piecewise gamma 2.2. This curve is only accurate at low nit levels. Thus, at high nit levels, a new curve known as the "perceptual quanitizer" or PQ TF is used instead. This curve is ostensibly fine up to 10000nits.
Because luminance ranges can differ drastically, converting media intended to be viewed on, say, a 3000nits display to a 1000nits display require other global transformations. HDR metadata standards are different parameterizations of different global transforms.
If you've ever experienced problems with HDR media it is because human perception is not actually global nor is it rooted in physics. We know from Retinex theory, the spatial dampening of the lateral geniculate nucleus, the Barten CSF, the Gelb effect, the 2022 Los Alamos paper on the non-Riemannian nature of color, etc. that the human visual system (HVS) cares about local spatio-temporal relationships more than it cares about global luminance. Because HDR pipelines are built on global transforms, they can actually have the effect of crushing the local differentials the HVS really cares about. There's a lot more to say on all of this, but that's the gist of it.
kgkgkkgkd 15 hours ago [-]
Nits go up to 11 on hdr displays.
cowlevel 22 hours ago [-]
mainly it confuses the heck out of everyone because some display industry association tried to tie it to absolute luminosity and then made HDR content way too bright or dark relative to everything around it
Cloudef 22 hours ago [-]
HDR is extra brightness on your display. In practice it's kind of a mess, as both the hardware and software implementation has to be good. If you have cheap display, you'll get something marketed as HDR even though it would look better with it turned off, as they likely use very big extra brightness zones, so it won't end up looking right. On software side, unless it's a console, the PC stack was not designed for HDR and it really takes co-operation of the whole stack to make it look correct on the display. For a while, for best result you had to basically bypass most of your display stack to get correct results. Valve's been working on it for their own platform, and wayland has some experimental support.
EDIT: For TV, HDR works well assuming you don't have cheap TV.
cyberax 1 days ago [-]
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?
magicalhippo 21 hours ago [-]
From what I can gather it's mainly a holdover from Quake[1] and the limited colors afforded by an 8-bit palette.
The lightmaps and such support colored lighting, but by default the software renderer just used the max IIRC of the color channels as a monochrome light value.
Just for giggles I recently had Claude rewrite the software renderer for Quake 2 to support true-color output and so could enable `sw_colorlight 1` when using the software renderer. Doing so results in the same reddish tint as the GL renderer, but with the software renderer aesthetics.
I think you can set `sw_colorlight` to `1` even in the classic renderer, but it'll look quite bad due to the limited colors afforded by the 8-bit palette.
Makes sense I guess, the plot takes place on Mars, so perhaps that's why they went heavy on the red-orange.
edit: uploaded some screenshots to show the difference:
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.
Sohcahtoa82 12 hours ago [-]
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.
magicalhippo 6 hours ago [-]
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.
Yes. And it had a very distinct dithering pattern which I can't say I've seen in any other games or such.
neckro23 16 hours ago [-]
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.
stoltzmann 15 hours ago [-]
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.
fredoralive 24 hours ago [-]
IIRC the software renderer in Quake 2 doesn't do coloured lighting.
nopurpose 24 hours ago [-]
I explained to myself at the time that it is because skybox light start to tint everything underneath it.
contingencies 1 days ago [-]
It's time to kick ass and render color. And I'm all outta color.
drdaeman 1 days ago [-]
Entirely different studio and codebases, I’m afraid.
contingencies 23 hours ago [-]
It's the period and the hardware, not the studio! I wonder what period gamers would have thought of GPUs and bitcoin :)
Although I never saw Quake on a 3dfx card, it has a recognizable "style." I like that style in modern user-made maps, some of which are entire games with multiple levels.
I always thought the style was an artistic choice rather than a technical limitation.
Now I understand that a lot of old graphics "styles" were restricted by the existing hardware.
arthur_steel 17 hours ago [-]
[flagged]
benchnotes 1 days ago [-]
[dead]
indubioproIO 1 days ago [-]
[dead]
Luke2642 23 hours ago [-]
I dream of a parallel timeline when OKLAB became the standard colourspace in 1980! It's a very colourful dream, the lightness stays consistent as the hues change, and colour interpolation just works!
cccbbbaaa 21 hours ago [-]
When it comes to colour spaces, there is no “one size fits all”. Perceptual colour spaces are good for, well, perceptual transformations, but many transformations ought to be done in a linear colour space, eg. exposure, color calibration and white balance adjustment, etc. This is how darktable operates (everything before the tonemapper is done in a linear colour space, everything after is done in a perceptual colour space such as JzAzBz or DT UCS 2022 [0], the latter being based on OKLab). Experience has shown that choices made when designing a perceptual colour space can lead to subtle issues [1]. (JzAzBz has its own issues for such transformations, such as not modelling the Helmholtz-Kohlrausch effect [2].)
Oklab/oklch is good for consistent luminance across hue, but the real world gamut is so limited - our display / print tech is always able to make green/yellow far brighter than red/blue, for any given tech - it can be a little frustrating to use.
fps-hero 23 hours ago [-]
Humans are too flawed with colour perception. I wish color were 2D, but much like music, it depends on what notes you play.
It’s bad enough that monitors do not produce colour accuracy, or to the full gamut.
Honestly, it’s the one thing Apple got right. Everyone in the creative industry runs Apple, and Apple had a consistency with color. Good luck getting your stuff approved if you produced it on Windows.
barrkel 22 hours ago [-]
Expecting a full gamut is unreasonable when you consider what it would mean: huge brightness for blue and red, artificial limiting of green.
Our eyes are simply more sensitive to yellowish green. Any reasonable tech will have a gamut that is tented towards green.
kllrnohj 16 hours ago [-]
A full gamut isn't unreasonable because of that. A full gamut is unreasonable because you'd need a larger number of subpixels to make that work. If you look at a CIE 1931 chromaticity diagram, no matter where you place your 3 points for 3 subpixels you will be unable to cover the full gamut. BT 2020 is basically an attempt at covering as much as possible and you can still see it misses huge amounts of visible colors. A wider gamut at that point requires additional color subpixels so it's no longer a triangle.
And at least with current technology we are not at a point where sacrificing resolution or brightness for more coverage of the green end of the gamut is a wortwhile tradeoff.
Dylan16807 4 hours ago [-]
We just need to invent red LEDs that can go negative and we'll basically fill out the gamut.
> And at least with current technology we are not at a point where sacrificing resolution or brightness for more coverage of the green end of the gamut is a wortwhile tradeoff.
I disagree there, we have a lot of very bright screens that could take the hit. And it's not just the green zone, replacing blue with azure and violet would allow a big expansion of possible saturated colors.
1. I have a Voodoo 2 paired with an S3 Virge/DX, the Voodoo 2 output level is lower. On a CRT I always have to make the image brighter when running a 3DFX game. Additionally, the V-Sync pulse is not the same as the Virge/DX and the Voodoo 2 image is shifted up.
2. I have a Voodoo Rush which is the maligned hybrid model of 2D and 3D chipsets on a single card. It still uses the internal switching though. On this card the voltage issues are the opposite, the 2D output is significantly dimmer than the 3D which makes the 3D game clip badly when running something until the image is adjusted again.
These problems are voltage level issues with the signal, not gamma. Adjusting gamma will not change the black or white voltage level of the signal. But a lower voltage signal may seem brighter as gamma is raised and the dynamic range is compressed.
> we were so enthralled by the absolute performance of 3DFX that the color fidelity didn’t get as much attention as it should have.
I would say it's more likely that they just didn't notice and the varying outputs from different 3DFX cards, with different GENDAC's, on differently calibrated CRTs just made it a total mess to try and and dial in something as imperceptible as a gamma level. Also keep in mind that around 1995-1996 adjusting the brightness of a CRT was as easy as twisting a few knobs on the front of it.
or some register poking after startup, e.g. https://github.com/RetroLoom/S3ctl
That has never once in his life stopped him.
http://esr.ibiblio.org/?p=129
https://nitter.netbub.com/esrtweet/status/185702046923013338...
That is one way to bury yourself into irrelevancy.
I see he's become a Jensen Huang truther.
But there is one place where sRGB is truly linear, and that is signal voltage for a CRT display. 50% of sRGB truly means 50% of signal voltage (between the minimum and maximum voltages).
https://en.wikipedia.org/wiki/SRGB#Transfer_function_(%22gam...
Edit: see comments re founders
Like Glide, CUDA took off because getting started is so much easier than getting started with OpenCL,etc, so a ton of researches could do stupid prototypes without getting bogged down in implementation details and once those prototypes took off a ton of code was tied to Cuda (seriously, look at OpenCL vs Cuda hello world or simple 1d kernel examples).
Now with higher level Python bindings being popular and US export restrictions, people has put effort into stuff like PyTorch supporting other API's, because there is enough industry pressure to have alternatives, the question is how long the CUDA moat can keep giving NVidia a hardware premium.
So, CUDA really wasn't anything they embraced or extended (even if they did so with GL,etc), it's their own API thus GP's parallell to 3dfx/Glide and the question is how long they can keep milking that moat (especially, since iroincally, AI's probably makes porting to other frameworks far easier).
CUDA stayed relevant because they stood behind it and supported it for 20 years rather than changing to a new framework every few years and only half-heartedly supporting, and because it worked on consumer cards so anyone could learn how to use it.
The panelists talk about the lead-up to forming the company (their time at SGI) and the downfall of the company (competing with board manufacturers being a major influence).
The also recorded a Jensen Huang oral history but I haven't gotten a chance to listen to it yet so I can't speak to how interesting it is: https://www.youtube.com/watch?v=0c8i4T9BSqY
Is that accurate? I saw some content about how Microsoft, Rick Beluzo and Jensen engineered the internal implosion of SGI and transfer of IP to Nvidia.
Now, imaging if NVIDIA make a titanium laptop.
As far as I'm concerned, the moment DGXOS appears on a viable laptop, I'm dumping Apple entirely.
If you remember, 3dfx screenshots were just as dithered as, say, an ATI Rage, but on screen it looked smoother (although a bit blurry) while the others looked visibly dithered still (see some 3dfx screenshots https://www.vogons.org/viewtopic.php?f=46&t=36548 )
Part of it is the gamma shenanigans mentioned, and also the blur filtering pass taking place in the DAC which "upgrades" the image (eventually claimed to be so-called 22 bit precision for Voodoo3), introducing some quite visible smudging and hints of unexpected colors as a result.
This has been approximated in shaders you can apply to most games with ReShade etc., take a look (https://www.vogons.org/viewtopic.php?t=36470)
Where he does focus, though, he goes incredibly deep.
EDIT: I think there's a good point though that the game assets should be produced to the asset pipeline losslessly so that they can be transformed to the game's own internal colorspace(s) (depending what the renderer is doing, it can make sense to have multiple colorspaces for different calculations)
The Riva came with the OEM PC I got. I remember HL2 looked very washed out on it and being quite unhappy with that. Funny that the 3dfx "solved" it for me.
https://www.tomshardware.com/reviews/nvidia,87-15.html
Well, you can go to the link in the previous comment and see how RIVA fared on P3/Celeron/K6 there compared to Voodoo 2.
so its possible that it runs hl2, it would be interesting to see if it does.
That's probably why streaming video has so much banding in dark streams too.
Nobody said they didn't. We're talking about the why not the what. Video codecs badly mangle darks, sure, but not because they are in linear like 3dfx in this historical information nugget.
There were issues in Quake/Quake 2 with bright areas not being quite right, so some measures were taken to try and achieve some form of overbright lighting [1]. Especially in Q1 where the light baking did not perform bounces/radiosity, there were a lot of black spots with adjacent highlights for dramatic effect, and you could see some banding there with the OpenGL renderers, which is more apparent with lower texture settings and pumped gamma.
But also, as a side effect of this overbright ability, lighting got flattened even more in GL [1]:
>The original quake (software) engine used overbright lighting, which means the lightmap brightness can go up to 200%. So, light.exe creates BSP files with lightmaps that go up to 200%.
>In glquake […] there is no overbright lighting, so every part of the lightmap that goes above 100% is flattened to equal 100%. This is why glquake looks just fine in darker rooms, but in bright areas the lighting looks very flat.
>[Some engines] restore the overbright feature of the software renderer, so that lighting hot-spots will actually be as bright as intended.
A similar effect was pursued further in Quake 3 with r_overbrightbits/r_mapoverbrightbits, which fakes a higher dynamic range through futzing with the hardware gamma ramp and bit-shifting/normalizing color channels [2], achieving highlights that pop a lot more... at the expense of introducing even more banding in dark spots.
He mentioned it in passing in a .plan in 2000 that touches on higher precision buffers [3]:
>Q3 hacks the gamma tables to sacrifice a bit of precision to get a 0.0 to 2.0 range, but I wanted more than that for even primitive rendering techniques.
Eventually, in his .plan dated january 29th, 2003 [4] he appears convinced,
>The future is in floating point framebuffers. One of the most noticeable thing this will get you without fundamental algorithm changes is the ability to use a correct display gamma ramp without destroying the dark color precision.
[1] https://www.quaddicted.com/engines/software_vs_glquake
[2] You can probably read the C/OpenGL code better :)
[3] https://github.com/ESWAT/john-carmack-plan-archive/blob/mast...
[4] https://github.com/ESWAT/john-carmack-plan-archive/blob/mast...
I do agree with you on the quantisation issues when working in linear space without taking proper care, though.
VGA default gamma y = 1 aka linear
3DFX default gamma y = 1.5
You might, like I did, think wtf is he talking about, default is linear and 3dfx bends it. But CRT monitors y = 2.2! When added up (multiply exponents) 3dfx is closer to linear output than ordinary VGA. You would still have to set 3dfx to 2.2 to get perfect linear output.
TLDR: Carmack is partially right. As he says even game developers were clueless. Nobody had to change their workflows. You could call glide grGammaCorrectionValue or even easier set DOS environment variable SST_GAMMA to 1 to get Exact same color mapping as ordinary VGA.
Why did 3dfx boost that? deffo not to get linear output, if they wanted linear they would set 2.2. Probably a Color twist on loudness war, brighter better, or maybe felt bad half the bits would get wasted (crushed into near blacks) in 16bit rendering.
Which by itself isn't the worst, if you have a 24-bit framebuffer and sRGB read conversion. Without read conversion and going from 565 textures to 565 framebuffer with a 1.5 gamma... blecch. Checking the curves, the banding on the low end is worse than an Atari 2600!
Someone enlighten me what HDR actually does then.
Because luminance ranges can differ drastically, converting media intended to be viewed on, say, a 3000nits display to a 1000nits display require other global transformations. HDR metadata standards are different parameterizations of different global transforms.
If you've ever experienced problems with HDR media it is because human perception is not actually global nor is it rooted in physics. We know from Retinex theory, the spatial dampening of the lateral geniculate nucleus, the Barten CSF, the Gelb effect, the 2022 Los Alamos paper on the non-Riemannian nature of color, etc. that the human visual system (HVS) cares about local spatio-temporal relationships more than it cares about global luminance. Because HDR pipelines are built on global transforms, they can actually have the effect of crushing the local differentials the HVS really cares about. There's a lot more to say on all of this, but that's the gist of it.
EDIT: For TV, HDR works well assuming you don't have cheap TV.
Does anyone know the reason for that?
The lightmaps and such support colored lighting, but by default the software renderer just used the max IIRC of the color channels as a monochrome light value.
Just for giggles I recently had Claude rewrite the software renderer for Quake 2 to support true-color output and so could enable `sw_colorlight 1` when using the software renderer. Doing so results in the same reddish tint as the GL renderer, but with the software renderer aesthetics.
I think you can set `sw_colorlight` to `1` even in the classic renderer, but it'll look quite bad due to the limited colors afforded by the 8-bit palette.
Makes sense I guess, the plot takes place on Mars, so perhaps that's why they went heavy on the red-orange.
edit: uploaded some screenshots to show the difference:
Classic SW with `sw_colorlight 1`: https://imglink.cc/cdn/fv5Z3WB_aS.jpg
True-color SW with `sw_colorlight 1`: https://imglink.cc/cdn/fx8prYfGs6.jpg
[1]: https://quake.fandom.com/wiki/Colored_lightning
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.
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.
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
Half-Life 1 could also do colored lighting in software, the software-rendered and accelerated versions looked almost identical aside from the texture filtering.
Big difference from what I remember was water rendering with the software mode having some fun effects.
For young'uns: https://en.wikipedia.org/wiki/Duke_Nukem_3D + https://en.wikipedia.org/wiki/3dfx#Entry_to_the_consumer_mar...
I always thought the style was an artistic choice rather than a technical limitation.
Now I understand that a lot of old graphics "styles" were restricted by the existing hardware.
[0] https://eng.aurelienpierre.com/2022/02/color-saturation-cont...
[1] https://ansel.photos/en/news/color-controls-finally-correct/... (Issue caused by the DT UCS 2022 colour space, which is based on OKLab.)
[2] https://en.wikipedia.org/wiki/Helmholtz%E2%80%93Kohlrausch_e...
It’s bad enough that monitors do not produce colour accuracy, or to the full gamut.
Honestly, it’s the one thing Apple got right. Everyone in the creative industry runs Apple, and Apple had a consistency with color. Good luck getting your stuff approved if you produced it on Windows.
Our eyes are simply more sensitive to yellowish green. Any reasonable tech will have a gamut that is tented towards green.
And at least with current technology we are not at a point where sacrificing resolution or brightness for more coverage of the green end of the gamut is a wortwhile tradeoff.
> And at least with current technology we are not at a point where sacrificing resolution or brightness for more coverage of the green end of the gamut is a wortwhile tradeoff.
I disagree there, we have a lot of very bright screens that could take the hit. And it's not just the green zone, replacing blue with azure and violet would allow a big expansion of possible saturated colors.