Company of Heroes
Cool you got it working, but I get a black box for a setup screen and then it dies horribly.
Cool you got it working, but I get a black box for a setup screen and then it dies horribly.
This has been my experience when using Wine and Gallium Nine with the open source amdgpu stack. I will give Proton a try soon and report back.
This game is working flawlessly on Linux with the latest proton. I just played an automatch to completion. 4K 60 FPS on an RX 580 with opensource driver stack.
Ive put a related issue here for the coh mod's which are listed as their own game on the steam store...
https://github.com/ValveSoftware/Proton/issues/2035
Yesterday I realized there is a regression with Proton 4.2-2: it still starts and seems playable, but alt tabbing makes it crash now. This is not the case with Proton 3.16-8.
Hello @Corben78, please add PROTON_LOG=1 %command% to the game's launch options, reproduce the crash, and drag and drop the generated $HOME/steam-$APPID.log into the comment box.
Hello @kisak-valve, requested file attached.
I just realized, this only happens when I try to capture the CoH window in OBS (23.0.2) via Xcomposite. It does not happen when capturing the complete desktop with XSHM or when OBS is not running at all. When capturing with OBS/Xcomposite the games crashes and brings the Relic crash reporter up. When alt-tabbing out, the window seems to be minimized to a little square in the top left corner. When trying to tab in again, it crashes.
With Proton 3.16-8 Beta I can still capture the CoH window and alt-tab out and back in without issues.
This game has address space issues that get worse as the graphical settings are increased. DXVK makes them worse. It supports both Direct3D 11 (feature level 10) and Direct3D 9. PROTON_FORCE_LARGE_ADDRESS_AWARE=1 should help. In the absolute worst case, PROTON_USE_WINED3D=1 should be used because WineD3D is less suspectible to address space exhaustion than DXVK.
Under no circumstance should this game be whitelisted unless both PROTON_FORCE_LARGE_ADDRESS_AWARE=1 and PROTON_USE_WINED3D=1 are set by the app_compat_configs in 891390:
https://steamdb.info/app/891390/
Even then, it can still run into issues (although those reportedly also happen on Windows), so whitelisting it might be a bad idea.
By the way, could we get forcelgadd set for this game in 891390? That would be both for app id 228200 and app id 4560. The latter is the "legacy version", which is the same thing as far as graphics is concerned.
This was working for me a few months ago, now it looks like its no longer working.
Ive deleted my comptdata folder for 228200 and recorded a log file here:
steam-228200.log
Company Of Heroes Pur Virtual Function Call
Issue transferred from https://github.com/ValveSoftware/Proton/issues/4582.
@Ludo-code posted on 2021-01-31T10:08:14:
Compatibility Report
- Name of the game with compatibility issues: Company of Heroes
- Steam AppID of the game: 228200
System Information
- GPU: UHD Graphics 605
- Driver/LLVM version: i915
- Kernel version: 5.8.0-42-generic x86_64
- Link to full system information report as Gist: https://gist.github.com/Ludo-code/f052aeafc8859cebcb0c21ebf77e81fa/
- Proton version: tried with all version but the best result is with the proton experimental
I confirm:
- [x] that I haven't found an existing compatibility report for this game.
- [x] that I have checked whether there are updates for my system available.
Symptoms
Can't launch Vierville mission i have an error of pur virtual function call.
Reproduction
Launch Company of Heroes and try to start Vierville mission.
Thanks to have transferred me.
Lots of crashes with Proton 6.3-3
But I don't think you could do much for it in Proton guys.
I have verified, with a few save game I have been able to reproduce upon load, that to play this game well without the regular crashes, you have to downgrade the render engine from DirectX10 to DirectX9, for this you have to method;
Proton
PROTON_NO_D3D10=1
Game
Changing screendevice=DirectX10 rendering device to screendevice=DirectX9 rendering device in
/home/arno/.local/share/Steam/steamapps/compatdata/0/pfx/drive_c/users/steamuser/My Documents/My Games/Company of Heroes Relaunch/Local.ini
After that I could not get the game to crash anymore. I think the DirectX10 implementation in this game is experimental and Proton users are encouraged to downgrade to dx9.
ps:Don't use PROTON_NO_D3D11 which has no effect, the game doesn't support d3d11, people on ProtonDB are wrong on this parameter usage.
Works for me fine so long as I do as class101 suggested plus set all graphics to low and set screen resolution to 880x600. I presume this is something to do with a memory y size issue. Also my config .ini file was located at /home/$USER/.steam/debian-installation/steamapps/common/Company of Heroes Relaunch and came preloaded with the right settings. (purchased from steam store today and downloaded from there as well)
Encountered a visual bug while playing through the campaign on the lowest settings. It's not a crash per se but the lower left part of the St Fromonge map is all messed up with some of the polygons really low res and others totally black see https://imgur.com/a/1Fivj3k
I recently picked up a Deck and ran this game on it.
This is a regression. The default Proton version for this game in Steam makes it crash upon opening a mission, whereas it does work correctly with at least Proton 3.7 (though I've not tested other more recent versions, I picked the oldest as I knew that this game runs successfully in Wine).
Current Proton 8.0-4 and lower. Tested until version 6.
Still has the crash issue when loading a scenario. It seems memory related as a game with 2 Player and two Computers worked 50% of the time on QHD resolution with all settings on high/ultra. When playing with the same settings a 3v3 (with 3 humans and 3 computers) it crashes when loading a scenario 100% of the time on my side.
Adding the workarounds from above helps/prevents the issue.
I am seemingly unable to launch the game at all, I have tried PROTON_NO_D3D10=1 class101 mentions, and the PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 mentioned on ProtonDB. I also have added -nomovies -novsync after %command% to no effect.
However I have no Local.ini config (not any Company of heroes Relaunch dir) under ~/.local/share or ~/.steam/. Perhaps that gets written when the game is actually launched?
Proton 7 has an associated error dialog:
There are exceptions in the steam-228200.log files (eg EXCEPTION_ACCESS_VIOLATION) but I am not sure which process is originating those.
There are also errors about missing DLLs and vulkan failure:
$ grep err /home/robert/steam-228200-706.log
11309.896:0130:0134:err:module:import_dll Library d3d10.dll (which is needed by L"Z:\\home\\robert\\mounts\\980data\\games\\steam\\steamapps\\common\\Company of Heroes Relaunch\\spDx10.dll") not found
11309.901:0130:0134:err:module:import_dll Library dxgi.dll (which is needed by L"Z:\\home\\robert\\mounts\\980data\\games\\steam\\steamapps\\common\\Company of Heroes Relaunch\\spDx10.dll") not found
11309.977:0130:0134:err:vulkan:wine_vk_instance_load_physical_devices Failed to enumerate physical devices, res=-3
11309.977:0130:0134:err:vulkan:__wine_create_vk_instance_with_callback Failed to load physical devices, res=-3
terminate called after throwing an instance of 'dxvk::DxvkError'
Can't attach process 0130: error 5
Running vulkaninfo shows information about my card (GTX 970).
Setting VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/nvidia_icd.json (per a comment in this 2022 issue) removes the vulkan-related Failed complaints in in the proton log but no change in behaviour otherwise.
Logs:
- Proton 6.3-8: steam-228200.log
- Proton 7.0-6: steam-228200-706.log ("pure virtual function call")
- Proton 9.0-4: steam-228200-904.log (caused a music skip when trying to launch, which is the only other indication I have that the launch process is having any effect)
- Proton Current (no compatibility set: hotfix-20250130-ffrebirth): steam-228200-hotfix.log
I'm not terribly familiar with troubleshooting Proton, so I would appreciate advice. Cheers! :)
Edit: Setting compatibility to Proton 3.7-8 seems to let the game launch. I was able to complete a skirmish vs CPU match, but performance was poor (from observation: max ~12 FPS, usually single digit, sometimes dropping to 1-2 FPS)
Company of Heroes (relaunched) - Pure Virtual Call Error in Linux mint Steam
Issue transferred from https://github.com/ValveSoftware/Proton/issues/9878.
@BambiTheNewbie posted on 2026-06-16T11:41:11:
Compatibility Report
- Name of the game with compatibility issues: Company of heroes error Pure Virtual Function Call
- Steam AppID of the game: https://store.steampowered.com/app/228200/Company_of_Heroes/
System Information
System:
Kernel: 6.17.0-35-generic arch: x86_64 bits: 64 compiler: gcc v: 13.3.0 clocksource: tsc
Desktop: Xfce v: 4.18.1 tk: Gtk v: 3.24.41 wm: xfwm4 v: 4.18.0 with: xfce4-panel
tools: light-locker vt: 7 dm: LightDM v: 1.30.0 Distro: Linux Mint 22.3 Zena
base: Ubuntu 24.04 noble
CPU:
Info: dual core model: Intel Core i5-4200U bits: 64 type: MT MCP smt: enabled arch: Haswell
rev: 1 cache: L1: 128 KiB L2: 512 KiB L3: 3 MiB
Speed (MHz): avg: 1721 high: 1796 min/max: 800/2600 cores: 1: 1696 2: 1696 3: 1696 4: 1796
bogomips: 18358
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
Device-1: Intel Haswell-ULT Integrated Graphics vendor: Lenovo ThinkPad X240 driver: i915
v: kernel arch: Gen-7.5 ports: active: eDP-1 empty: DP-1, DP-2, HDMI-A-1, HDMI-A-2
bus-ID: 00:02.0 chip-ID: 8086:0a16 class-ID: 0300
- Proton version: 6.3-8
I confirm:
- [ YES] that I haven't found an existing compatibility report for this game.
- [ YES] that I have checked whether there are updates for my system available.
Symptoms
I tried to run the game but it only starts/launch on Proton 6.3-8, No other proton version can launch it. I am Vanilla only so i dont have any mods installed. That is the first problem, only one proton version can Launch the game ( we are only at launch no playing yet)
The next problem is that when i start playing a campaign/skirmish/multiplayer ( dont matter same result ) the game crashes it says " Runtime Error! R66025 - Pure Virtual Function Call.
Tried changing the the shaders settings from maximum (default) to high, the result is the game's terrain is black and grey moving constantly like a television without signal thats the terrain.
Tried changing to Low Shader setting, the terrain becomes black hard to differenciate from the obstacles.
please help, i tried changeing proton versions but non really worked. i am on linux mint xfce right now but before i was in Cinnamon linux mint and same problem. so i cant play the game.
Reproduction
Hello @BambiTheNewbie, https://gitlab.freedesktop.org/mesa/mesa/-/work_items/7827 is relevant to your system. The Vulkan driver for your hardware generation doesn't advertise support for Vulkan 1.3. DXVK bundled with newer Proton versions is failing out from a lack of hardware features.
hello kisak, does that mean that i will never be able to play Company of heroes in this device?
In theory, you could try telling mesa to lie about what Vulkan version the hardware supports (https://docs.mesa3d.org/envvars.html#envvar-MESA_VK_VERSION_OVERRIDE) and you might get lucky, but generally your hardware isn't supportable by Proton going forward. Alternatively, you could tell Proton to use wine's DirectX to OpenGL render path with PROTON_USE_WINED3D=1, but that is also not considered supported and is known to come with a significant performance penalty.
Thanks @kisak-valve im glad you still helped me despite of my old device being no longer supported. :)
Proton versions
proton 6.3-8x2 2026-06proton 3.7-8x1 2025-01proton 7.0-6x1 2025-01proton 9.0-4x1 2025-01proton 8.0-4x1 2024-01proton 3.7x1 2022-10proton 6.3-3x1 2021-05proton experimentalx1 2021-01proton 3.16-8x2 2019-04proton 4.2-2x1 2019-04
Launch options
MESA_VK_VERSION_OVERRIDEx1 2026-06PROTON_USE_WINED3D=1`,x1 2026-06PROTON_NO_D3D10=1`x2 2025-01PROTON_NO_ESYNC=1x1 2025-01PROTON_NO_FSYNC=1`x1 2025-01PROTON_NO_D3D11x1 2021-05PROTON_FORCE_LARGE_ADDRESS_AWARE=1`x1 2019-08PROTON_USE_WINED3D=1`x1 2019-08PROTON_LOG=1x1 2019-04
Upstream links
- ValveSoftware/Proton/issues/9878x1 2026-06
- ValveSoftware/Proton/issues/4582x1 2021-01
- ValveSoftware/Proton/issues/2035x1 2018-11
DLLs
d3d10.dllx1 2025-01dxgi.dllx1 2025-01spdx10.dllx1 2025-01
Whitelist Request
System Information
I confirm:
Playbutton in the Steam client is sufficient.are necessary to run the game.
Issues
remaining issues