[Bug 45967] New: Beat hazard 2 - bad network/float behavior
https://bugs.winehq.org/show_bug.cgi?id=45967 Bug ID: 45967 Summary: Beat hazard 2 - bad network/float behavior Product: Wine Version: 3.17 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: spleefer90(a)gmail.com Distribution: --- Tested with DXVK 0.81 and wine-devel/staging 3.17. git staging from yesterday(maybe earlier) seems incapable of launching steam, so stable versions. Game hard crashes on wine-devel when trying to start a round of the game but that's irrelevant for this report(as it works on staging). The game didn't even go through the version check at bootup until the developer changed a variable with float into an int. Current problems are some kind of message check happening over and over in the main menu, leaderboards only showing score and not any other information, and ingame leaderboards fluctuating between completely random score. Game also crashes when trying to view some leaderboards tab, although am not sure if that relates to the network issue, if it even is a network issue The only relevant log WINE ever throws is 003a:fixme:wininet:InternetCheckConnectionW (L"https://aws.amazon.com/" 1 0) Which I don't think is behind the issue. Developer is reachable on Discord - https://discord.gg/beathazard -- 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.
https://bugs.winehq.org/show_bug.cgi?id=45967 zzzzzyzz(a)hacari.org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |zzzzzyzz(a)hacari.org -- 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.
https://bugs.winehq.org/show_bug.cgi?id=45967 João Ferreira <devilj(a)outlook.pt> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |devilj(a)outlook.pt --- Comment #1 from João Ferreira <devilj(a)outlook.pt> --- Experiencing the same bug under wine-staging 3.18. The leaderboards also get somewhat corrupted, leading to occasional crashes. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=45967 --- Comment #2 from C0rn3j <spleefer90(a)gmail.com> --- As a note, launching the game with -SteamBoards parameter now disables the problematic part (contacting AWS) and the game seem to work OK under WINE without the network leaderboards function. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=45967 --- Comment #3 from João Ferreira <devilj(a)outlook.pt> --- Created attachment 62966 --> https://bugs.winehq.org/attachment.cgi?id=62966 Full console output Captured with +timestamp,+tid,+debugstr,+wininet. I don't really think this is useful, but whatever. Have at 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.
https://bugs.winehq.org/show_bug.cgi?id=45967 --- Comment #4 from João Ferreira <devilj(a)outlook.pt> --- Bug still present as of Wine-staging 4.0rc1. (Regular Wine exhibits different behavior, now that it can run Steam again; maybe change this bug report to target wine-staging only?) What types of logs would be useful to Wine devs? There's a free game by the same developer, Martial Arts Brutality, which displays similar behavior. It's free on Steam: https://store.steampowered.com/app/618080/Martial_Arts_Brutality/ -- 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.
https://bugs.winehq.org/show_bug.cgi?id=45967 --- Comment #5 from João Ferreira <devilj(a)outlook.pt> --- This is now fixed for me in 4.0rc3 (staging and non-staging alike). Thanks! -- 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.
https://bugs.winehq.org/show_bug.cgi?id=45967 --- Comment #6 from João Ferreira <devilj(a)outlook.pt> --- Actually, this is also suddenly fixed on old versions such as staging-3.18. I don't know what has changed (certainly not a game update), outside of Arch Linux updates. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=45967 --- Comment #7 from C0rn3j <spleefer90(a)gmail.com> --- Created attachment 63090 --> https://bugs.winehq.org/attachment.cgi?id=63090 Wine 4.0rc3 crash log cutout I'm too on a fully up to date Arch Linux box, retested in new prefix with wine-staging 4.0rc3. Am still experiencing the same issue (just launching the game still gives the endless flashing Working... screen). Are you sure you're not launching the game with a parameter that disables the leaderboards? I've also tested with wine 4.0rc3 and that crashes after entering the main menu (where the Working... screen would appear) 4958.350:0253:warn:debugstr:OutputDebugStringA "Error calling WriteConsole\r\n" -- 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.
https://bugs.winehq.org/show_bug.cgi?id=45967 --- Comment #8 from C0rn3j <spleefer90(a)gmail.com> --- Created attachment 63091 --> https://bugs.winehq.org/attachment.cgi?id=63091 game debug.txt from the crash I wanted to add that the 4958.350:0253:warn:debugstr:OutputDebugStringA "Error calling WriteConsole\r\n" is not present for me (although might be something else) and instead the game crashes at this point, I took this line from the first posted log. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=45967 --- Comment #9 from C0rn3j <spleefer90(a)gmail.com> --- Got the game to work great with the help of JohnTH. The game needs msvcr120 override to work, for that you can just winetricks vcrun2013. Then the game will crash because of missing country code defined in reg keys - https://bugs.winehq.org/show_bug.cgi?id=46196 Simply create the following via regedit as a workaround HKEY_CURRENT_USER\Control Panel\International\Geo Key name: Nation Type: REG_SZ (String) value: 124 (example, use a real one from https://docs.microsoft.com/en-us/windows/desktop/intl/table-of-geographical-...) After that the game launches and networking features work great! -- 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.
https://bugs.winehq.org/show_bug.cgi?id=45967 --- Comment #10 from João Ferreira <devilj(a)outlook.pt> --- I'll add that: 1) This bug is still present as of Wine 4.21; 2) This bug occurs with Wine's implementation of msvcr120. Using winetricks to install Microsoft's native runtime fixes this bug. Someone should probably change "Component" to "msvcrt" or something like that; "Severity" should probably be "minor" or less, since this is so easy to work around. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=45967 Zebediah Figura <z.figura12(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|-unknown |msvcrt -- 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.
https://bugs.winehq.org/show_bug.cgi?id=45967 --- Comment #11 from Gijs Vermeulen <gijsvrm(a)gmail.com> --- <https://source.winehq.org/git/wine.git/commitdiff/7695433c0511e0cd3c035e17a1ec10d86f30dd40> mentions this bug, can anyone please retest with wine-5.4? -- 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.
https://bugs.winehq.org/show_bug.cgi?id=45967 --- Comment #12 from João Ferreira <devilj(a)outlook.pt> --- Confirming fixed from Wine 5.0rc1 through 5.4 by patch 7695433c0511e0cd3c035e17a1ec10d86f30dd40! -- 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.
https://bugs.winehq.org/show_bug.cgi?id=45967 Gijs Vermeulen <gijsvrm(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Fixed by SHA1| |7695433c0511e0cd3c035e17a1e | |c10d86f30dd40 Resolution|--- |FIXED --- Comment #13 from Gijs Vermeulen <gijsvrm(a)gmail.com> --- (In reply to João Ferreira from comment #12)
Confirming fixed from Wine 5.0rc1 through 5.4 by patch 7695433c0511e0cd3c035e17a1ec10d86f30dd40!
Marking FIXED then, thanks for the fast reply! -- 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.
https://bugs.winehq.org/show_bug.cgi?id=45967 Alexandre Julliard <julliard(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #14 from Alexandre Julliard <julliard(a)winehq.org> --- Closing bugs fixed in 5.5. -- 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 (2)
-
wine-bugs＠winehq.org -
WineHQ Bugzilla