this post was submitted on 06 Dec 2024
350 points (98.3% liked)

Technology

60035 readers
2764 users here now

This is a most excellent place for technology news and articles.

Our Rules

  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots

founded 2 years ago
MODERATORS
L3s@lemmy.world
L3s@fry.gs
L4s@fry.gs
L4s@lemmy.world
enu@lemmy.world
350
A Valve engineer fixed 3D lighting so hard he had to tell all the graphics card manufacturers their math was wrong, and the reaction was: 'I hate you' (www.pcgamer.com)
submitted 2 weeks ago by pookie@lemmy.blahaj.zone to c/technology@lemmy.world
25 comments fedilink hide all child comments
 

cross-posted from: https://lemmy.ca/post/34328210

you are viewing a single comment's thread
view the rest of the comments
[–] BlackLaZoR@fedia.io 45 points 2 weeks ago (5 children)

"It's a bit technical," begins Birdwell, "but the simple version is that graphics cards at the time always stored RGB textures and even displayed everything as non linear intensities, meaning that an 8 bit RGB value of 128 encodes a pixel that's about 22% as bright as a value of 255, but the graphics hardware was doing lighting calculations as though everything was linear.

Jesus Christ, I knew this was a problem with image editing software back then, but I never knew, that GPU manufacturers fucked it up as well. How did this happen?

[–] Mistic@lemmy.world 15 points 2 weeks ago* (last edited 2 weeks ago) (1 children)

I have a good guess on how this would actually happen:

PM: We need this

Specialist: makes this (doesn't check results)

QC: Looks good (but doesn't actually check)

Some updates later may further break the functionality. And as long as numbers aren't blatantly wrong (think 0s everywhere, for example) and nobody checks thoroughly enough, the issue will remain.

I have unfortunate experience of being a part of such a story, haha. There are ways to counter it. Mainly, their project documentation either wasn't up to par or wasn't used as a reference during creation and tests. Either way, it's negligence.

[–] BlackLaZoR@fedia.io 3 points 2 weeks ago

I imagine in case of GPU design, there should be a bunch of tests for image correctness at some point, which would require pixel perfect reproduction to pass.

But it's plausible that tests were running incorrect math too.

[–] Iapar@feddit.org 6 points 2 weeks ago

"They are just human after aaaall 🎶"

[–] leds@feddit.dk 2 points 2 weeks ago

Linear is probably a lot faster?