Warcraft III stopped working after v2.3.1

[IceWolf0110]

I didnt bother to change the version but I was curios if new version give any improvement. I tested all the version but since v2.4 and above, the game just not playable anymore.

Im using nvidia card, proprietary driver, fedora 41 and flatpak version of lutris.

[K0bin]

Can you upload DXVK logs?

[WinterSnowfall]

Works fine here. Are you sure you are using both dxvk's d3d8.dll and d3d9.dll with the game?

P.S.: Might be a Lutris bug or whatnot, but that message won't be shown with a proper dxvk setup in Wine.

[IceWolf0110]

Can you upload DXVK logs?

where's the log? I can provide.

[IceWolf0110]

I download the one in the release section and worked, maybe it's lutris bug.

Edit: not lutris bug, I exit the game and restart and now it's not working again.

[IceWolf0110]

it's not working again.

[Blisto91]

How are you setting the dxvk version? Proton GE ships its own so the lutris version selection shouldn't have an effect

[IceWolf0110]

How are you setting the dxvk version? Proton GE ships its own so the lutris version selection shouldn't have an effect

override dlls just like wine, proton is just wine with some magic sources of Valve on top of that.

[Blisto91]

No i meant if you are replacing the DLLs manually?

[IceWolf0110]

No i meant if you are replacing the DLLs manually?

you could replace them manually and disable dxvk option

[Blisto91]

In regards to getting a log that we could look at.
To get a standard Proton (GE) log out of Lutris right click on the game -> choose "Configure" -> select "Runner options" tab -> scroll to the bottom -> at the "Output debugging info" option select "Inherit from environment". (just selecting enable will disable the standard extra Proton log channels/options)
Then go to the "Sytem options" tab -> at the "Environment variables" option click "Add" -> set key to PROTON_LOG and value to 1.
A log named steam-default.log will then appear in your users home folder. When you have attached it here you can just remove the environment variable again and set Output debugging info to disabled.