The Witcher 3: Wild Hunt – Remastered launched on September 29, 2026, as a free upgrade for existing owners on PC, PlayStation 5, and Xbox Series X/S. Within hours, AMD Radeon owners started posting screenshots of grass rendering solid black, hair turning into glowing artifacts, and environments missing entire stretches of vegetation. Nvidia GeForce owners, by most accounts, were playing a functional game. CD PROJEKT RED confirmed the split is driver-related, not a universal defect, and pointed AMD users toward a driver package that had not fully rolled out at launch.
This is not a minor visual quirk buried in a patch log. It is a launch-day compatibility failure on one of the two major PC GPU vendors, arriving for a title that had already drawn scrutiny over its RTX 5090 performance falling short of a locked 60 FPS. The remaster’s free upgrade spanning six platforms was meant to be a goodwill victory lap for a game turning more than a decade old. Instead, a sizable chunk of its PC audience is now troubleshooting driver versions instead of exploring Velen.
Don't miss new tech stories on Google
Add Tech Insider once in the Google app and our stories appear in your news suggestions.
What’s actually broken on AMD Radeon GPUs
The reported symptom list is unusually broad for a single-vendor issue. Outlets covering the launch, including virus.hr and IGN, documented missing trees and vegetation, black visual artifacts spreading across terrain and character models, flickering and corrupted textures, incorrect level-of-detail rendering, and environments that failed to fully load. Ray tracing and path tracing modes compounded the problem, producing additional visual corruption on top of the baseline rendering glitches. Some players also reported outright crashes and general instability during extended play sessions.
Virus.hr characterized the AMD experience as involving numerous visual bugs and crashes, while noting that Nvidia users generally found the remaster functional out of the box. IGN’s coverage highlighted the same missing-vegetation and black-artifact pattern independently, suggesting the issue was reproducible across review units rather than an isolated configuration problem. A GOG community discussion went further, describing the remaster as “completely broken” on Radeon RX 9000-series hardware prior to a driver update. Tech creator NikTek posted footage from an RX 9070 XT, writing: “The Witcher 3 Remastered is completely broken on AMD hardware I’m playing on an RX 9070 XT and as you can see in this clip; the water glitches out, hair, skin textures are off and the grass is black.”
At the severe end of the spectrum, some Radeon owners reported entire environmental chunks failing to render at all, rather than simply displaying corrupted textures on top of existing geometry. That’s a meaningfully different failure mode. A black or flickering texture is a shading or texture-streaming bug layered on a scene that still loads; a missing chunk of forest or terrain points to the game’s asset-streaming system failing to pull in level-of-detail data correctly on affected Radeon configurations. Combined with the glowing-hair and water-rendering glitches captured on camera, the range of symptoms suggests problems spanning multiple parts of the rendering pipeline, including textures, geometry streaming, and shader compilation, rather than one isolated bug.
Some players also flagged glowing hair rendering as a distinct symptom separate from the black-texture problem, with a subset reporting that an older AMD driver, version 26.3.1, resolved that specific artifact when the newer recommended driver did not. That is user testimony shared on Steam’s community forums rather than an official CD Projekt Red or AMD confirmation, and it underscores how fragmented the workaround landscape became in the first 24 hours after launch.
Which AMD GPUs are affected
The remaster ships with AMD FSR 4 support, including Frame Generation and Anti-Lag 2, for Radeon RX 7000-series cards and newer, with FSR 2 as a fallback for older, unsupported GPUs. That means the newest and most expensive Radeon hardware on the market, the cards most likely to be running this remaster at native or near-native resolution, is exactly where the driver mismatch is landing hardest. The GOG discussion thread specifically calls out RX 9000-series hardware as broken before the driver update, and the tech creator’s on-camera demonstration used an RX 9070 XT, currently one of AMD’s flagship gaming GPUs.
Available reporting does not provide a complete card-by-card failure list, and it does not establish that every RX 7000 or RX 9000 card is affected to the same degree. What is consistent across sources is that AMD Radeon GPUs as a class are the ones generating the bug reports, while Nvidia GeForce cards are not showing the same pattern at anywhere near the same frequency.
| Reported issue | AMD Radeon | Nvidia GeForce |
|---|---|---|
| Missing trees/vegetation | Reported (IGN, virus.hr) | Not reported |
| Black texture artifacts | Reported widely | Not reported |
| Glowing hair rendering | Reported (Steam forums) | Not reported |
| Ray tracing/path tracing glitches | Reported | Occasional, limited (GOG forums) |
| Crashes/instability | Reported | Not widely reported |
| “Completely broken” claims | RX 9000-series, pre-driver-update (GOG forums) | N/A |
| Recommended driver at launch | Adrenalin 26.9.2 (released Sept. 29, 2026, same day as launch) | 617.14 |
The technical root cause: why shader compilation and texture streaming broke on Radeon
The symptom list reported across Radeon hardware, solid black grass, missing forests, glowing hair, corrupted water, isn’t random noise. Each failure mode maps onto a different part of the rendering pipeline, and the roughly six-week gap between AMD’s last pre-launch driver, Adrenalin 26.8.1 on August 20, and the fix that actually shipped, Adrenalin 26.9.2 on September 29, is long enough for a title’s new shader and streaming code to drift out of sync with what an installed driver expects. Breaking down why helps explain both the severity of the bugs and why one driver update resolved most, but not all, of them.
Shader compilation stutter and the black-texture link
Modern PC titles, especially a remaster rebuilt around ray tracing and path tracing, don’t ship with every shader variant pre-compiled for every GPU architecture. The driver compiles shader permutations against the specific hardware running it, often the first time a given material or lighting effect is encountered in gameplay. That step depends on the driver correctly recognizing the game’s rendering calls and translating them into instructions its shader cores can execute. When a driver hasn’t been validated against a title’s new shader set, the position Radeon owners were in while running Adrenalin 26.9.1 or earlier against a remaster built around reworked lighting and materials, compilation can fail or time out. The typical fallback when a shader fails to bind correctly isn’t a crash; it’s a null or default texture state, which on screen looks exactly like what Radeon owners described: grass, hair, and skin rendering as flat black. That failure pattern points to a driver-side compatibility gap rather than a defect in the remaster’s art assets, since the same assets reportedly rendered correctly for most users once Adrenalin 26.9.2 reached their systems on September 29 — though AMD’s own release notes for that driver never explicitly itemized a fix for this specific shader-compilation fault, a gap covered in more detail further below.
Asset streaming and the missing-forest problem
The missing-vegetation reports describe something different from a texture problem: entire stretches of forest and terrain geometry failing to appear at all. Open-world engines stream level-of-detail data into memory as a player moves through the world, pulling higher-resolution geometry and foliage into GPU memory only when needed and discarding it when it isn’t. That streaming pipeline depends on tight coordination between the engine’s requests and the driver’s memory management. If a driver mismanages residency, meaning the data describing where a given texture or model actually sits in GPU memory, the engine’s request for a tree or terrain chunk can fail silently, and the world renders without it instead of throwing an error. That distinction matters for severity: a black texture is a cosmetic failure layered on a scene that still loads, while a missing forest chunk is the streaming system failing a request outright, which is consistent with why some of the pre-driver-update footage looked closer to partially unloaded levels than ordinary graphical corruption.
Why ray tracing and path tracing made it worse
The remaster’s ray tracing and path tracing modes compounded both problems rather than existing as a separate issue. Ray-traced lighting and reflections depend on an acceleration structure, essentially a map of where every object in a scene sits, built from the same geometry and texture data the base renderer uses. If a texture is already rendering as a null black state or a forest chunk failed to stream in, the ray tracing pass inherits that broken input and can amplify it, since reflections and global illumination sample from whatever is actually present in the scene, errors included. Path tracing’s denoiser, which smooths noisy ray-traced output into a clean image, can also misbehave when it’s processing a frame that already contains corrupted source data, which lines up with the flickering and shimmering some players reported layered on top of the underlying black-texture and missing-vegetation bugs. That compounding effect matches reports that disabling ray tracing and path tracing reduced, without fully eliminating, the severity of visual bugs for Radeon owners still waiting on a complete fix.
The driver timeline CD Projekt Red didn’t control
The root of the problem appears to be a driver-release timing squeeze rather than a game-code defect specific to AMD hardware. CD PROJEKT RED’s customer support account published a pre-launch driver recommendation: “Before you dive in to The Witcher 3: Wild Hunt – Remastered, make sure your graphics drivers are updated to the recommended version: NVIDIA: 617.14 AMD: 26.9.2 – not released yet, coming later Intel 32.0.101.8993.” At the time that recommendation went out, the most recent generally available AMD driver was Adrenalin 26.8.1, released August 20, roughly six weeks before the remaster’s launch window, with nothing newer on offer for Radeon owners trying to prepare in advance. AMD closed that gap on the day it mattered most: the Adrenalin 26.9.2 driver, adding official support for the remaster, went out on September 29, 2026, the same day the game went live, rather than days or weeks afterward.
CD PROJEKT RED’s support account posted directly about the situation, writing: “AMD users: the latest GPU drivers are now available! If you’ve been experiencing visual issues in The Witcher 3: Wild Hunt – Remastered, please make sure to download and install the latest drivers.” The same account’s pre-launch guidance had explicitly flagged the AMD driver as “not released yet, coming later,” which means the studio knew about the gap before launch day and shipped anyway rather than delaying. That is a notable decision for a marquee free-upgrade release built to generate goodwill and renewed sales interest a decade after the original game shipped.
TechSpot’s benchmark coverage of the remaster put it bluntly: “The publicly available Adrenalin 26.9.1 driver was effectively unusable in our testing, producing numerous rendering glitches.” The same outlet added that “Radeon GPUs appear to be running into some kind of performance limitation, likely driver-related, which becomes even more obvious when testing the Medium preset.” That detail matters because it suggests the problem was not limited to high-end ray tracing configurations. It showed up even in lower-demand rendering modes, which points toward a driver compatibility gap rather than a hardware ceiling being hit.
TechSpot’s own benchmark numbers came with an asterisk worth noting: rather than testing on the public 26.9.1 build, the outlet obtained and ran a pre-release AMD driver, build 26.20.15.02, specifically because the publicly available 26.9.1 driver was producing too many glitches to generate usable benchmark data. That detail is a useful data point on its own. It means the performance and stability picture most Radeon owners actually experienced at launch, stuck on the public driver rather than an unreleased internal build, was likely rougher than what showed up in benchmark coverage running newer, unreleased driver code.
Once AMD’s 26.9.2 WHQL driver rolled out on September 29, the same day as launch, reports indicate meaningful improvement for many affected users, though plenty of players were already mid-session on the old driver before the update reached them.
Why a same-day driver didn’t stop the bug reports
AMD didn’t let the gap between its pre-launch messaging and an actual download run for weeks. The company released the Adrenalin 26.9.2 driver on September 29, 2026, the same calendar day the remaster went live, adding official game support and targeting the rendering problems directly. That is noticeably faster than the “not released yet, coming later” framing in CD Projekt Red’s earlier advisory suggested.
Same-day isn’t instant, though. Steam, GOG, and Epic all pre-load purchased and owned titles ahead of a game’s unlock time, which means a meaningful share of the remaster’s PC audience had the game installed and ready to launch the moment it unlocked, whether or not they had separately gone and installed a brand-new GPU driver that dropped on that same day. Driver updates aren’t automatic the way a game patch often is. A player has to notice the release, download it through AMD’s software or site, and restart before it takes effect. For a driver that lands on launch day itself rather than days in advance, it’s entirely plausible for thousands of players to be well into their first play session before 26.9.2 ever reaches their system.
That distribution lag, measured in hours rather than the weeks implied by a driver simply not existing yet, lines up with what reporters documented: a wave of black-texture and missing-vegetation complaints concentrated in the launch window, followed by posts crediting the driver with fixing the problem once players actually installed it. It also means AMD’s response was faster than the pre-launch messaging implied, even though the practical experience for a chunk of Radeon owners on day one looked identical either way: boot up the remaster, see broken rendering, go looking for a driver update.
Nvidia’s comparatively smooth launch
The contrast with Nvidia hardware is one of the more striking parts of this story. Multiple outlets, including virus.hr and IGN, reported that GeForce users were generally able to run the remaster without the widespread corruption Radeon owners experienced. That does not mean Nvidia’s launch was flawless. A GOG forum discussion mentioned occasional path-tracing glitches and rendering inconsistencies even on Nvidia systems, but described those as limited issues rather than the systemic, reproducible failure pattern seen on AMD hardware.
That asymmetry is part of what makes this launch notable in the context of the remaster’s earlier RTX 5090 performance story, where the flagship Nvidia card fell one frame short of a locked 60 FPS target. Nvidia owners have a performance conversation to have. AMD owners, for a window of time, had a playability conversation instead. Those are very different categories of launch problem, and only one of them is solved by patient benchmarking.
A recurring pattern for CD Projekt Red and AMD hardware
It’s worth being precise about what can and can’t be claimed here. Available reporting does not establish a continuous, well-documented history of identical AMD-specific failures stretching back to the original next-gen update for The Witcher 3. What the current evidence supports is narrower: a new, standalone 2026 remastered release, a concentrated AMD driver and rendering problem specifically tied to this launch, and a pattern of community-sourced fixes filling the gap before an official driver caught up. Broader industry context is still relevant, since driver-timing mismatches between major PC game launches and GPU vendor driver cycles are a recurring friction point across the industry, not unique to this one title, and they tend to hit whichever vendor’s driver team is racing a publisher’s launch date rather than setting it.
What CD Projekt Red has and hasn’t said
CD PROJEKT RED’s public response in the first days after launch was limited to the driver-update advisory posted through its support account, rather than a dedicated emergency game patch aimed specifically at the AMD rendering bugs. That changed, at least partially, on October 8, 2026, when the studio shipped Update 5.01, the remaster’s first substantial patch since launch, adding graphics improvements and performance enhancements. A GOG discussion thread had indicated the studio was signaling forthcoming patches addressing issues including incorrect vegetation rendering, and Update 5.01 lines up with that signal in timing, but its notes still don’t itemize fixes specific to the AMD rendering complaints by name. The gap between forum-level reporting and a formal, AMD-specific patch note remains, even with a real patch now shipped. For a studio that built its post-launch reputation on aggressive patching after Cyberpunk 2077’s troubled 2020 debut, the response so far has leaned more on “update your drivers” and general patch notes than a targeted, same-day hotfix calling out the Radeon-specific bugs.
That distinction matters for accountability. A driver-side fix from AMD addresses the rendering corruption, but it doesn’t resolve the underlying question of why a studio would ship a marquee remaster while knowingly listing a recommended GPU driver that had not yet been released to the public. Whether that was an unavoidable scheduling collision between AMD’s driver team and CD Projekt Red’s launch date, or a decision to launch on time regardless of driver readiness, has not been addressed in any statement documented so far.
Workarounds players are actually using
With an official patch not yet fully documented, the fix landscape right now is a mix of one legitimate vendor-level solution and several community workarounds of varying reliability. The clearest fix is checking AMD’s official support and driver download page for the Adrenalin 26.9.2 WHQL driver once it’s available for a given system, which multiple reports credit with resolving the bulk of the black-texture and missing-vegetation problems. For players who install 26.9.2 and still see issues, community threads recommend a clean driver installation using Display Driver Uninstaller (DDU) followed by deleting the shader cache before relaunching the game.
A smaller group of players reported that rolling back to the much older Adrenalin 26.3.1 driver fixed specific artifacts, notably the glowing-hair and black-rendering combination, in cases where the newer recommended driver did not. That is explicitly a community-sourced workaround rather than an AMD-endorsed fix, and rolling back several driver generations carries its own tradeoffs for other games and applications running on the same system. For players hitting severe corruption or repeated crashes, the most conservative advice circulating is simply to hold off on playing the remaster on AMD hardware until a stable, fully released driver is confirmed working, and to disable or reduce ray tracing and path tracing settings in the interim if those modes are triggering the worst artifacts.
| Workaround | Source | Status |
|---|---|---|
| Install AMD Adrenalin 26.9.2 WHQL | Multiple user reports, GOG forums | Most credited fix |
| Clean install via DDU + delete shader cache | Community suggestion | Unofficial |
| Roll back to Adrenalin 26.3.1 | Steam community forums | Unofficial, fixes some artifacts only |
| Disable/reduce ray tracing and path tracing | GOG forums, IGN | Unofficial, reduces but may not eliminate bugs |
| Delay play until driver confirmed stable | IGN reader advice | Conservative fallback |
Why this keeps happening at major PC launches
The Witcher 3 Remastered situation is a specific case of a general problem in PC gaming: publishers set launch dates on their own schedules, while GPU vendors set driver release schedules on theirs, and the two don’t always line up. When a AAA launch and a GPU driver cycle collide badly, the GPU vendor whose driver misses the window takes the reputational hit even though the underlying game code may be fine. This dynamic is why driver readiness has become as closely watched around major releases as the games themselves, and why day-one driver packages from both AMD and Nvidia are now treated as part of a launch rather than a side note.
For a game as heavily benchmarked and widely owned as The Witcher 3, the stakes are higher than usual. This isn’t a niche indie title with a small day-one audience testing new hardware paths. It’s one of the best-selling PC games of the last decade getting a marquee visual overhaul, running headfirst into exactly the kind of vendor-driver timing gap that smaller, lower-profile releases can usually absorb without much notice.
What this means for AMD’s FSR 4 push
The timing is awkward for AMD specifically because the remaster is one of the more prominent showcases yet for FSR 4, including Frame Generation and Anti-Lag 2, running on RX 7000-series and newer hardware, the same broad lineup covered in AMD’s rollout of its FSR Redstone upscaling technology for RX 9000-series cards. Having flagship RX 9000-series cards visibly breaking on a title meant to highlight AMD’s newest upscaling and frame-generation stack undercuts the marketing value of that feature set, at least for the launch window before the fix rolled out. AMD has been trying to close the perception gap with Nvidia’s DLSS ecosystem, and a widely shared video of an RX 9070 XT rendering black grass and corrupted skin textures is the kind of clip that outlives the driver fix that eventually resolves it.
Broader context: remasters and driver risk
This launch adds to a growing list of examples where remasters and re-releases of older games introduce new PC-side risk rather than reducing it. Rebuilding lighting, adding ray tracing and path tracing support, and integrating newer upscaling technology like FSR 4 and Intel XeSS 2.0 means touching rendering paths far more extensively than a simple resolution bump. Each of those additions is a new surface area for driver-specific bugs to appear, even on a game whose base code has been stable and widely tested for more than ten years. The remaster’s use of ray tracing and path tracing, along with Intel XeSS 2.0 with Frame Generation and Low Latency support, means there are now three separate upscaling and frame-generation ecosystems the game has to behave correctly across, each tied to its own vendor driver cycle.
That complexity is also relevant to broader PC hardware coverage this year, including ongoing scrutiny of next-generation GPU release timing from both Nvidia and AMD and continued attention on how current-generation GPUs perform without AI-assisted rendering features. As more games lean on multiple competing upscaling stacks simultaneously, the odds of a launch-day mismatch on at least one vendor’s hardware appear to be rising rather than falling.
Market and reputational impact
For CD Projekt Red, the immediate impact is reputational rather than financial in any measurable sense yet, since the remaster is a free upgrade for existing owners rather than a new paid product with refund exposure at scale. But goodwill matters for a studio still rebuilding trust after Cyberpunk 2077’s 2020 launch problems. A visible AMD-specific bug wave on a free celebratory remaster, even one caused primarily by a GPU vendor’s driver timing rather than CD Projekt Red’s own code, still lands as a launch-day black eye that dominates early social media chatter and video coverage instead of the remaster’s actual improvements.
For AMD, the impact is arguably sharper because the affected hardware includes its newest RX 9000-series cards, the ones it most needs to look competitive against Nvidia’s current lineup in high-visibility PC gaming coverage. A driver gap that leaves flagship-tier Radeon GPUs “completely broken,” in the words of the GOG forum thread describing pre-update RX 9000-series performance, is a costly optics problem regardless of how quickly the eventual fix arrives.
Steam reviews and the scale of the backlash
The launch-day numbers
The reputational damage shows up directly in Steam’s review data. More than 1,100 negative reviews were recorded on launch day alone, representing 32% of all reviews posted that day, according to an October 15, 2026 report from PC Guide. That is a large share of negative sentiment for a free upgrade to an already decade-old, critically acclaimed game, and it lines up with the black-texture and missing-vegetation complaints documented across virus.hr, IGN, and the GOG and Steam community forums in the same window.
Why the driver fix didn’t reverse the trend
What stands out in PC Guide’s reporting is that the negative-review pace didn’t stop once Adrenalin 26.9.2 became broadly available. Negative reviews kept arriving even after players had a working driver to install, which suggests at least part of the backlash is about the launch experience itself rather than something a driver update alone can retroactively erase. A player who hit black grass and crashes on day one and left a negative review generally doesn’t go back and revise that review once a fix ships days later. That is a separate problem from the technical bug for CD Projekt Red and AMD to manage: fixing the rendering issue helps future players, but it doesn’t recover the review-score damage the launch-week audience already logged. Combined with the AMD-specific driver-timing failure, the review pattern adds a second, harder-to-reverse cost to a launch that was designed as a low-risk goodwill gesture for existing owners rather than a new paid release.
Where the AMD situation stands now
As of October 2026, the Adrenalin 26.9.2 WHQL driver that AMD shipped on launch day remains the baseline recommendation for Radeon owners installing the remaster for the first time. Reports credit it with resolving the bulk of the black-texture, missing-vegetation, and glowing-hair complaints that defined the first 24 to 48 hours after the September 29 launch, and the loudest wave of bug reports has not repeated at the same volume in the weeks since. That credit comes from user testimony and outlet observation rather than AMD’s own documentation, though: an October 15, 2026 report from Mixed-News noted that AMD listed 26.9.2 as an optional update within its own software hub rather than a required one, and that the driver’s release notes never explicitly confirmed a fix for the Witcher 3 rendering fault. An unconfirmed fix that nonetheless appears to work for most affected users is still consistent with a driver-timing problem rather than a permanent hardware incompatibility: once the correct driver reaches a given system, the reported symptoms largely go away.
That doesn’t mean every thread is closed. Community forums on Steam and GOG continue to reference the older Adrenalin 26.3.1 rollback as a workaround for the specific glowing-hair artifact on some configurations, which suggests a subset of Radeon users are still chasing an edge case that 26.9.2 didn’t fully resolve. CD Projekt Red’s October 8 Update 5.01 added graphics improvements and performance enhancements, but, as with the driver itself, it still hasn’t published a fully itemized, AMD-specific patch note addressing the vegetation and texture issues independent of the driver fix, so the official record of what was a driver problem versus what required a game-side fix remains incomplete. For players picking up the remaster for the first time now, the practical guidance hasn’t changed: confirm Adrenalin 26.9.2 or newer is installed before launching on Radeon hardware.
Predictions: where this goes from here
- AMD will likely continue rolling WHQL-certified updates to 26.9.2 and beyond across its driver distribution channels over the coming days, narrowing the gap between users still on 26.8.1 or earlier and those with the fix.
- CD Projekt Red has already shipped one post-launch patch, Update 5.01 on October 8, 2026, with graphics improvements and performance enhancements, and will probably issue further updates addressing vegetation rendering and other AMD-flagged visual issues more specifically, following the pattern described in GOG forum discussions of planned fixes.
- Expect renewed scrutiny of pre-launch driver certification processes for major PC releases, with more publishers pushed to either delay launches or publish clearer day-one compatibility disclaimers when a vendor driver isn’t ready.
- AMD’s FSR 4 marketing push tied to this remaster will likely take a temporary hit in community sentiment, even after the driver fix lands, since early impressions and video clips tend to circulate longer than the fixes that resolve them.
- Community-sourced workaround guides, including driver-rollback instructions, will likely remain in circulation on forums like Steam Community and GOG for weeks after an official fix ships, since not every affected player will immediately see driver-update prompts or coverage of the fix.
What players should do right now
If you’re on AMD Radeon hardware and haven’t launched the remaster yet, the most straightforward step is following a proper process to update your graphics card drivers and confirming whether Adrenalin 26.9.2 WHQL is available for your specific card before installing the game. If you’ve already hit black textures, missing vegetation, or glowing hair artifacts, updating to that driver resolves the issue for most reported cases. If problems persist after updating, a clean reinstall via DDU followed by clearing the shader cache is the next community-recommended step, and disabling ray tracing or path tracing temporarily can reduce the severity of remaining visual bugs while a full fix is pending. Anyone hitting repeated crashes rather than just visual corruption should hold off entirely until the driver situation stabilizes further, since instability is a different risk category than cosmetic rendering bugs.
Frequently Asked Questions
Is The Witcher 3 Remastered broken on all AMD GPUs?
No. Reporting points to widespread issues concentrated on Radeon GPUs as a class, with RX 9000-series cards specifically called out as severely affected before a driver update. Available sources don’t establish that every AMD card is affected equally, and some players report a clean experience depending on driver version.
What AMD driver fixes the Witcher 3 Remastered bugs?
CD Projekt Red’s official recommendation was AMD Adrenalin 26.9.2, which AMD released on September 29, 2026, the same day as the remaster’s launch, adding official support for the game. Multiple user reports credit the WHQL build with resolving the bulk of the black-texture and missing-vegetation issues once it reached their systems.
Does Nvidia have the same issues in the remaster?
Reports indicate Nvidia GeForce users generally experienced a functional launch, with only occasional, limited path-tracing glitches mentioned in community forums, a much smaller footprint than the AMD-specific problems.
Has CD Projekt Red released a patch for the AMD issues?
Partially. The studio’s initial response centered on advising AMD users to install the latest GPU drivers, and on October 8, 2026 it shipped Update 5.01, adding graphics improvements and performance enhancements. That patch’s notes still don’t itemize fixes specific to the AMD rendering bugs by name, so a fully itemized, AMD-specific patch note has not been broadly documented yet.
Did The Witcher 3 Remastered get review-bombed on Steam?
Steam recorded more than 1,100 negative reviews on launch day, about 32% of that day’s total, according to an October 15, 2026 PC Guide report. Negative reviews kept coming in even after the Adrenalin 26.9.2 driver fix became available, indicating the backlash wasn’t fully resolved by the driver update alone.
What platforms is The Witcher 3 Remastered available on?
The remaster launched as a free upgrade on PC via Steam, GOG, and Epic Games Store, as well as PlayStation 5 and Xbox Series X/S.
Should I roll back my AMD driver to fix the remaster?
Some players reported that rolling back to Adrenalin 26.3.1 fixed specific artifacts like glowing hair, but this is an unofficial community workaround, not an AMD-endorsed fix, and older drivers can affect performance or compatibility in other games.
Does disabling ray tracing fix the AMD bugs?
Disabling or reducing ray tracing and path tracing settings appears to reduce the severity of some reported visual bugs, according to forum discussions, but it is not confirmed as a complete or officially recommended fix.
Did AMD’s day-one driver fully fix the problem?
Largely, but not completely. AMD shipped Adrenalin 26.9.2 on September 29, 2026, the same day as launch, and most reports of black textures and missing vegetation cleared up once players installed it. A smaller subset of Radeon owners still reported the glowing-hair artifact persisting on 26.9.2 and found a rollback to the older 26.3.1 driver fixed that specific issue, which indicates at least one edge case the day-one driver didn’t fully address.
Is this the first time The Witcher 3 has had AMD-specific problems?
Available reporting does not establish a documented history of identical AMD-specific issues going back to the original 2024-era next-gen update. What’s confirmed is that this specific 2026 remastered release has a concentrated, driver-related AMD problem at launch.
