https://bugs.winehq.org/show_bug.cgi?id=52240
Bug ID: 52240 Summary: VODKALIBUR Mod Tool Crashes on Starup Product: Wine Version: 6.23 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 71349 --> https://bugs.winehq.org/attachment.cgi?id=71349 Staging6.23_Logs_and_dotnet_prefix_backtrace
(The mod-tool is meant for SoulCalibur VI)
In a clean Wine Staging 6.23 prefix, the program crashes on startup without displaying anything.
Running the program with dotnet48 gets the program to display a splash-screen before throwing an exception error and dropping 3 .dll files in the app's directory.
SHA256: 4ddbc85ed075aaf3943319945d0dc7d43b7be4e244674f4df8f47c6d18b6dbe3
Download: https://cdn.discordapp.com/attachments/651396632167841812/906212137431621632... (Releases are typically obtained with in-app updates or via the developer's Discord server - this is a direct link to the last WPF build that was released via a direct Discord attachment at the time of writing)
https://bugs.winehq.org/show_bug.cgi?id=52240
nekoNexus@protonmail.ch changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |dotnet, download URL| |https://appdb.winehq.org/ob | |jectManager.php?sClass=vers | |ion&iId=40470&iTestingId=11 | |1594 Distribution|--- |ArchLinux
https://bugs.winehq.org/show_bug.cgi?id=52240
Louis Lenders xerox.xerox2000x@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |xerox.xerox2000x@gmail.com Component|-unknown |mscoree URL|https://appdb.winehq.org/ob |https://cdn.discordapp.com/ |jectManager.php?sClass=vers |attachments/651396632167841 |ion&iId=40470&iTestingId=11 |812/906212137431621632/VODK |1594 |ALIBUR.exe Keywords|dotnet |
--- Comment #1 from Louis Lenders xerox.xerox2000x@gmail.com --- Confirming.
Marking as mscoree bug, see crash below
@Reporter of bug: It starts here without crashing using native dotnet48 and d3dcompiler_47 (and i also installed arial). So maybe you could try 'winetricks d3dcompiler_47' to get a bit further with native dotnet48. (Though i got a warning about internet connection not working.... Maybe yet another bug)
Unhandled Exception: System.TypeLoadException: Could not load type of field 'VODKALIBUR.BattleTracker:iMemory' (19) due to: Could not load file or assembly 'Memory, Version=1.2.18.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. at System.Runtime.CompilerServices.AsyncVoidMethodBuilder.Start[TStateMachine] (TStateMachine& stateMachine) [0x0002c] in <bee01833bcad4475a5c84b3c3d7e0cd6>:0 at VODKALIBUR.Splash.SplashWindow_Loaded (System.Object sender, System.Windows.RoutedEventArgs e) [0x00034] in <bd7ec205411c478cb45fceb4f5d2cc4e>:0 at System.Windows.RoutedEventHandlerInfo.InvokeHandler (System.Object target, System.Windows.RoutedEventArgs routedEventArgs) [0x0002a] in <e43a66ac5a17469c8cf758a9c0e850de>:0 at System.Windows.RouteItem.InvokeHandler (System.Windows.RoutedEventArgs routedEventArgs) [0x00001] in <e43a66ac5a17469c8cf758a9c0e850de>:0
https://bugs.winehq.org/show_bug.cgi?id=52240
Louis Lenders xerox.xerox2000x@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever confirmed|0 |1
--- Comment #2 from Louis Lenders xerox.xerox2000x@gmail.com --- Also forgot to mention: You have to run the exe in the directory where it resides, otherwise warnings pop up about missing dlls.
https://bugs.winehq.org/show_bug.cgi?id=52240
--- Comment #3 from nekoNexus@protonmail.ch --- Created attachment 71357 --> https://bugs.winehq.org/attachment.cgi?id=71357 Screenshots and New Backtrace
Adding d3dcompiler_47 (I also added the arial font this time) managed to get the program to run and enter the settings configuration screen, though with one bug I noticed (more on that later).
In the screenshots, I attached, I listed the order in which the program proceed before it triggered another exception error where I collected the new backtrace for.
I forgot to make the terminal where I ran this have infinite scrolling so I couldn't grab the terminal output at the time though; I'll have to redo this soon when I have a moment.
As for that other bug with the settings menu I mentioned (which is also in one of the screenshots), pointing to the savegame path manually doesn't populate the path field for it but does for the other fields (like selecting the game's "pak" folder path).
https://bugs.winehq.org/show_bug.cgi?id=52240
--- Comment #4 from nekoNexus@protonmail.ch --- Also note that I skipped the part where it asked to update itself*
https://bugs.winehq.org/show_bug.cgi?id=52240
Fabian Maurer dark.shadow4@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |dark.shadow4@web.de
--- Comment #5 from Fabian Maurer dark.shadow4@web.de --- Archived download at: https://web.archive.org/web/20211220213203/https://cdn.discordapp.com/attach...
https://bugs.winehq.org/show_bug.cgi?id=52240
--- Comment #6 from nekoNexus@protonmail.ch --- Created attachment 71369 --> https://bugs.winehq.org/attachment.cgi?id=71369 WineStaging6.23-Logs-Screenshots-and-Backtrace-Followup-3
I rebuilt the prefix with the same configuration and it threw 2 new errors (as in-program message boxes) during the settings configuration phase: - The first when selecting the savedata folder for the game (it actually realized that the chosen path in-app was all whitespace) - and the second was when I tried to save the settings upon attempting to close the config window
I saved screenshots for these.
After the "download" process it does after this, checking off boxes (with a missing icon or font to the left of the checklist?), it attempts to launch another process of itself - the same part that I mentioned fails last time and throws the new exception error. I included a screenshot for this as well - though, last time the new window it brought up actually rendered and this time it did not. :/
Those aside, I included the terminal output for this attempt along with another backtrace.
https://bugs.winehq.org/show_bug.cgi?id=52240
--- Comment #7 from Louis Lenders xerox.xerox2000x@gmail.com --- (In reply to nekoNexus from comment #6)
I rebuilt the prefix with the same configuration and it threw 2 new errors (as in-program message boxes) during the settings configuration phase:
Hi, policy is one bug per bugreport, so I guess it`d be better to open new bugreport for upfollowing bugs. Let`s keep this one for the Mono-bug
(Interestingly from your log the upfollowing crashes seems to occur inside wmp.dll. Does something 'winetricks -q wmp11' change anything?
https://bugs.winehq.org/show_bug.cgi?id=52240
--- Comment #8 from nekoNexus@protonmail.ch --- Ah, I'll keep that in mind; thanks.
As for your question, this (in addition to the other options [using Wine Staging 7.0-rc1]) did make the program run properly, but a key function of the program was not working - though this did not produce an error, it just seemed to not load the game's save files.
As for the folder path being "invisible," as I mentioned before: turned out that it was actually a font coloring issue for some reason; the font for that field just misbehaved and rendered so dark that it is VERY difficult to notice unless you get very close to your screen.
I'll make a separate issues for these.
https://bugs.winehq.org/show_bug.cgi?id=52240
--- Comment #9 from Neko-san nekoNexus@protonmail.ch --- Created attachment 73563 --> https://bugs.winehq.org/attachment.cgi?id=73563 Wine Staging 7.20 Log and Backtrace
This solution used to work but has regressed In Wine Staging 7.20, `winetricks -q dotnet48 d3dcompiler_47 arial wmp11` no longer permits the app to launch at all.
I'm attaching a backtrace along with a terminal log
https://bugs.winehq.org/show_bug.cgi?id=52240
Esme Povirk madewokherd@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |madewokherd@gmail.com
https://bugs.winehq.org/show_bug.cgi?id=52240
--- Comment #10 from Neko-san nekoNexus@protonmail.ch --- Created attachment 77544 --> https://bugs.winehq.org/attachment.cgi?id=77544 Vanilla Wine 9.22 Output Log
Update on this issue: The workaround works again with Wine 9.22 (winetricks -q wmp11 arial dotnet48 d3dcompiler_47)
Using the latest executable release (archive.org link, since the dev only releases on Discord): https://web.archive.org/web/20241207210421/https://cdn.discordapp.com/attach...
-----
However, several issues (errors) appear that prevents the app from proceeding past initial configuration during the setup process.
One of the errors is "recoverable" in that it'll still proceed despite it, but a second error appears (by the app) along with an Unhandled Exception window that interacting with causes Wine to spawn a backtrace.
Additionally, attempting to copy the errors via the "Report bug" button in-app doesn't actually copy the error message to the clipboard.
Also, at one point the app tries to connect to the internet to check for updates but fails to on every attempt.
I have screenshots of all of these: - Internet Connection Issue: https://i.imgur.com/DWhSAAw.png - First Error: https://i.imgur.com/42yUx0b.png - Second Error: https://i.imgur.com/XPNDHGt.png - Accompanying Unhandled Exception Window: https://i.imgur.com/VlSwqtP.png
https://bugs.winehq.org/show_bug.cgi?id=52240
--- Comment #11 from Neko-san nekoNexus@protonmail.ch --- Created attachment 77545 --> https://bugs.winehq.org/attachment.cgi?id=77545 WIne 9.22 Backtrace
Also, to clarify why I LZMA compressed the 9.22 log: I did so because I had to compress it really hard because the file size was still pretty big if I didn't do so