this post was submitted on 26 Feb 2026
264 points (99.3% liked)
PC Gaming
15490 readers
506 users here now
For PC gaming news and discussion. PCGamingWiki
Rules:
- Be Respectful.
- No Spam or Porn.
- No Advertising.
- No Memes.
- No Tech Support.
- No questions about buying/building computers.
- No game suggestions, friend requests, surveys, or begging.
- No Let's Plays, streams, highlight reels/montages, random videos or shorts.
- No off-topic posts/comments, within reason.
- Use the original source, no clickbait titles, no duplicates. (Submissions should be from the original source if possible, unless from paywalled or non-english sources. If the title is clickbait or lacks context you may lightly edit the title.)
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
How fucking hard can it be to write a functional driver for the device you built yourself?
Like, very very very hard? The kind of hard that can't be vive coded?
Considering the amount of legacy soft- and hardware the drivers have to interact with as well as all the fixes specific Programms need, its a complete nightmare to write these drivers. Especially since they pivoted from raw processing power to a mich more software supported system.
What I can't excuse is the abysmal amount of quality control the seem to be doing.
not trying to defend anyone but graphics drivers (particularly in windows) are black magic fuckery. It's no easy task, Intel Arc has been a very public example of how difficult this can be with their first foray into serious dgfx.
If I'm not mistaken most of the driver is fixes for games doing weird shit with graphics api.