[Bug 57986] New: Final Fantasy XI Online window borders and content behave strangely
https://bugs.winehq.org/show_bug.cgi?id=57986 Bug ID: 57986 Summary: Final Fantasy XI Online window borders and content behave strangely Product: Wine Version: 9.16 Hardware: x86-64 URL: https://web.archive.org/web/20210810150839/http://www. playonline.com/ff11eu/download/media/install_win.html OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: win32u Assignee: wine-bugs(a)winehq.org Reporter: chiitoo(a)gentoo.org Regression SHA1: cb1c03b926ca01619be02f835f382c1dd7d4a478 Distribution: Gentoo After cb1c03b926c [1], Final Fantasy XI Online has its built-in borders behave in a new way. When running in windowed mode, the game window has a 2 pixel border around it, and with the mentioned commit, moving the window makes the game content shift slightly, perhaps 2 pixels at a time, almost making a circle inside, or over the borders (or at least that is what it looks like). During normal operation, due to this border, the actual window dimensions are 1924x1084 when set to 1920x1080, almost as if the bordering area was a part of another window the game is wrapped inside of. Sometimes after moving the window around a bit, things may or may not stabilise, until the game window is re-sized (I'm not sure that is even possible to do on Windows, as the game does not account for the new size at all, and will be stretched). Other times the game window appears without the mentioned border, at the size of 1920x1080 when set to run at that size, and the border may or may not appear when the window is moved or the size is adjusted. Last tested at commit: e66405a50406e While the installer can be downloaded for free, getting to test this part will require purchasing the game, or ordering a free trial download (which may or may not be available at times, and still requires account creation). Thank you! 1. https://gitlab.winehq.org/zfigura/wine/-/commit/cb1c03b926ca01619be02f835f38... -- 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=57986 Chiitoo <chiitoo(a)gentoo.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download, regression -- 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=57986 Chiitoo <chiitoo(a)gentoo.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Fixed by SHA1| |b52ff2d69961bd1f3adc7ba386f | |179b12af26481 Status|UNCONFIRMED |RESOLVED --- Comment #1 from Chiitoo <chiitoo(a)gentoo.org> --- Adding to previous description, it seems that moving the window repeatedly (usually ~2-7 times) would make the window stabilise consistently, until re-sized, which restores the weirdness. Having written that, this seems to have been fixed, or at least the behaviour has returned to normal after commit b52ff2d6996 [1]. Thank you! 1. https://gitlab.winehq.org/zfigura/wine/-/commit/b52ff2d69961bd1f3adc7ba386f1... -- 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=57986 Chiitoo <chiitoo(a)gentoo.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|FIXED |--- Status|RESOLVED |UNCONFIRMED --- Comment #2 from Chiitoo <chiitoo(a)gentoo.org> --- Re-unconfirming as this seems to have returned with commit 1dce2661ec9 [1], althought it's possible there is some random factor causing this, it does seem very consistent while testing the seemingly good VS bad commits. 1. https://gitlab.winehq.org/zfigura/wine/-/commit/1dce2661ec9fa2efc21de1292f65... -- 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=57986 --- Comment #3 from Chiitoo <chiitoo(a)gentoo.org> --- Correct URLs for the references, which I somehow initially got from zf's repository, and then kept copying for the rest... 1. https://gitlab.winehq.org/wine/wine/-/commit/cb1c03b926ca01619be02f835f382c1... 2. https://gitlab.winehq.org/wine/wine/-/commit/b52ff2d69961bd1f3adc7ba386f179b... 3. https://gitlab.winehq.org/wine/wine/-/commit/1dce2661ec9fa2efc21de1292f65246... -- 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=57986 Chiitoo <chiitoo(a)gentoo.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Fixed by SHA1|b52ff2d69961bd1f3adc7ba386f |659e3b3e14e45526109870bf0da |179b12af26481 |70d63b10e5641 Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #4 from Chiitoo <chiitoo(a)gentoo.org> --- It seems some confusion here was caused by different behaviour between builds using different GCC versions (and, hopefully, 'ccache'). While it seemed as if the issue was "moving goal posts", I never saw different behaviour on re-running the application on a single same build. After a while I realised I was seeing different behaviour with an older build of Wine release 10.4, which had been built using GCC 14.2.1. After even more bisecting back and forth, and still feeling like something wasn't right with the "goal posts", I started suspecting 'ccache' having an effect as well, which I had meant to disable already a while ago for this (not that it even helps with these CPU/HDD speeds here (building in RAM in addition still seems to give me some gains though, depending on changes of course). I can still see differences between the GCC versions though, so there might be something to investigate on the GCC side as well, but what comes to the Wine part, this issue seems to have been resolved with GCC 15.1.0 at Wine commit 9141dd4d850 [4] (included in release 10.7), and for current GCC 14.2.1_p20250419 (as well as 13.3.1_p20250418) a bit later at Wine commit 659e3b3e14e [5]. Things improved or changed for 14.2.1 earlier at some point already too, but the initial state for the window was still incorrect (looking at the later change, I am quite unsure why 15.1.0 does better without it... but maybe that is for another investigation time). Not sure if it's possible for GCC to use objects from a cache that was populated by a build with a different version of GCC, though I suppose that could explain some of the strange changes in behaviour I was seeing when switching the version and moving between commits again. I also went back to the regression SHA, to make sure the issue starts with both versions the same, and that does seem to be the case (also tested some with GCC 13.3.1_p20250418). In any case, right now at current git master, 09539a3af5f [6], the window behaves as expected regardless of which of the 3 GCC version I build Wine with. Thank you! 4. https://gitlab.winehq.org/wine/wine/-/commit/9141dd4d850210788dcc63838abeca2... 5. https://gitlab.winehq.org/wine/wine/-/commit/659e3b3e14e45526109870bf0da70d6... 6. https://gitlab.winehq.org/wine/wine/-/commit/09539a3af5f806bf319917cafff2b07... -- 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=57986 Alexandre Julliard <julliard(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #5 from Alexandre Julliard <julliard(a)winehq.org> --- Closing bugs fixed in 10.8. -- 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