Hey!
Can confirm the same issue.
I am using RTX 3070, driver ver. 595.71.05.
CachyOS Kernel 7.0.10-1-cachyos
It might be an NVIDIA issue. I played about an hour without any issues on AMD Radeon 6750XT, Kubuntu 26.04.
Thanks for the reports everyone! I have created bug 6225934 for tracking this issue within NVIDIA.
Running flawlessly for me on Proton Experimental (bleeding edge as of May 26th 3pm pacific - sorry, unsure where to get the specific version information - the python file lists 'CURRENT_PREFIX_VERSION="11.0-100"')
5090 on 595.71.05
7.0.10-1-cachyos
KDE + Wayland
for me it was possible to bypass the issue by turning on DLSS framegen and performance mode
4060 Ti on 595.71.05
Fedora 44 KDE (Wayland)
Running flawlessly for me on Proton Experimental (bleeding edge as of May 26th 3pm pacific - sorry, unsure where to get the specific version information - the python file lists 'CURRENT_PREFIX_VERSION="11.0-100"')
5090 on 595.71.05
7.0.10-1-cachyos
KDE + Wayland
I tried this too but am still having the issue.
Gameplay seems fine, but cutscenes are a bit hit-or-miss. Turning DLSS on to the Dynamic setting let me past the opening cutscene but would freeze on later ones. Running the bleeding-edge Proton Experimental.
Having three distinct issues:
I can see both (1) and (2) being mistaken for freezes, the truth is if you wait them out (sometimes like 3+ minutes) the game does resume.
There's also this in dmesg
[1897022.986665] umip: 007FirstLight.e[935164] ip:149538554 sp:10b8f8: SGDT instruction cannot be used by applications.
[1897022.986670] umip: 007FirstLight.e[935164] ip:149538554 sp:10b8f8: For now, expensive software emulation returns the result.
[1897022.987436] umip: 007FirstLight.e[935164] ip:149538554 sp:10b8f8: SGDT instruction cannot be used by applications.
[1897606.975056] umip_printk: 201 callbacks suppressed
Running on Proton Experimental
RTX 4090
NVIDIA 595.71.05
ArchLinux 7.0.3-arch1-2
EDIT: Looks like DLSS + FrameGen is what is causing both (1) and (2).
The drivers haven't hit the Fedora repos yet, but I am curious if anyone has had any success with the new 610 driver series that came into the new feature branch yesterday.
It isn't just in cutscenes unfortunately. Sometimes it just happens anyway for some reason after loading a save.
I'm on a 4080 and 9800x3d and could play for a long hour today after updating everything on CachyOS through Octopi.
I enabled DLSS and Super Resolution and was using Proton Hotfix.
I also played through the first two chapters on windows though. I doubt that matters because I went through a handful of cutscenes on the proton side and it went smoothly with just a couple of hiccups
Will there ever be a time for me to run all the games without any problems? These damn corporations do everything to make the games only for Windows
update to 610.43.02 nvidia driver didn't fix this issue. still get long freeze and crash with infamous xid 109.
May 29 01:48:28 cachyos kernel: NVRM: Xid (PCI:0000:01:00): 109, pid=13479, name=007FirstLight.e, channel 0x00000019, errorString CTX SWITCH TIMEOUT, Info 0x32c02e
So as of today the game crashes for me about 10 seconds after loading into it. Tried different proton versions (experimental, GE10-34, Proton 11 beta, etc.). They show the same behaviour. Start game - Load last save - wait a few seconds - crash
Just yesterday I was able to play without any issue for about 2-3 hours.
Got it to work again after going back to Experimental and now I am not sure if it is a game bug or a proton thing. I was at Act 4 Aleph on the step where you had to enter the auction. If you wait too long after the game loads it will crash a few seconds later but if you start to move it the game will continue to run.
For me, it just opens a black window in the background, and I can hear it, but I can't focus it. Tried with Proton Experimental and default Proton.
Edit: I managed to "fix" it by using gamescope, but now I'm having another issue. It will after awhile of playtime just halve my FPS, and I have to restart it to get it back.
007_proton_excerpt.txt Hello everyone! If you're having the same problem as me, it would help if we collect and curate proton logs. you can set them in your launch instructions using PROTON_LOG=1 %command% .
Proton log for me shows Enhanced Barriers fixme spam immediately after swapchain recreate on level load (~514k times over 65 seconds), followed by Xid 109 CTX SWITCH TIMEOUT.
This is probably a bug in the translation layer between vulkan and d3d.
~So as of today the game crashes for me about 10 seconds after loading into it. Tried different proton versions (experimental, GE10-34, Proton 11 beta, etc.). They show the same behaviour. Start game - Load last save - wait a few seconds - crash~ Just yesterday I was able to play without any issue for about 2-3 hours.
Got it to work again after going back to Experimental and now I am not sure if it is a game bug or a proton thing. I was at Act 4 Aleph on the step where you had to enter the auction. If you wait too long after the game loads it will crash a few seconds later but if you start to move it the game will continue to run.
This is exactly my issue. could you also run it using a proton log and look for Enhanced Barriers in the log? it might shed some light if other people are having the same issue.
This is exactly my issue. could you also run it using a proton log and look for Enhanced Barriers in the log? it might shed some light if other people are having the same issue.
Unfortunately if you load back into that part of the story as a replay you are not entering at that point in time but already past the guard. And I do not have a manual save game for that specific point. Bummer.
The game sticks at the same moment, also fps drops to 3-5 from time to time and then gets back to normal
@juppstein @rhamnos can you be more specific about when the issue happens? https://www.youtube.com/watch?v=ATaOpJ6T4sQ here's a video of act 4 so having a pinpoint of when it's supposed to happen would be helpful.
For me, it just opens a black window in the background, and I can hear it, but I can't focus it. Tried with Proton Experimental and default Proton.
Edit: I managed to "fix" it by using gamescope, but now I'm having another issue. It will after awhile of playtime just halve my FPS, and I have to restart it to get it back.
im having exactly same issue with same log
i hope it will help
For me, it just opens a black window in the background, and I can hear it, but I can't focus it. Tried with Proton Experimental and default Proton.
Edit: I managed to "fix" it by using gamescope, but now I'm having another issue. It will after awhile of playtime just halve my FPS, and I have to restart it to get it back.
ive tried it my seems not helping
Tryed different distros,x11/Wayland,some launch commands,another proton versions,c++ 2022 resist,gamescope, nothing helps
In the Null space - "follow moneypenny", the script does not launch
007 First Light (3768760)
Issue transferred from https://github.com/ValveSoftware/Proton/issues/9941.
@by-edartg posted on 2026-07-02T17:20:29:
Tested using: Proton Experimental Jun. 27, 2026, Mesa 26.2.0-devel, RX580 Nitro+ 8GB.
I apologize for taking up your time, I know you are incredibly busy, but I would like to ask a quick question about the possibility of running the game on older hardware.
Is there any chance that "007 First Light" will become fully playable on Polaris and Vega (gfx8) graphics cards in the future? Currently, only two episodes work (if a save file from an already completed game has been loaded). Without a save file, the game crashes or fails to load during the introductory cutscene.
Do you think this is something that could eventually be fixed through future RADV driver updates or new Proton versions?
proton experimentalx8 2026-07proton hotfixx1 2026-05ge-proton10-34x1 2026-05PROTON_LOG=1x1 2026-05
Compatibility Report
System Information
I confirm:
steam-3768760.tar.gz
Symptoms
Video freezes about 10-15 seconds into the opening cutscene. Audio and controller vibration continues to function but the game has to be killed.
Reproduction
Start the game, load into the game and watch the opening cutscene.