[Bug 58565] New: Very high single core CPU usage while doing LAN gaming with DirectPlay on FIFA 2005
http://bugs.winehq.org/show_bug.cgi?id=58565 Bug ID: 58565 Summary: Very high single core CPU usage while doing LAN gaming with DirectPlay on FIFA 2005 Product: Wine Version: 10.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: dplay Assignee: wine-bugs(a)winehq.org Reporter: salva.liebana(a)gmail.com Distribution: --- . So , I have both pcs with cachyOS, exactly the same settings. I've tried to do multiplayer on FIFA 2005, that runs great with dxvk with very low cpu/gpu usage since it's a very old game (even at hacked 1080p). After failing on doing lan game I remembered these games tend to use directplay, so I did install it on both , disable the firewall, and both pcs experienced a severe spike on one core to 100% and the framerate tanks. how to reproduce: After install DirectPlay with winetricks on wine-10.12.r0.gb09545bc ( TkG Staging NTsync, yes, I have kernel 6.15 ) in wow64 mode with a 64 bit prefix running FIFA 2005. problem: 1 core goes mad at 100% on both pcs and makes the game unplayable. also uses tons of energy for obvious reasons. -- 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=58565 --- Comment #1 from Salvador <salva.liebana(a)gmail.com> --- sorry, just to clarify, the problem occurs when doing LAN netplay with directplay. not on single player. -- 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=58565 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEEDINFO CC| |austinenglish(a)gmail.com Ever confirmed|0 |1 --- Comment #2 from Austin English <austinenglish(a)gmail.com> --- To be clear, are you using native directplay (winetricks directplay)? If so, this isn't an issue in winetricks directplay (and possibly is invalid, given the native component, but I'll leave that for someone more familiar with wine's directplay/networking components). -- 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=58565 --- Comment #3 from Salvador <salva.liebana(a)gmail.com> --- (In reply to Austin English from comment #2)
To be clear, are you using native directplay (winetricks directplay)? If so, this isn't an issue in winetricks directplay (and possibly is invalid, given the native component, but I'll leave that for someone more familiar with wine's directplay/networking components).
You are right, yet, the ticket is still valid, bc the issue stays the same with built in wine directplay implementation. I remade both prefixes, no winetricks directplay.. and the experience was exactly the same. turns out that my firewall was tjhe problem on not working the first time, but again, super bad performance and very high cpu usage. the ticket still holds. -- 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=58565 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|dplay |-unknown Status|NEEDINFO |NEW --- Comment #4 from Austin English <austinenglish(a)gmail.com> --- Thanks, sounds like it's not a directplay issue then, since native has the same behavior. -- 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=58565 --- Comment #5 from Salvador <salva.liebana(a)gmail.com> --- (In reply to Austin English from comment #4)
Thanks, sounds like it's not a directplay issue then, since native has the same behavior.
sure, may be NTsync (I wasnt able to disable even with the proper ENV VAR) or wow64.. or something else. yet, it's hard to justify this kind of performance and CPU utilization. -- 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