[Bug 59332] New: [Error Report] Dragon Ball Online Galaxy: Cryptic Error
http://bugs.winehq.org/show_bug.cgi?id=59332 Bug ID: 59332 Summary: [Error Report] Dragon Ball Online Galaxy: Cryptic Error Product: Wine Version: 11.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs@list.winehq.org Reporter: perithefrost@proton.me Distribution: --- Created attachment 80264 --> http://bugs.winehq.org/attachment.cgi?id=80264 Error shown in the ingame debugger and bug report tool Good afternoon, I have some issues with Wine, on all 3 versions (Mac, Linux and Android (In this case using Winlator as a frontend)) Me and the staff/developers from the Dragon Ball Online Galaxy team ran into an issue with the game. We thought we fixed it before, thinking it was a DXVK bug, but after the latest update, on all platforms that use Wine (or Proton for those that have it available), the game outright throws this cryptic error: The error before used to be a bug on DXVK.conf, but after that error had been fixed, after a while this error in the following attachments emerged. The lead developer, Forest, and I are trying to fix it. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=59332 --- Comment #1 from Rafał Mużyło <galtgendo@o2.pl> --- ...for one, are you running this is the locale the program expects, cause the top part of the screenshot suggests otherwise ? That's likely just a matter of incomplete localization, not the real problem here, still... Other than that, attach the full console output of the game. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=59332 --- Comment #2 from Joaquin Marquez <perithefrost@proton.me> --- Created attachment 80268 --> http://bugs.winehq.org/attachment.cgi?id=80268 Log and dump file from DBO, ran at 28/01/26 This is the log that I was able to export thanks to the game using BugTrap. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=59332 --- Comment #3 from Rafał Mużyło <galtgendo@o2.pl> --- Whatever that BugTrap tool is, it may be something cute and useful on Windows, but in the context of wine it's far less so. One of the first things you get asked here is 'full console output' as the document linked to the bug filing page describes it - https://gitlab.winehq.org/wine/wine/-/wikis/FAQ#how-can-i-get-a-debugging-lo... . Sure, sometimes it ain't all that useful either, but in the majority of the cases it is (or becomes so, after adding a few debug channels - just don't use the settings from the next paragraph: 'relay' is pretty much the *last* resort; just go with defaults till you get asked for more). -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=59332 --- Comment #4 from Joaquin Marquez <perithefrost@proton.me> --- Created attachment 80269 --> http://bugs.winehq.org/attachment.cgi?id=80269 Wine logs (28/01/26, clean prefix) Here it is, apologies if I misunderstood before. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=59332 --- Comment #5 from Rafał Mużyło <galtgendo@o2.pl> --- ...something swallows the crash output, likely the debug dialog. In the standard crash dialog, picking one of the options does that, while picking the other drops it to console (IIRC, picking 'Cancel' does that, but I'm not 100% sure), but we're dealing here with a custom dialog, so I don't know if you even have that option... Check if picking another button among the available makes the game print crash backtrace to the console and post that (still the full output, not just crash backtrace). Otherwise, check if creating/setting DWORD value 'ShowCrashDialog' of 0 for Software\Wine\WineDbg regkey gets you that output (it probably already exists, but is set to the default (1)). Oh, and try to run the game at least once in zh_CN.utf8 locale (as that's likely the one game expects, given the support link), just to see if the garbage at the top becomes something readable. Sure, most likely it will be Chinese, so it will tell me (and likely you too) nothing, but someone who knows the language might find it helpful - I mean, given the nature of those dialogs, most likely not, but if there's a chance... -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=59332 --- Comment #6 from Joaquin Marquez <perithefrost@proton.me> --- Created attachment 80275 --> http://bugs.winehq.org/attachment.cgi?id=80275 Back trace of DBOLauncher + DBOGame exe, 29/01/26 Did all of the steps so far, and BugTrap just burped the same error: ACCESS_VIOLATION at location. Same error as displayed. Had to force Wine to export a debug trace. The lead developer again, does not know how to program compatibility for Wine/Proton, given this is a custom server for an MMO that is long shut down. Still, as he does have the code, I will also tell him to contact this forum in order to be of more assistance too.
From my side, here is the debug trace. I hope it is of utility.
-- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
participants (1)
-
WineHQ Bugzilla