search

ValveSoftware / Proton

Compatibility tool for Steam Play based on Wine and additional components
Other
24.6k stars 1.07k forks source link

Company of Heroes (228200) #1381

Open jaubin opened 6 years ago

jaubin commented 6 years ago

Whitelist Request

System Information

I confirm:

Issues

hydranmenace commented 6 years ago

Cool you got it working, but I get a black box for a setup screen and then it dies horribly.

ryan-ronnander commented 6 years ago

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.

ryan-ronnander commented 6 years ago

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.

Gibbz commented 6 years ago

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

Corben78 commented 5 years ago

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.

kisak-valve commented 5 years ago

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.

Corben78 commented 5 years ago

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.

steam-228200.log

ryao commented 5 years ago

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.

Gibbz commented 4 years ago

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

kisak-valve commented 3 years ago

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

System Information

I confirm:

steam-228200.log

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.

Ludo-code commented 3 years ago

Thanks to have transferred me.

class101 commented 3 years ago

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.

Tasty213 commented 3 years ago

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)

Tasty213 commented 3 years ago

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

TZer0 commented 2 years ago

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).

pseiler commented 10 months ago

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.