Repository navigation
IL-2 Sturmovik: Cliffs of Dover Blitz Edition (754530) #5007
Description
Compatibility Report
- Name of the game with compatibility issues: IL-2 Sturmovik: Cliffs of Dover Blitz Edition
- Steam AppID of the game: 754530
System Information
- GPU: NVIDIA GeForce RTX 2060 SUPER
- Driver/LLVM version: NVidia 470.57.02
- Kernel version: 5.8.0-63
- Link to full system information report as Gist: Here
- Proton version: 6.3.5
I confirm:
- that I haven't found an existing compatibility report for this game.
- that I have checked whether there are updates for my system available.
Symptoms
The game fails to launch at all.
Looking at the proton log, it complains about DLLs that it can't open. (Log 1). For each of these I created symlinks in the same directory as the main executable, which did seen to resolve these errors. After doing this this, there are null reference exceptions in the log and lines like this (Log 2):
EXCEPTION handling: System.InvalidProgramException: Invalid IL code in <Module>:?A0xe813d47e.??__F?A0xe813d47e@_Fac_tidy_reg@std@@YMXXZ (): IL_0024: calli 0x11000144
Which are a bit beyond my ken.
Reproduction
Hit play; game listed as running for a few seconds, then exits.
Activity
kisak-valve commentedon Jul 25, 2021
Hello @coljac, your logs indicate that you tested the game with Proton 5.0-10, and that this game uses Windows Presentation Framework. Wine-mono 4.9.4 in Proton 5.0-10 is too old to support that.
You may have a better chance of success with the game and Proton 5.13 or newer.
coljac commentedon Jul 25, 2021
@kisak-valve You're correct, I thought I was using 6.3. Here's the log for proton 6.3: In this case, I get a splash screen briefly, then it quits. This may be a relevant bit from the (attached) log:
log_v6.log
madewokherd commentedon Jul 26, 2021
The first problem is with our handling of this line in Launcher64.exe.config:
<probing privatePath="parts/core;parts/bob" />We only have this set up for loading assemblies, not native dll's referenced via DllImport. I'm not sure where is the correct place to fix that.
madewokherd commentedon Jul 26, 2021
Looking at the method causing the invalid IL error, it's using a vararg pinvoke call, which was implemented in Wine Mono 6.2.0 (Proton 6.3 currently has Wine Mono 6.1.2). You can either install that manually via the msi (newest is https://dl.winehq.org/wine/wine-mono/6.3.0/wine-mono-6.3.0-x86.msi) or try proton experimental which has 6.2.2.
madewokherd commentedon Jul 26, 2021
It turns out Mono finds the native dll referenced via DllImport just fine, but it depends on another dll in the same directory, which isn't being searched for dependencies. This should just be a matter of using the LOAD_WITH_ALTERED_SEARCH_PATH flag when loading those dll's.
madewokherd commentedon Jul 26, 2021
After fixing the dll load issue and using latest Wine Mono, the next problem is that it tries to read C:\Program Files (x86)\Steam\userdata\\config\localconfig.vdf. I worked around this by symlinking ~/.steam/root/userdata to the directory in the Wine prefix. After that, the menu comes up, but I didn't try to start the game.
coljac commentedon Jul 27, 2021
@madewokherd After adding a symlink such that 'C:\Program Files (x86)\Steam\userdata\config\localconfig.vdf' is visible within wine, and then running with proton experimental, the splash screen still appears but the menu didn't successfully show up. The log is below which includes:
I also tried uninstalling wine-mono 6.2 and installed 6.3.0 into the game's wineprefix (so running
WINEPREFIX=/steam/steamapps/compatdata/754530/pfx "/steam/steamapps/common/Proton - Experimental/files/bin/wine" uninstallershows 6.3.0 installed), but the exception seems the same. That log is appended as well.Proton experimental log
With mono 6.3.0
madewokherd commentedon Jul 27, 2021
Oh, github's formatting messed up the path in my earlier post, it should have said
C:\Program Files (x86)\Steam\userdata\<userid>\config\localconfig.vdfcoljac commentedon Jul 31, 2021
@madeworkherd Using Proton Experimental, with wine mono 6.3.0, I was unable to reproduce the reported success in getting as far as the menu. Are you able to share any further info on wine version/configuration which got to this step? Despite various attempts I seem to have hit a road block with the "unhandled C++ exception" above. The only other thing to add is that trying on a machine with no GPU, the game got as far as the splash screen and ended up in an endless loop with the following (I killed it after the log file reached 11G):
madewokherd commentedon Jul 31, 2021
Well, if the symlink didn't work, you might be getting a C++ exception for a different reason than I did, but just to make sure you could get a +file log to see the exact unix filename it's trying to access.
coljac commentedon Aug 1, 2021
@madewokherd Thanks for taking another look. Looking at the longer log (+file) I found the .vdf was still an issue - I symlinked the wrong directory - and once I fixed this, I could get the menu to work and it navigates fine.
Launching the game resulted in a crash, it seems to result in the same "C++ exception". Here's the logs with and without `WINEDEBUG="+file".
proton log
Large log with +file: withpfile.zip
12 remaining items
kisak-valve commentedon Sep 10, 2021
You seemed to have missed the intent of what I wrote. It's not that the launch option is now deprecated, it never was considered supported. That doesn't make it any less useful for troubleshooting.
We get wined3d more or less for free from upstream wine, and it doesn't hurt to keep it around, but most quirks with it aren't investigated here. Instead, upstream supports that render path and fixes in wined3d come in with all the other wine changes when Proton does a major rebase onto a newer version of wine.
piotr-gbyliczek commentedon Sep 10, 2021
Ah. That makes sense, I see. I will try DXVK anyway, but expect it will not work. In which case I will report it against Wine.
piotr-gbyliczek commentedon Sep 10, 2021
Ah, the plot thickens !
After cleaning up wine prefix, removing user-settings.py file from proton - experimental folder and removing PROTON_USE_WINED3D=1 from launch options, it seems that game can work with DXVK. All it needed was a symlink of userdata directory into the prefix and symlinks of 3 dlls from ./parts/core to the game dir (both mentioned above).
It seems that this is the case in which game seems to be free from graphical glitches, but crashes at 90% loading any mission.
Attached a log file from that session.
steam-754530.log
Only thing I can see there so far is :
[0000000000000114:] EXCEPTION handling: System.IO.FileNotFoundException: Could not load file or assembly 'Z:\home\peem\SteamLibrary\steamapps\common\Proton - Experimental\files\share\wine\mono\wine-mono-6.3.0\lib\mono\gac\PresentationCore\4.0.0.0__31bf3856ad364e35\pl-PL\PresentationCore.resources.dll' or one of its dependencies.I've created the pl-PL folder and symlinked 2 files present in Proton - Experimental\files\share\wine\mono\wine-mono-6.3.0\lib\mono\gac\PresentationCore\4.0.0.0__31bf3856ad364e35 into it, but it did not change the game's behaviour, still crashing at 90% loading of any mission.
kisak-valve commentedon Sep 10, 2021
From the log:
I think this looks like #5007 (comment).
piotr-gbyliczek commentedon Sep 10, 2021
Are we did the full circle then :)
Not sure what it means, this was the comment that pointed me and - probably - @coljac towards using unsupported wined3d, right ?
Are we saying this is bug in application and it will not work with DXVK ? Or is this somehow still using wined3d on my machine ? Actually, it may be irrelevant, I feel like both answers mean we need to report bug with wine and /or with game developers :)
coljac commentedon Oct 1, 2021
Just an update: While the menus still work, the game still crashes when entering the game proper with Proton Experimental as of 2020-10-02. It's the same:
Log attached.
log_experimental_20211002.zip
JJones780 commentedon Jan 29, 2023
I followed CaptainPanda34's entry on protondb and it works very well. I suspect his issues are present for me as well but am going to wait until the VR upgrade to come back to it. It looks very nice as far as I can tell!
I had previously run :
sudo winetricks --self-update( very important as if you/your distro doesn't have latest winetricks you will get old dlls installed by protontricks )
protontricks 754530 d3dcompiler_47As I installed this game on an external drive:
Excited to see this in VR! Any week now?
raven-intheclouds commentedon Jun 4, 2024
Game works, but the mouse cursor is invisible in the game menu. This is a regression; the cursor is visible in Proton 7.0, and invisible in Proton 8.0, 9.0, Experimental.
After doing the following as noted in the previous comment:
The game starts, renders and plays fine on Proton 9.0, 8.0. It has normal perfomance from what it looks like. I haven't tried binding joysticks. This is on Steamdeck docked and game mode.
For Proton 7.0, one needs to use
PROTON_USE_WINED3D=1 %command%.I would be glad to debug, please ping me if so.
kisak-valve commentedon Jun 4, 2024
Hello @raven-intheclouds, please add
PROTON_LOG=1 %command%to the game's launch options, reproduce the regression, and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.) Also, please note if running the game withPROTON_USE_WINED3D=1 %command%on newer Proton has any effect to the regression you've described so that it can be removed from the differential diagnosis.raven-intheclouds commentedon Jun 4, 2024
Argh, sorry, forgot to append the log. The following log is from starting the game, clicking into quick missions, and starting the first mission to fly for some seconds, which renders fine.
steam-754530.log
Running with
PROTON_USE_WINED3D=1 %command%on Proton 9 still shows the regression of invisible cursor.raven-intheclouds commentedon Dec 11, 2024
This regression is now gone in Proton 9.0-3 and 9.0-4. The game shows the system pointer on its menus, and the game pointer correctly when one starts flying and is inside of the cabin.
The game seems to work fine here, but one needs to set it on to fullscreen, at least for me.