ValveSoftware
DCS World Steam Edition (223750)
Compatibility Report
- Name of the game with compatibility issues: Does not launch
- Steam AppID of the game: 223750
System Information
- GPU: GTX 1070
- Driver/LLVM version: Nvidia 396.54
- Kernel version: 4.15.0-36
- Link to full system information report as Gist:
- Proton version: 3.7-7
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
While using the most current, stable (non-beta) client (Proton 3.7-7), the game does not launch. The attached report shows errors.
Reproduction
Install DCS World Steam Edition, launch the game and acknowledge play via Steamplay.
I got it to start (Proton 4.2-2, Nvidia 418.56) and authenticate by installing corefonts and vcrun2015 via protontricks. It came up in windowed mode, then I set it to fullscreen and all graphics options to the highest I could. So far so good, then I started a mission with A10-C. It loaded ok, but once it reached 100% it didn't continue. I had to SIGKILL the whole thing. It didn't start again after that so I removed the Config directory from the compatdata prefix. More humble in iteration two, I left everything as is (windowed, no graphics change), now the mission loaded fine, but then the whole process crashed when it tried to switch to in-flight.
@mlassnig I followed your instructions and got it running with proton 4.2-4. Everything is purple/pink (see attached screenshot) and I'm currently messing with the settings to see if I can fix it.
My System:
- Ubuntu 19.04, kernel 5.0.0-15
- GTX-1070, driver 418.56
What I did to get it running:
- installed corefonts and vcrun2015 using winetricks. I used these instructions: https://github.com/redmcg/wine/wiki. DCS-World steam ID is 223750
- ensured I have the latest release of proton enabled in Steam 4.2-4
I got rid of the pink hue by turning off MSSA but no combination of settings seems to allow this to render correctly. I upgraded to nvidia-drivers-430 with the same results. See screenshots:
Tried it with proton 4.2-7 mesa/radv and DXVK. Had to manually install corefonts using protontricks.
That did work, even in fullscreen and with MSAA activated. Also the activation and usage of DLC does work. Performance was ok (35-40 fps on high profile with my RX Vega 64), but a bit worse than on Windows.
Also tried it with WINED3D, but there I get the same visual glitches as @h54.
Using protontricks
protontricks 223750 vcrun2017 corefonts xact d3dcompiler_43
seemed to fix nearly all the issues I was having. Everything renders beautifully at 60fps with very high settings.
The only things I'm unsure about:
- is the mouse supposed to control the camera inside/outside the aircraft? If so, it doesn't work.
- Pressing
for the map freezes the game. I have to use ALT+F4 and restart Steam but the game restarts just fine.
* is the mouse supposed to control the camera inside/outside the aircraft? If so, it doesn't work.
Inside the aircraft, no. The aircraft usually have a clickable cockpit, so moving the mouse moves a cursor you can use to flip switches etc. Not sure about outside of the cockpit from the top of my head.
@Preisschild not as of yet. LinuxTrack recognizes the device and is able to create a working profile for X-Plane but I'm not sure where to go for DCS.
@h54 What is your joystick setup? Do you have one, if so how well does it work?
@MrMinimal currently using a Gladiator Mk II and it worked out of the box with no issues. I just had to map buttons to where I wanted them. https://store.x-plane.org/Gladiator-MK-II_p_595.html
Anyone have any luck getting the F10 map working? The game freezes (alt + F4 fixes that) and restarting Steam fixes it. To restart Steam, I have to kill 9 a bunch of steam processes.
Anyone have any luck getting the F10 map working? The game freezes (alt + F4 fixes that) and restarting Steam fixes it. To restart Steam, I have to kill 9 a bunch of steam processes.
Actually that works fine for me, no issues. Without applying any additional tricks, just what is mentioned above already.
btw, in my test yesterday I found that the performance is now significantly better and around the same as on Windows 7. As I mentioned before, I had around 35-40 fps on high profile (just did a short test flight with the T51D and the Huey). Now I get 60-80 fps on high profile in the T51D. Don't know what caused the improvement, might be a new kernel version, new mesa version, new wine/proton, DXVK or something else, but it's definitely better.
It still crashes on launch for me :/
Only thing that caught my eye during protontricks installation was a lot of lines like this:
Executing cabextract -q -d /media/data/Spiele/Steam/steamapps/compatdata/223750/pfx/dosdevices/c:/windows/syswow64 -L -F xapofx*.dll /media/data/Spiele/Steam/steamapps/compatdata/223750/pfx/dosdevices/c:/windows/temp/_xact/oct2006_xact_x86.cab /media/data/Spiele/Steam/steamapps/compatdata/223750/pfx/dosdevices/c:/windows/temp/_xact/oct2006_xact_x86.cab: WARNING; possible 5960 extra bytes at end of file.
The Proton-Log states a pagefault, but nothing i can read anything out of. It doesn't create a subfolder "dcs" in "steamapps/compatdata/223750/pfx/dosdevices/c:/users/steamuser/Saved Games/" where the gamelog normaly should be iirc.
Happens both with ACO and RADV_PERFTEST=llvm
Maybe someone has any suggestion?
Maybe something went wrong during the installation of the packages? Did you try with a clean wine prefix?
i just quit steam, deleted /steamapps/compatdata/223750/ and /steamapps/common/Proton 4.11/, restarted steam and verified proton 4.11 to download it again, started DCS (crash), ran "protontricks 223750 vcrun2013 corefonts xact d3dcompiler_43" and still got a crash :/ Is there any way to make proton "more clean"?
No I think that'll do. I don't think it's proton then. Maybe drivers or some part of the system or maybe a bad download for DCS or something else.
@Termuellinator
Try adding dxvk
protontricks 223750 dxvk
@berniyh
I started with a clean wine prefix and can't get the F10 map to work. The game still crashes for me. Can you show me the output of the following?
protontricks 223750 list-installed
@h54 didn't help either. Seems to still be the same error if i read the log correctly:
1993.470:0033:0034:trace:seh:call_stack_handlers found wine frame 0x22fdf0 rsp 22ffe0 handler 0x7b4c0fe0
1993.470:0033:0034:trace:seh:call_teb_handler calling TEB handler 0x7b4c0fe0 (rec=0x22f7d0, frame=0x22fdf0 context=0x22eca0, dispatch=0x22ea40)
wine: Unhandled page fault on read access to 0x00000004 at address 0x1407024fa (thread 0034), starting debugger...
1993.470:0033:0034:trace:seh:start_debugger Starting debugger "winedbg --auto 51 232"
ERROR: ld.so: object '/home/termy/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
i disabled the steam overlay (because of the gameoverlayrenderer.se error), but still the same
Have you checked out what other AMD users did on ProtonDB? https://www.protondb.com/app/223750
@h54 didn't help either. Seems to still be the same error if i read the log correctly:
1993.470:0033:0034:trace:seh:call_stack_handlers found wine frame 0x22fdf0 rsp 22ffe0 handler 0x7b4c0fe0 1993.470:0033:0034:trace:seh:call_teb_handler calling TEB handler 0x7b4c0fe0 (rec=0x22f7d0, frame=0x22fdf0 context=0x22eca0, dispatch=0x22ea40) wine: Unhandled page fault on read access to 0x00000004 at address 0x1407024fa (thread 0034), starting debugger... 1993.470:0033:0034:trace:seh:start_debugger Starting debugger "winedbg --auto 51 232" ERROR: ld.so: object '/home/termy/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.i disabled the steam overlay (because of the gameoverlayrenderer.se error), but still the same
@Termuellinator , have you checked out what other AMD users did on ProtonDB? https://www.protondb.com/app/223750
i disabled the steam overlay (because of the gameoverlayrenderer.se error), but still the same
That error you can ignore, it's just normal on 64bit systems.
Have you checked out what other AMD users did on ProtonDB?
I was the first here to report success with this game and I'm running an AMD CPU (FX 4350) and GPU (RX Vega). ;)
Also on Mesa and RADV.
I upgraded to Ubuntu 19.10 with the packaged Nvidia 435 drivers and was getting frequent freezes. I had to start over with a clean Steam prefix every time afterwards. Downgrading to the 430 drivers (graphics drivers PPA) fixed it. Anyone else experience this? Also, the F10 map still crashes the game.
The game runs pretty much flawlessly on 4.11.7 for me. The one annoying issue is the F10 map crash which I don't seem to be alone in experiencing. What makes it even worse is that I have to remove and re-create the whole prefix after it happens.
@berniyh You said the F10 map works fine for you. Would you mind posting more info about your setup?
Update: I found a very simple solution to the problem. The map isn't the issue, it's the F10 key itself. Try pressing it in the main menu and it will still crash the game. So, the solution is to just rebind the key to anything else.
Also, I ran a diff of a working and non-working prefix, and it looks like the crash causes two files to appear:
pfx/drive_c/windows/system32/wbemprox.dll
pfx/drive_c/windows/system32/lsteamclient.dll
The latter is the one that is causing the game to not start again, so removing it saves you from having to reset your whole prefix after a crash.
@TheZoq2
Both of your solutions work for me, amazing work!
Previously, I was backing up the entire prefix dir just in case but removing that file is pretty simple.
Glad to hear the fix is reproducible. At least something about this bug makes sense :P It would be really interesting to know what causes the issue in the first place. I've never heard of a single key permanently crashing a game :D
Proton Version 4.11 - DCS World, GTR - FIA Racing Game do not launch
Issue transferred from https://github.com/ValveSoftware/Proton/issues/3282. @Jeducious posted on 2019-12-03T07:42:09:
Hi,
So I have followed the instructions here to install the necessary drivers. I have a attached a dump of the output of steam after trying to launch DCS World. There is a crash with a stack trace near the end of the game, see DSC WORLD STEAM stdout/stderr.txt
This happens also for GTR. Though I can try to start the game, it never loads and I get similar output from GTR also.
My hardware is nothing out of the ordinary, software is Ubuntu 19.04. For the exact setup I have, see steam_system_info.txt
Also in the system info file I see a lot of errors related to steam trying to list the items in the "graphics-details" section of "architectures".
Any help would be appreciated, but I am not holding my breath there, this information is for the devs to hopefully make things work for average linux users like me. Gaming on linux would be nice, but so far I feel I have spent so much time trying to get this to work that its a bit of a turn off, and I am going to try and find a way to get a windows box up and running instead since I know I can run all these games on win 10 platform.
@Jeducious
For DCS, did you follow the instructions at proton-db? Without it the game probaly won't run.
I also notice you're using a fairly old AMD GPU (from 2013 if wikipedia is to be trusted). Unfortunately, I think AMDs linux drivers weren't great back then, and I'm not sure if that has been fixed, so that might cause your issues.