[NFSMW] Instant crash when turning on the game using Wine
Issue probably related to #1013 and #480.
Trying to launch NFS: MW using Lutris and its built in installer - game works fine without WFP, however after installing it the game crashes instantly after launch.
Config:

Crashlog, on external site for report clarity: https://paste.sh/ngNnh3B5#QUWVyIG1c2YVj2go8lF0_lKL=
What is even more weird, Carbon and its WFP work fine.
System specs: https://paste.sh/EGitCKS8#wJeygA1b2RadCbAjvnZvixgb=
Your config seems fine, I use almost the same setup (except with DXVK turned on and a different Wine version) and it works for me. Turning off DXVK didn't cause it to crash so it's not that either. Have you tried other Wine versions?
I have the same issue with you, but i using steam deck.
Hi, @baluw
Did you manage to resolve the issue in the meantime? I noticed you're missing the DLL overrides in the second screenshot.
You need to add dinput8 as a native then builtin as per the instructions here.. This is key to get the ASI loader to run and load the plugins.
It works fine for me under Proton and Wine (except that wined3d doesn't like Reshade, that's the only caveat).
- No, 2. This did not resolve the issue as I vividly remember trying this to fix it
On Mon, 12 Sep 2022 at 14:19, Lovro Pleše @.***> wrote:
Hi, @baluw https://github.com/baluw
Did you manage to resolve the issue in the meantime? I noticed you're missing the DLL overrides in the second screenshot.
You need to add dinput8 as a native then builtin as per the instructions here. https://cookieplmonster.github.io/setup-instructions/#proton-wine. This is key to get the ASI loader to run and load the plugins.
It works fine for me under Proton and Wine (except that wined3d doesn't like Reshade, that's the only caveat).
— Reply to this email directly, view it on GitHub https://github.com/ThirteenAG/WidescreenFixesPack/issues/1088#issuecomment-1243657138, or unsubscribe https://github.com/notifications/unsubscribe-auth/AELDVDLULDVXTFVHVYANPL3V54NWBANCNFSM5ZBQRTDA . You are receiving this because you were mentioned.Message ID: @.***>
OK in that case can you do either of these things? (first is better than second but whatever works)
- Try out the latest version again and send that crash log again
- Send the ASI (and PDB file if you have it) over so I can debug the exact version you had at the time you had the crash
I've updated the ASI since then and the addresses have changed so I don't know where's what in that crash log you sent earlier.
As there's no follow up, I'm closing this. Open another issue if/when you want to debug this.