007 First Light Update 1.2.1 Fixes Nine Path Tracing Crashes on PC
IO Interactive has shipped hotfix 1.2.1 for 007 First Light, and the 007 First Light update 1.2.1 notes are almost entirely about crashes: nine path tracing faults across Chapters 01, 03, 06 and 09, plus one stability fix that can hit anyone. It is a PC-side repair job, landing two days after the path tracing patch that caused the problems.
007 First Light launched on 27 May 2026 for PlayStation 5, Xbox Series X|S and PC, with a Nintendo Switch 2 version still scheduled for March 2027. Path tracing is a PC feature only, so console players never saw the crashes this hotfix removes. The one exception is the stability entry below, which is not tied to any rendering setting.
What 007 First Light update 1.2.1 fixes
The studio groups the notes into two sections. The stability fix is the one that matters regardless of your graphics settings: a crash that could occur after finishing the mission debrief in Chapter 03, Out of the Ashes, while Bond is travelling to the Q-Lab.
Everything else requires path tracing to be switched on. The list, chapter by chapter:
- Chapter 01, Against the Odds — flame decals on the crashed helicopter no longer cast shadows they should not cast.
- Chapter 03, All the Time in the World — a GPU crash just before the main gate on the intro drive, a freeze and crash during the car chase, and a GPU hang during the abandoned airfield shootout are all fixed.
- Chapter 06, Knightfall — the crash when Bond steps off the cargo lift at the Flight Deck entrance is gone.
- Chapter 06, Going Old School — the Valhalla room no longer blows out to unnatural brightness, which had also crashed the game on a checkpoint reload, and the interrogation room walls no longer render pitch black.
- Chapter 09, Wave of the Future — a crash during the arrival cinematic, and a second crash when quitting to the main menu after path tracing rendering had become corrupted.
That is four of the nine tied to a single chapter, Chapter 06 and Chapter 03 between them accounting for most of the hard crashes. If you shelved the game after the path tracing patch because it fell over on the airfield or at the Flight Deck lift, those are the two specific fixes to look for.
Which platforms and GPUs are affected
Path tracing arrived in 007 First Light on 15 September, PC only, built around GeForce RTX 50 Series desktop cards with DLSS Ray Reconstruction. Nvidia says players without that hardware can still run the path traced version by streaming it through GeForce NOW. PS5 and Xbox Series X|S builds do not offer the mode at all.
AMD owners got something separate in that same patch, and the studio lists it again in these notes: support for AMD FSR Upscaling, previously called FidelityFX Super Resolution 4. On Radeon RX 7000 and RX 9000 cards — RDNA 3 and RDNA 4 — the game now picks FSR 4.1 automatically when you select FSR as the upscaler. Everything else falls back to FSR 3.1.
Performance is still a work in progress
IO Interactive is unusually direct about the state of things. The studio says it is aware players are hitting performance issues, that it is working with Nvidia to investigate the reports, and that it wants to "clarify questions around settings and hardware requirements" — an acknowledgement that the published guidance has confused people.
The studio calls 1.2.1 "the first step", with further updates and hotfixes planned over the next couple of weeks. So this is not the patch that makes path tracing run well; it is the patch that stops it crashing in nine known places. Expect at least one more before the picture settles.
The pattern is familiar for a heavy PC rendering feature arriving months after launch. For comparison on the hardware side, the published PC requirements for Gears of War: E-Day now demand a ray-tracing capable GPU outright, and Silent Hill: Townfall starts at an RTX 2060 Super at the bottom tier. Meanwhile PC players on older cards have been reaching for workarounds like the DLSS Unlocked mod for RTX 20, 30 and 40 series GPUs.
Post-launch hotfixes of this shape have been common this month. Marvel's Wolverine update 01.001.004 took the same approach: a short list, aimed at crashes and blockers, shipped fast rather than bundled into the next content drop.
Do you need to do anything?
No manual step is required. The hotfix downloads through your storefront the same way any patch does, and there is no progression reset, no save migration and no separate path tracing download. If path tracing is switched off in your settings, the only change you will notice is the Chapter 03 debrief crash fix.
Frequently Asked Questions
What does 007 First Light update 1.2.1 fix?
It fixes nine path tracing problems on PC: GPU crashes and hangs in Chapter 03's intro drive, car chase and airfield shootout, a crash at the Chapter 06 Flight Deck cargo lift, lighting faults in the Valhalla and interrogation rooms, and two crashes in Chapter 09. It also fixes a crash after the Chapter 03 mission debrief that is not tied to path tracing.
Is the 007 First Light hotfix on PS5 and Xbox?
Path tracing is a PC-only feature, so the nine rendering fixes do not apply to PlayStation 5 or Xbox Series X|S. The Chapter 03 mission debrief crash fix is the one entry that is not tied to a rendering setting. IO Interactive's notes do not list separate console version numbers.
Does 007 First Light path tracing need an Nvidia GPU?
Yes. The path tracing mode added on 15 September is built around GeForce RTX 50 Series desktop cards using DLSS Ray Reconstruction. Nvidia says players without that hardware can run the path traced version by streaming the game through GeForce NOW instead.
Does 007 First Light support AMD FSR 4?
It does. On Radeon RX 7000 and RX 9000 cards, built on RDNA 3 and RDNA 4, the game automatically selects AMD FSR Upscaling 4.1 when you choose FSR as the upscaling method. Other cards fall back to FSR 3.1.
Will there be more 007 First Light patches?
IO Interactive calls 1.2.1 the first step and says more updates and hotfixes are planned over the next couple of weeks. The studio says it is working with Nvidia on the remaining performance complaints and on clarifying the settings and hardware guidance for path tracing.
