https://bugs.winehq.org/show_bug.cgi?id=52275
Bug ID: 52275 Summary: VODKALIBUR Mod Tool - Renders Specific Folder Path Text Field Incorrectly Product: Wine Version: 7.0-rc1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: nekoNexus@protonmail.ch Distribution: ---
Created attachment 71406 --> https://bugs.winehq.org/attachment.cgi?id=71406 WineStaging7.0-rc1 Terminal Log and Screenshot
SHA256: 4ddbc85ed075aaf3943319945d0dc7d43b7be4e244674f4df8f47c6d18b6dbe3
Download: https://web.archive.org/web/20211220213203/https://cdn.discordapp.com/attach...
At the moment, to the get the application running and (mostly) behaving correctly, Winetricks needs to be ran with these components:
WINEPREFIX=[path/to/desired/prefix] winetricks -q dotnet48 arial d3dcompiler_47 wmp11
--- NOTE: Testing this REQUIRES that you either own the game and save data or otherwise have access to someone else's save files to perform this with. ---
After this is done, run the program in the prefix and you'll get to a settings configuration screen (if the program tells you that there's an update (as it will definitely do if you have an active internet connection), tell it no because that (obviously) changes the version this report is about.
Once at the settings screen, there will be a folder path field that asks you to select the game's save data location because it cannot auto-detect the save path due to this likely being a separate prefix than Proton's - since we're using vanilla Wine. Point this path towards:
<Steam-folder>/steamapps/compatdata/544750/pfx/drive_c/users/steamuser/AppData/Local/SoulcaliburVI/Saved/SaveGames/<some_id_number>/GAME/
Once this is done, it will appear as though the path was never selected in the field, but this is actually false: if you get close enough to your screen, you can see that the path actually is there but clearly far too difficult to see the way that it should.
The log I am attaching is of a broader test of the application, where I tested whether the application functioned correctly, but the related output from this part is part of the log as I had done this process in the same run; I will provide my other (unrelated) findings as (a) separate report(s).