F1 23
The game claims to be Steam Deck compatible, and other people on ProtonDB.com say that the game runs, so maybe I'm just in a small subset that are having issues. - None of those people are running on NVidia cards either though...
Can confirm you're not alone
System Information
- GPU: 6800 XT
- Driver/LLVM version: Mesa 23.1.3
- Kernel version: 6.4.3-arch1-1
- Link to full system information report as Gist:
- Proton version: experimental-8.0-20230705b
I confirm:
Symptoms
- Game starts and runs but low fps (30-60) vs Windows (120). Running mangohud shows GPU <50% usage and CPU ~20%. Consistent stuttering. Graphical settings, resolution does not affect result
- Graphical artifacts around helmet
- No issues with F122 or F121
Reproduction
- Start game
- Run benchmark
I reproduced the freezes on startup. It also freezes if it goes straight to the menu instead of the news screen. I get a Xid 69 in dmesg, but I wasn't able to get much info out of the breadcrumbs. It no longer freezes if I downgrade to 530.41.03.
- GPU: GTX 1660 Ti
- Driver: 535.54.03
- Kernel: 6.4.3-arch1-1 and 6.1.38-1-lts
- Proton: Experimental bleeding-edge
NVRM: GPU at PCI:0000:08:00: GPU-a8fb3a3a-9dd5-b430-1b78-cb1f1ecd6079
NVRM: Xid (PCI:0000:08:00): 69, pid=4562, name=F1_23.exe, Class Error: ChId 011b, Class 0000c597, Offset 00002388, Data fffffff0, ErrorCode 00000004
032c:err:vkd3d_breadcrumb_tracer_report_device_lost: Device lost observed, analyzing breadcrumbs ...
032c:fixme:vkd3d_breadcrumb_tracer_report_queue_nv: Markers have different contexts. Execution is likely split across multiple command buffers?
032c:err:vkd3d_breadcrumb_tracer_report_device_lost: Done analyzing breadcrumbs ...
As in all previous games, using the Logitech G29, the pedals are incorrectly mapped.
Although they can be remapped in the preferences, this makes instant replay unusable, which always leaves the camera looking back.
A bit frustrating...
Getting the same issue as the submitter - Attempted on both Proton 8.0-3 and Proton Experimental.
System Info
GPU: RTX 3080TI
Driver/LLVM version: NVIDIA 535.86.05
Kernel version: 6.4.4-arch1-1
Hi, this and f1 22 are the only games where VR doesn't get sent to the headset, instead the headset just stays in the dark sky transition screen while there's a perfectly viable rendered (left eye I think) on my screen tracking and everything.
I am on:
Arch Linux 6.4.7.arch-1-1
mesa 23.1.4-2
AMD RX 6750XT
Valve Index
Proton Experimental Bleeding Edge
Btw the normal game works decently (although the GPU is pulling 200W in the main menu for some reason)
Game seems to be running on proton 7.0.6, possibly a proton 8 issue
OS: NixOS 23.05.20230822.a16f7eb (Stoat) x86_64
Kernel: 6.4.11-xanmod1
GPU: NVIDIA GeForce RTX 3090 535.86.05 with open-source kernel module
I'm with AMD RX 6800 and Mesa 23. The game runs both in Proton 7 and 8. But in 8, I got helmet graphical artifacts.
Hello @DaRacci, @yaliv, please add PROTON_LOG=1 %command% to the game's launch options, reproduce the regressions you're seeing, and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.) Also, please copy the contents of Steam Runtime Diagnostics from Steam (Steam -> Help -> Steam Runtime Diagnostics) and put it in a gist, then include a link to the gist in this issue report.
@yaliv, can you also include a screenshot of the misrendering you're seeing?
@kisak-valve here's my report:
Screenshots with Proton 7
Screenshots with Proton 8
The graphical artifacts on the helmet look a lot like dirt :nauseated_face:
@kisak-valve
Below is the final screen that is reached in proton 8 is the main menu, before I was able to launch and dismiss it in proton 7 it would be the news menu.
Thanks @DaRacci, as a quick test, can you try running the game with Proton 8.0 and setting the game's launch options toVKD3D_DISABLE_EXTENSIONS=VK_KHR_present_id,VK_KHR_present_wait %command%?
Thanks @DaRacci, as a quick test, can you try running the game with Proton 8.0 and setting the game's launch options to
VKD3D_DISABLE_EXTENSIONS=VK_KHR_present_id,VK_KHR_present_wait %command%?
I tried it with Proton Experimental bleeding edge, it's the same
@kisak-valve yeah same situation steam-2108330.log
@DaRacci @CatalinPuscoci I was able to reproduce this issue, but only when using the Nvidia 535 drivers. I couldn't repro using the Nvidia 525 drivers. Could you try installing the 525 drivers and see if that fixes the issue?
I am on AMD/mesa 23.1 But something in the lastest Proton experimental/Bleeding Edge fixed it
Oh, apologies @CatalinPuscoci. I thought you were having the same issue as DaRicci. The fix for the "dirty helmet" was a vkd3d-proton fix by the way :)
Oh, apologies @CatalinPuscoci. I thought you were having the same issue as DaRicci. The fix for the "dirty helmet" was a vkd3d-proton fix by the way :)
Oh I had a very similar thing, but the effect was slightly different (it was square-y and blocky like Variable Rate Shading artifacting)
@DaRacci @CatalinPuscoci I was able to reproduce this issue, but only when using the Nvidia 535 drivers. I couldn't repro using the Nvidia 525 drivers. Could you try installing the 525 drivers and see if that fixes the issue?
Seems like that did indeed resolve the issue, cheers
@yaliv The fix for this should now be available in latest Proton Experimental.
@yaliv The fix for this should now be available in latest Proton Experimental.
Great! I can confirm that.
Can confirm that I have the same black screen with music freeze issue as described by @caoimhebyrne and @DaRacci.
GPU: NVIDIA GeForce RTX 3070 Ti
Driver version: 535.113.01
OS: Arch Linux
Kernel: 6.5.7-zen1-1-zen
It's resolved for me by using Proton 7.0-6.
Furthermore, the game is now triggering Denuvo's CodeFusion five devices per day anti-tamper restriction.
I don't have the loading freeze but the game stutters a lot when using certain maps (Monaco) and might even crash after some time.
Running telegraf on the machine I was able to deduce that the GPU only ran at max P2 Powerstate, even at 100% utilization. Temps are not going above 65C. All other levels seem normal.
GPU: NVIDIA GA104 GeForce RTX 3060 Ti LHR
Driver version: 535.129.03
OS: Ubuntu 23.04 (Lunar Lobster)
Kernel: 6.2.0-39-generic x86_64
F1 23 now outputs to my VR headset. Now I have to see if I can get the HUD to work on the headset!
@Alexithymia2014 Are you using Nvidia, if so what driver and model?
I'm using a Radeon 7900XTX. I can't get the HUD to show at all on my headset even with configuring the OSD. It only shows on the game window on my desktop. Full immersion I guess!
[BUG] F1 23 does not render UI elements on headset
Issue transferred from https://github.com/ValveSoftware/SteamVR-for-Linux/issues/785.
@Alexithymia2014 posted on 2025-05-11T00:41:33:
Describe the bug
When playing F1 23, the game does not start floating in the world as it does on Windows. Additionally, once you get into a race, it will not show the UI elements like buttons or any on screen displays like laps, time, map, etc.
To Reproduce
Steps to reproduce the behavior:
- Launch F1 23 in SteamVR mode
- Observe that the game doesn't launch in a floating window on the headset, it's just black
- Go to F1 World
- Start a time trial
- Choose any track and car
- Observe that the buttons on the bottom right as display on the monitor does not appear in the headset.
- Go out onto track.
- Observe there isn't the race menu in the bottom right. Any configured OSDs aren't showing on the headset either.
Expected behavior
The game should start in floating mode on the headset.
The game should also show OSD elements on the headset in addition to the monitor.
System Information (please complete the following information):
Please use the latest Steam beta client and SteamVR beta for your bug reports!
- Steam client version (build number or date):
- SteamVR version: 2.10.4
- Distribution (e.g. Ubuntu): Arch Linux
- Steam runtime diagnostics:
- Steam and SteamVR logs: [generate by running this command in a terminal
tar -zcvf ~/Desktop/steam-logs.tar.gz ~/.steam/steam/logs] - Minidumps: [run the following command:
tar -zcvf ~/Desktop/steam-minidumps.tar.gz /tmp/dumps]
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Not sure if this is a Proton, VKD3D-proton, or SteamVR bug. I've reported it on the relevant Proton page previously.
Problems running F1 23
Issue transferred from https://github.com/ValveSoftware/Proton/issues/9036.
@notreweee posted on 2025-09-08T13:16:25:
Hi, I'm using Ubuntu and I'm trying to run the game F1 23, but every time I open it, after a few minutes, I get the same problem. I've tried all Protons, but I'm currently using Proton 7 and the Nvidia 535 driver.
Can anyone help me?
Proton versions
proton 7.0-6x1 2023-10proton experimentalx6 2023-09proton 8.0x2 2023-08proton 7.0x1 2023-08proton 8.0-3x1 2023-07
Launch options
VKD3D_DISABLE_EXTENSIONS=VK_KHR_present_id,VK_KHR_present_waitx2 2023-08PROTON_LOG=1x1 2023-08
Launch lines
Upstream links
- ValveSoftware/Proton/issues/9036x1 2025-09
Compatibility Report
System Information
I confirm:
steam-2108330.log
Symptoms
The game seems to start fine, but once you get through the title sequence and the "Press any button" screen, the game will lock after it transitions to the News screen.
It seems to do this automatically for me, but I played on Windows before, so maybe it's doing it automatically since I haven't played in a while.
I've tried spamming buttons before the freeze happens to try and close the news screen, but that doesn't seem to work. Whilst the screen has frozen, I can still hear audio in the background playing properly.
Here's a screenshot of where my game freezes for reference:
Some other relevant notes:
flatpak updatesaying that there is 'Nothing to do'.Reproduction