Same for Carmageddon: Reincarnation too (but with even worse performance). Seems like a threading issue?

FWIW, I traced the game on Windows, focusing on the "my garage" view. (I can't get apitrace to work in-game but there's a substantial fps drop when viewing a car, and even worse post-race when all cars are displayed):

On Windows I get a steady 125 fps. With Proton Beta 3.7-5 I get a whopping 13 fps with esync off. With esync on I get around 45 fps. However, replaying the apitrace with Wine and DXVK I average 130 fps, though I'm not sure if that's a good representation of dxvk performance given that apitrace runs the trace uncapped and the game stops at 125 fps.

Would be interesting to know what staging does different given that esync doesn't seem to be used by default.

Apitrace if anyone is interested:
https://www.dropbox.com/s/ahi8h9i43gvul9c/carma_md_garage.trace.xz?dl=0

I bisected the patches from staging and the winner is the nvapi patchset: nvapi-Stub_DLL.

Confirmed by applying the patchset to vanilla Wine. I have no idea why, or what happens given that the patches are mostly stubs. Maybe the game uses another render path when nvapi is detected?

That sounds plausible, but I tried spoofing an AMD card both with dxvk.conf and in config.cpp and I don't see any change in performance?

I can't even get the game to run. I'm not alone: https://www.protondb.com/app/505170

The splash screen appears, I get the stainless logo fullscreen then the game crashes. I can't report to ProtonDB as it says

Validation Errors!Answer To What Game: Could not find game with App ID 505170. This can happen if it is either inaccurate or if it has: been removed from the Steam store, not listed as a 'game', or not available in your country.

Has anyone managed to get this game working well?

https://gist.github.com/TRPB/82ed319170822742893ecd2a89e0bae3

Computer Information:
    Manufacturer:  Unknown
    Model:  Unknown
    Form Factor: Desktop
    No Touch Input Detected

Processor Information:
    CPU Vendor:  AuthenticAMD
    CPU Brand:  AMD Ryzen Threadripper 1950X 16-Core Processor 
    CPU Family:  0x17
    CPU Model:  0x1
    CPU Stepping:  0x1
    CPU Type:  0x0
    Speed:  3400 Mhz
    32 logical processors
    16 physical processors
    HyperThreading:  Supported
    FCMOV:  Supported
    SSE2:  Supported
    SSE3:  Supported
    SSSE3:  Supported
    SSE4a:  Supported
    SSE41:  Supported
    SSE42:  Supported
    AES:  Supported
    AVX:  Supported
    CMPXCHG16B:  Supported
    LAHF/SAHF:  Supported
    PrefetchW:  Unsupported

Operating System Version:
    Linux (64 bit)
    Kernel Name:  Linux
    Kernel Version:  5.0.13-arch1-1-ARCH
    X Server Vendor:  The X.Org Foundation
    X Server Release:  12004000
    X Window Manager:  KWin
    Steam Runtime Version:  <Runtime disabled>

Video Card:
    Driver:  X.Org AMD Radeon VII (VEGA20, DRM 3.27.0, 5.0.13-arch1-1-ARCH, LLVM 8.0.0)
    Driver Version:  4.5 (Compatibility Profile) Mesa 19.0.4
    OpenGL Version: 4.5
    Desktop Color Depth: 24 bits per pixel
    Monitor Refresh Rate: 59 Hz
    VendorID:  0x1002
    DeviceID:  0x66af
    Revision Not Detected
    Number of Monitors:  2
    Number of Logical Video Cards:  1
    Primary Display Resolution:  3840 x 2160
    Desktop Resolution: 7680 x 2160
    Primary Display Size: 20.51" x 11.54" (23.50" diag)
                                            52.1cm x 29.3cm (59.7cm diag)
    Primary VRAM: 16368 MB

Sound card:
    Audio device: Realtek ALC1220

Memory:
    RAM:  64341 Mb

Miscellaneous:
    UI Language:  English
    LANG:  en_GB.UTF-8
    Total Hard Disk Space Available:  468083 Mb
    Largest Free Hard Disk Block:  200206 Mb
    VR Headset: None detected

Recent Failure Reports:

Same problem. It shows the splash screen (with the desktop), goes fullscreen and shows the Stainless Games intro movie, then crashes to desktop.

Log file with PROTON_FORCE_LARGE_ADDRESS_AWARE=1:

steam-505170.log

I don't know if there's any relation but I also have a AMD Ryzen Threadripper 1950X 16-Core Processor.

This is still unplayable for me. Over 200 fps at start, down to ~10fps ingame and back to 200+ fps in menus.

Here is my proton log.
steam-505170.log

While that may contribute to it, I am seeing a different problem as I can't even past the first loading screen. Looking at ProtonDB it appears to be an AMD/nVidia thing. AMD gpus crash after the loading screen and nvidia GPUs can launch the game but with very poor performance.

So much for the kickstarter I donated to 7 years ago which promised linux support...

I don't have the time to help narrow this down, but I recently tried this game again, but using Proton-4.19-GE-1 and it works very very well, I could play at full speed (didn't get FPS sorry, but rest assured it was buttery smooth) at max settings on my RTX2060 powered laptop.

Edit: also to confirm and clarify, tried again with Steam provided Proton without changing game settings, and it reduces to a slideshow of what feels like 1 frame every 2-3 seconds.

Still doesn't work on AMD. It launches and crashes to the desktop.

Well, it was a Threadripper issue for me!

I had to lock the process to the first 4 'node 0 cpus' using this launcher option:
taskset -c 0-3 %command%

My NUMA config was loooking like this:

numactl -H
available: 1 nodes (0)
node 0 cpus: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31
node 0 size: 64269 MB
node 0 free: 49081 MB
node distances:
node   0 
  0:  10

I got about 40-70 fps with vanilla Proton but got a steady 124.9 fps using Proton 4.19-GE-1

Thanks for the suggestion. That gets me further, I can now get to the menu and start a game but it crashes to desktop about 80% into the loading screen when starting a level.

Here's the log file. I can't see anything in here that causes the crash other than the repeated

 2741.503:002b:002c:err:nvapi:NvAPI_D3D11_SetDepthBoundsTest Failed to get wined3d device handle!

The crash seems to be here:

 terminate called after throwing an instance of 'std::bad_alloc'
  what():  std::bad_alloc

but I'm not sure that gives us any real clues.
steam-505170.log

My NUMA settings are different, I have two nodes (this seems better in a lot of games):

numactl -H
available: 2 nodes (0-1)
node 0 cpus: 0 1 2 3 4 5 6 7 16 17 18 19 20 21 22 23
node 0 size: 32119 MB
node 0 free: 20765 MB
node 1 cpus: 8 9 10 11 12 13 14 15 24 25 26 27 28 29 30 31
node 1 size: 32218 MB
node 1 free: 24701 MB
node distances:
node   0   1 
  0:  10  16 
  1:  16  10 

And I also tried setting the launch option:

PROTON_LOG=1 numactl --membind=0 --cpunodebind=0  %command%

This works as much as taskset, it gets past the intro screen into the game's loading screen after selecting a level. It still crashes to desktop at that point though. I had hoped the membind option would fix it because of the bad_alloc error above.

EDIT: tried switching NUMA mode to only have one channel but I get the same result, crash to desktop right before entering the level.

Also tried graphics options on lowest and ultra to see if it's a graphic option that causes it. Both have the same result.

Been testing this lately and even with 1080TI and proton5.13 the performance is still pretty bad with BEST PERFORMANCE setting. FPS is between 20-60fps depending on situation.

Not sure what the fix would be.

Using proton-tkg-5.19 seemed to help performance a bit, but the game abruptly ctd after a minute of playing.

I suggest people try proton-ge and tkg builds and see if they get the same result or not, just to see if proton in general can be made to work better for this game.

@jarrard try the GE version. Whatever that build is doing seems to work fine.

@jarrard try the GE version. Whatever that build is doing seems to work fine.

You are correct, seems to run quite well now.

Can you get a gamepad to work? I have 360 controller but it does appear to work ingame. Maybe I need to be in big picture mode?

Nope Big Picture Mode does not enable controller (which works in steam). Seems this game can't detect xbox360 controller :(

System Information

• GPU: Nvidia Geforce RTX 2070
• Driver/LLVM version: Nvidia 470.57.02
• Kernel version: 5.4.0-80-generic
• Link to full system information report as Gist: https://gist.github.com/Johnnii360/e970bbf3e0930af31e21272c408966ba
• Proton version: 5.21-GE-1

I confirm:

• [x] that I haven't found an existing compatibility report for this game.x
• [x] that I have checked whether there are updates for my system available.

steam-505170.log

Symptoms

Steam shows the start dialogue, switches to game mode and game crashes. Only the latest Proton 6 versions are able to start the game properly but the performance in game is very awful.

I already tried Proton 5.9-GE-8-ST and 5.9-GE-6-ST as recommended in the protondb but crash either. Steam's 5.13-6 is also crashy.

Uhm... never mind... :) Proton 6.9-GE-2 work for me very well.

Still an issue on Steam Deck, 1-2 fps in-game or when viewing car models. max fps in main menu.

I needed to add PROTON_ENABLE_NVAPI=1 to command options to go from 8fps to 120fps.

My system is a hybrid laptop with RTX3070 gpu

From what it seems like at least on deck, you need to use Proton-6.5-GE-2 to get good performance. On desktop, checking protondb seems to suggest performance gets better if you use "PROTON_ENABLE_NVAPI=1" too. But at this point I have a feeling this game might need a workaround or something for the performance problems. Moreso since it seems like the game's been abandoned.

I've even seen footage of someone able to get this game into the triple digits fps wise with that specific proton ge version on deck.

I tested it out on my deck, using "PROTON_ENABLE_NVAPI=1" just outright crashes it when loading into a map. On the latest Experimental without using the command it shifts between a mixture of 30 and 15 fps in a race.

steam-505170.zip

Yeah this game has never worked right on newer proton versions. Like someone said you need 6.5 or earlier or you get the weird fps/stutter issues. No idea if this game actually makes use of Nvidia API or not. So it may just do nothing enabling that.

I was using experimental + PROTON_ENABLE_NVAPI. It was working very very well.

My nvidia driver version is 535.43.02

Retested on my OLED Deck, game has regressed on latest proton Experimental build. Loads up fine if I drop to 8.0-5, but framerate still drops down to mid 30s and below alot.

steam-505170.log

Guessing the constant spam of "warn: GetMonitorFormatBpp: Unknown format:" counting up endlessly might be a sign?

Game still has one more regression with latest proton Experimental build. Seems to get stuck on the splash screen now compared to before where it only took a second before it went away. I can fix it though by closing the splash screen window tab.

steam-505170.log

Performance is still bad in races too.

Update: "warn: GetMonitorFormatBpp: Unknown format:" still shows up in the logs counting up infinitely unless you close the splash screen.

Update: Issue does not occur when launching in desktop mode. I also tried opting in with proton Experimental bleeding edge and that seems to fix the issue in game mode.

Game boots up fine now on proton Experimental, but the performance is still pretty bad, curious if there is actually a way to fix up and work around the issue without using Proton GE

On Steam Deck, official Proton 10.0-4/Experimental boots, but framerate enters the single-digits even with all graphics set at their absolute lowest. Proton-GE 6.8-2, on the other hand, runs C:MD buttery-smooth at max settings, at the cost of crashing on every second level-load after the game boots. I hope someone out there is trying to fix this major discrepancy...

Using PROTON_ENABLE_NVAPI=1 %command% does not improve framerate one iota, either way.