DCS World Steam Edition (223750)

[h54]

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.

steam-223750.log

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.

[MrMinimal]

Same here. System information: gist

[mlassnig]

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.

[h54]

@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

[h54]

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:

[berniyh]

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.

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

[berniyh]

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

[h54]

It runs really nicely!

[Preisschild]

@h54 did you get TrackIR and HOTAS working?

[h54]

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

[MrMinimal]

@h54 What is your joystick setup? Do you have one, if so how well does it work?

[h54]

@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

[h54]

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.

[Preisschild]

@h54 reopen the issue please

[berniyh]

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.

[Termuellinator]

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.

steam-223750.log

Happens both with ACO and RADV_PERFTEST=llvm

Maybe someone has any suggestion?

[berniyh]

Maybe something went wrong during the installation of the packages? Did you try with a clean wine prefix?

[Termuellinator]

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"?

[berniyh]

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.

[h54]

@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

[Termuellinator]

@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

[h54]

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

[berniyh]

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.

[h54]

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.

[TheZoq2]

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?

[TheZoq2]

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.

[h54]

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

[TheZoq2]

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

[kisak-valve]

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.

[TheZoq2]

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

[Jeducious]

OK, I can see some instructions there to install protontricks and winetricks. But the instructions just tell me I have to install them, not how to.

So, question, why am I having to install these extra packages in the first place? How come the steam client doesn't install all the necessary components to run the games?

[Jeducious]

Also can't install winetricks, apparently this is needed to complete the protontricks command that gets DCS working so until I can install winetricks I think I am boned?

Here's the output of me trying to do the protontricks command and then trying to install winetricks....

james@james-xubuntu:~/.local/pipx/venvs/protontricks/bin$ ./protontricks 223750 vcrun2017 corefonts xact protontricks (ERROR): 'winetricks' executable could not be found automatically. Winetricks isn't installed, please install winetricks in order to use this script! james@james-xubuntu:~/.local/pipx/venvs/protontricks/bin$ pipx install winetricks Cache entry deserialization failed, entry ignored ERROR: Could not find a version that satisfies the requirement winetricks (from versions: none) ERROR: No matching distribution found for winetricks '/home/james/.local/pipx/venvs/winetricks/bin/python -m pip install winetricks -q' failed james@james-xubuntu:~/.local/pipx/venvs/protontricks/bin$

[TheZoq2]

So, question, why am I having to install these extra packages in the first place? How come the steam client doesn't install all the necessary components to run the games?

DCS isn't officially supported by steam/proton

pipx install winetricks

I don't believe winetricks can be installed using pip

See https://github.com/Winetricks/winetricks for installation instructions

[Jeducious]

Yeah, turns out winetricks is installed using apt, its a package. So can someone explain what is the deal with steam's support of linux then? It appears to the casual user (me at least) that there are various ways to support their titles on linux, either using steam's own linux client/runtime/thingy, or proton.

Each of these options appears in steam as if it were some kind of app. They even have launch buttons. All of them fail to launch with an error btw, yes, I tried to launch them :( guessing you're not supposed to launch them?

[TheZoq2]

So can someone explain what is the deal with steam's support of linux then? It appears to the casual user (me at least) that there are various ways to support their titles on linux, either using steam's own linux client/runtime/thingy, or proton.

There are essentially three tiers of linux support:

• Games with native linux versions
• Games without native linux versions but that are officially supported by proton
  • (more info here https://steamcommunity.com/games/221410/announcements/detail/1696055855739350561)
• Games without native linux versions and without official support, like DCS

Games in the last category can work, but there are no guarantees. They often require tweaking, and in cases where there are issues in proton, you can report them here. A community-maintained list of games is https://www.protondb.com/ where players can report game status and workarounds.

[berniyh]

Also can't install winetricks, apparently this is needed to complete the protontricks command that gets DCS working so until I can install winetricks I think I am boned?

Yes. The thing is that proton is in a test phase and officially only supports selected games. However, many other games do work even without official support. DCS is not one of them as some part of setting up the wine config. This is what you fix using winetricks. Once the proper procedure was established and tested, there is a chance that it will be included in a future proton release (meaning that it's done automatically or is obsolete) and the support status might change to being officially supported. Unfortunately the list of games is very long so it'll take them a long time to get there.

Thankfully winetricks (or even better protontricks) makes it rather easy to apply the appropriate fixes, so … could be worse. ;)

btw, protontricks is just a frontend to winetricks making it easier to apply corresponding fixes to a specific game.

Yeah, turns out winetricks is installed using apt, its a package. So can someone explain what is the deal with steam's support of linux then? It appears to the casual user (me at least) that there are various ways to support their titles on linux, either using steam's own linux client/runtime/thingy, or proton.

Just ignore the steam runtime thing for the moment.

[TheZoq2]

On an unrelated note, do smoke particle effects behave weirdly for anyone else. For me, it kind of looks like they don't move, they just animate.

This is most obvious with chimneys where there are just three white dots spaced out evenly above the chimney. It also makes flares and missile trails look really strange.

As far as I can tell, not all particle effects are broken though. Explosions, and the black smoke from engines look like they work fine

[h54]

@TheZoq2 I experience the same thing. Contrails, missile exhaust, chimney smoke, and any other white smoke has gaps and doesn't seem to be animated. Black exhaust smoke while using MIL power and explosion and fire smoke seems to be fine.

[TheZoq2]

As of the 2.5.6 open beta patch, I can no longer log into the game. Both standalone and steam crash on pressing login, though the steam version works fine if canceling the login.

The relevant parts of the game log seem to be

2020-02-29 09:06:43.698 INFO    EDCORE: # -------------- 20200229-090644 --------------
2020-02-29 09:06:43.698 INFO    EDCORE: DCS/2.5.6.43931 (x86_64; Windows NT 5.2.3790)
2020-02-29 09:06:43.698 INFO    EDCORE: C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\DCS.exe
2020-02-29 09:06:43.698 INFO    EDCORE: # C0000005 ACCESS_VIOLATION at 40831C13 00:00000000
2020-02-29 09:06:43.698 INFO    EDCORE: SymInit: Symbol-SearchPath: '.;C:\Program Files\Eagle Dynamics\DCS World OpenBeta;C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin;C:\windows;C:\windows\system32;SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols;', symOptions: 530, UserName: 'frans'
2020-02-29 09:06:43.698 INFO    EDCORE: OS-Version: 5.2.3790 (Service Pack 2) 0x0-0x1
2020-02-29 09:06:44.054 INFO    EDCORE: 0x0000000000831C13 (dcs): (function-name not available) + 0x0
2020-02-29 09:06:44.054 INFO    EDCORE: 0x00000000008315CE (dcs): (function-name not available) + 0x0
2020-02-29 09:06:44.055 INFO    EDCORE: 0x000000000167F196 (dcs): (function-name not available) + 0x0
2020-02-29 09:06:44.055 INFO    EDCORE: 0x00000000008513DF (dcs): (function-name not available) + 0x0
2020-02-29 09:06:44.056 INFO    EDCORE: 0x000000000085325C (dcs): (function-name not available) + 0x0
2020-02-29 09:06:44.056 INFO    EDCORE: 0x00000000008545E0 (dcs): (function-name not available) + 0x0
2020-02-29 09:06:44.056 INFO    EDCORE: 0x000000000084F88F (dcs): (function-name not available) + 0x0
2020-02-29 09:06:44.057 INFO    EDCORE: 0x000000000167E92B (dcs): (function-name not available) + 0x0
2020-02-29 09:06:44.057 INFO    EDCORE: 0x00000000006DFACF (dcs): (function-name not available) + 0x0

I have not seen any reports of windows users experiencing this, so I'm suspecting it's a wine issue. Has anyone else experienced it?

[Ape]

@TheZoq2 I have the same issue with the latest open beta versions. 2.5.5 and the first 2.5.6 patch are working, but any later 2.5.6 patch (including the current one) crash with that same log output.

[paju1986]

I have the same issues with 2.5.6, i cant get it to work on Proton, please fix!

[h54]

It seems there was an update today (03/19/2020) and I can no longer launch the game with any version of Proton. Anyone else having issues? I'd pause the update if possible.

[TheZoq2]

Looks like I have similar issues.

For reference, this is the terminal output after the crash:

wine: Unhandled page fault on read access to 000000000000000C at address 000000014030B99A (thread 0035), starting debugger...
ERROR: ld.so: object '/home/frans/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
>>> Adding process 9195 for game ID 223750
Process of pid=0034 has terminated
No process loaded, cannot execute 'echo Modules:'
Cannot get info on module while no process is loaded
No process loaded, cannot execute 'echo Threads:'
process  tid      prio (all id:s are in hex)
00000008 steam.exe
    0000002a    0
    00000009    0
0000000c services.exe
    00000026    0
    00000020    0
    00000018    0
    00000013    0
    00000012    0
    00000011    0
    0000000e    0
    0000000d    0
0000000f plugplay.exe
    00000015    0
    00000014    0
    00000010    0
00000016 winedevice.exe
    0000001d    0
    0000001c    0
    0000001b    0
    0000001a    0
    00000019    0
    00000017    0
0000001e winedevice.exe
    00000023    0
    00000022    0
    00000021    0
    0000001f    0
00000024 winedevice.exe
    00000029    0
    00000028    0
    00000027    0
    00000025    0
0000002b explorer.exe
    00000031    0
    00000030    0
    0000002d    0
    0000002c    0
pid 9148 != 9147, skipping destruction (fork without exec?)

[Ape]

The latest patch (2.5.6.45317) seems to have fixed the login problems that occurred on the previous versions (see the comments above). So that's at least good news.

However, now the game crashes on a different stage (after login) with this message:

2020-03-20 14:40:45.903 INFO    EDCORE: DCS/2.5.6.45317 (x86_64; Windows NT 6.0.6002)
2020-03-20 14:40:45.903 INFO    EDCORE: C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\webrtc_plugin.dll
2020-03-20 14:40:45.903 INFO    EDCORE: # C0000005 ACCESS_VIOLATION at 2AA02CDD 02:00002CDD
2020-03-20 14:40:46.218 INFO    EDCORE: SymInit: Symbol-SearchPath: '.;C:\Program Files\Eagle Dynamics\DCS World OpenBeta;C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin;C:\windows;C:\windows\system32;SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols;', symOptions: 530, UserName: 'ape'
2020-03-20 14:40:46.218 INFO    EDCORE: OS-Version: 6.0.6002 (Service Pack 2) 0x0-0x1
2020-03-20 14:40:47.780 INFO    EDCORE: 0x0000000000002CDD (webrtc_plugin): (function-name not available) + 0x0
2020-03-20 14:40:47.781 INFO    EDCORE: 0x00000000002888E9 (webrtc_plugin): (function-name not available) + 0x0
2020-03-20 14:40:47.781 INFO    EDCORE: 0x00000000001A7070 (webrtc_plugin): (function-name not available) + 0x0

This seems to be related to webrtc_plugin.dll. Maybe there is something we can do to workaround the crash..

EDIT: This is probably an issue with the voice chat feature. WebRTC is probably used for that and the last log line from DCS is

SECURITYCONTROL: Loaded ./CoreMods/services/VoiceChat/bin/VoiceChat.dll

[TheZoq2]

Disregard my last comment, I forgot to run protontricks after creating a new prefix. I am getting the same error as @Ape now, I wonder if there is something we can do to skip loading WebRTC.

Also, are you sure the login issues are fixed, mine crashes during the splash screen, before login. Or are you running the non-steam version which shows login early?

[TheZoq2]

Looks like disabling voice chat in the options file does not solve the problem either :(

[Ape]

@TheZoq2 In the previous version, both Steam and standalone versions crashed with the same stack trace on login. In the standalone version the login happens before the splash screen and on Steam it happens ingame. In this new version I cannot test login on Steam version, but it has definitely been fixed on the standalone version. And since the login crash was previously identical I am expecting that the problem has been fixed on the Steam version, too.

[TheZoq2]

Yea, that was my experience too, so that's good news. I'm going to try and see if I can get it to stop loading that DLL somehow. Unfortunately, disabling voice chat in the options file doesn't work

[TheZoq2]

Some good news and some bad news:

Bad news: After getting the game running, I get another crash just after loading seems to be done:

020-03-20 17:56:33.183 INFO    UIBASERENDERER: Cannot load font [C:\windows\Fonts\Arial.ttf]!
2020-03-20 17:56:33.183 INFO    EDCORE: try to write dump information
2020-03-20 17:56:33.183 INFO    EDCORE: # -------------- 20200320-175634 --------------
2020-03-20 17:56:33.183 INFO    EDCORE: DCS/2.5.6.45317 (x86_64; Windows NT 5.2.3790)
2020-03-20 17:56:33.183 INFO    EDCORE: Z:\home\frans\.local\share\Steam\steamapps\common\DCSWorld\bin\DCS.exe
2020-03-20 17:56:33.183 INFO    EDCORE: # C0000005 ACCESS_VIOLATION at 407C9C1F 00:00000000
2020-03-20 17:56:34.053 INFO    EDCORE: SymInit: Symbol-SearchPath: '.;Z:\home\frans\.local\share\Steam\steamapps\common\DCSWorld;Z:\home\frans\.local\share\Steam\steamapps\common\DCSWorld\bin;C:\windows;C:\windows\system32;SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols;', symOptions: 530, UserName: 'steamuser'
2020-03-20 17:56:34.053 INFO    EDCORE: OS-Version: 5.2.3790 (Service Pack 2) 0x0-0x1
2020-03-20 17:56:36.100 INFO    EDCORE: 0x00000000007C9C1F (dcs): (function-name not available) + 0x0
2020-03-20 17:56:36.100 INFO    EDCORE: 0x00000000007BCD4D (dcs): (function-name not available) + 0x0
2020-03-20 17:56:37.132 INFO    EDCORE: Minidump created.

Good news: The game seems to start and get to the main menu by commenting out a bunch of stuff in the lua files. Stupidly enough, I didn't write this down, but this is what I think I did:

• Comment out the 'VoiceChat' line in coreMods/entry.lua. This causes more issues since the module doesn't exist
• To fix those: comment out all of MissionEditor/modules/mul_voiceChat.lua apart from the following line:

  
  local base = _G

module('mul_voicechat')

Finally, fix the last error by changing `getVoiceChatDevices` in `MissionEditor/modules/Options/optionsDb.lua` to

local function getVoiceChatDevices(dev_type) -- local devices = mod_sound.getVoiceChatDevices(devtype) local result = {} -- if not devices then -- table.insert(result,Name(('Undefined')):Value("")) -- else -- for k,v in ipairs(devices) do -- table.insert(result,Name(v[2]):Value(v[1])) -- end -- end

return result

end

[TheZoq2]

Success!

Looks like the clue was in the first line of the last log file I posted. Something was wrong with my arial font which is symlinked to something in proton. Replacing it with the arial font from the standalone version works :tada: If anyone wants a copy of that file, let me know and I'll upload it here

Edit: the login button in the steam version does nothing. But standalone seems to work. I'm currently downloading all my modules to it