You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just been looking through the script and noticed a possible issue. cnc-ddraw is being copied into the system folder (which is fine, wine should use it now by default). However, then a dll override is added (native,builtin) that forces wine to load ddraw.dll from the game folder rather than the one from the system folder. Is there any reason why it's set up like this or is it a bug?
The result is now that if you install a game from steam/gog that is shipped with a ddraw.dll that isn't working in wine then cnc_ddraw would actually not fix the issue because of the override.
The text was updated successfully, but these errors were encountered:
Just been looking through the script and noticed a possible issue. cnc-ddraw is being copied into the system folder (which is fine, wine should use it now by default). However, then a dll override is added (native,builtin) that forces wine to load ddraw.dll from the game folder rather than the one from the system folder. Is there any reason why it's set up like this or is it a bug?
https://github.com/Winetricks/winetricks/blob/master/src/winetricks#L5484
The result is now that if you install a game from steam/gog that is shipped with a ddraw.dll that isn't working in wine then cnc_ddraw would actually not fix the issue because of the override.
The text was updated successfully, but these errors were encountered: