https://bugs.winehq.org/show_bug.cgi?id=49423 zepar <stefanfunk1998(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |stefanfunk1998(a)gmail.com --- Comment #1 from zepar <stefanfunk1998(a)gmail.com> --- can confirm that key inputs dont work right for me, and my mouse is not getting captured in fullscreen mode in Final Fantasy XIV with any wine version above 4.16 -- 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=49423 --- Comment #3 from Bloody Iron <bloodyiron(a)lanified.com> --- (In reply to Zebediah Figura from comment #2) How does testing with WINE 5.7 not constitute a rough regression test? I tested with WINE 5.7 today and confirmed the issue. I myself am really not in a position to compile WINE from source and test very deeply for this. -- 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=49423 --- Comment #5 from Bloody Iron <bloodyiron(a)lanified.com> --- (In reply to Zebediah Figura from comment #4) Ahh okay, well hopefully someone more versed in this process can assist with this. I'm still ultra green when it comes to compiling WINE from source, and getting all the other manual steps in-order. I could eventually figure it out, but I'm afraid that's not in the cards right now. Considering how consistent the issue is, I suspect this impacts a lot of people. Maybe it'll get some attention soon from someone who can handle this :D -- 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=49423 Anya <animegirl(a)stronzi.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |animegirl(a)stronzi.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=49423 joaopa <jeremielapuree(a)yahoo.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree(a)yahoo.fr --- Comment #7 from joaopa <jeremielapuree(a)yahoo.fr> --- Regression test is fast. compilations are requested to do a regression test. -- 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=49423 --- Comment #9 from Bloody Iron <bloodyiron(a)lanified.com> --- (In reply to joaopa from comment #7) While my two original samples are between 4.16 and 5.7, the issue is also observed in much earlier versions, namely, 4.17 and 4.20. I personally have seen it in 4.20, and other people I have talked to reported the issue observed in 4.17. So we can limit the range there. As for age, you don't need to be 20 to observe this issue. I'm much older than that, and ca observe it. I agree that better methods need to be developed to adapt to the growing Linux userbase. Either way, this is a very easily reproducible issue. -- 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=49423 --- Comment #11 from Sveinar Søpler <cybermax(a)dexter.no> --- (In reply to Zebediah Figura from comment #10) Well, since this is staging, it is not ONLY wine commits that has to be bisected. Lets say it is 200 commits between wine-deve-4.16 -> 4.17 (to narrow it down). I know 4.16 = "good", and 4.17 = "Bad". My first bisect would then be 4.16+100 (half right?). Thats fine, exept i might not be able to apply staging at that point. Staging does not get rebased on a "per commit" basis in case of breakage, but sometimes quite a few commits later. So lets say the rebased "staging" is then 4.16+132. Fine, that is also "bad". Next bisec would then be 4.16+66. Lets say once again i am unable to apply staging, but have to apply to eg. 4.16+49. This is "good". Oki.. then i might end up unable to apply staging AT ALL on any of the commits between 4.16+49 -> 4.16+132 I cant see me applying staging to 4.16 and the merging 4.16+100 either, as that is 99% sure to fail, not to mention having to keep tabs on what patchsets gets added/removed/disabled/enabled inbetween those commits. I know it might not be exactly like this, but i have done tries before, and have ended up with a commit range not likely to be accurate enough for any devs to bother. Sorry if i have missunderstood the whole consept tho, but bisecting "staging" when you do not know if it is a staging patch or a wine commit that is the culprit is a bit over medium hard for "regular folks" imo. I know it might be that wine-4.16 only needs 2-3 patchsets to work with Battle.net/WoW, but i do not know the minimal patchset needed. I am willing to try if someone know the absolute minimum patchset tho, so it is way less to fiddle with. (Verified one at that, not "it should probably possible work with only X and Y") I do understand... no problem. It is just not that easy ref. my attempt to describe the problem above. Another thing to worsen this problem is that WoW is NOT playable with WineD3D AT ALL (nope.. having 4-5 fps is NOT playable). So you would need DXVK to get this working, and recent DXVK might need recent wine and/or vulkan patches to work properly too. Sorry, i do understand your problem, but hopefully you also understand mine :) That is why i asked if there was something that could be logged. Maybe a overly amount of "key-press-buffer-overrun" or whatever that MAY point in a certain direction :) -- 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=49423 --- Comment #13 from joaopa <jeremielapuree(a)yahoo.fr> --- Does the bug still occur with plain wine-7.0-rc5? -- 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=49423 --- Comment #15 from Sveinar Søpler <cybermax(a)dexter.no> --- (In reply to Marco Kretz from comment #14) It might not be that big a difference between X vs XWayland, as i don't think wine is Wayland compatible yet, and would need XWayland to work. It might not be THAT DE-agnostic then. Have you experimented with winecfg and "Capture mouse" option, aswell as "Virtual Desktop" settings to see if it makes any difference? A completely dead input should be possible to log, but "general latency" is a bit harder. -- 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=49423 --- Comment #17 from Marco Kretz <mk(a)marco-kretz.de> --- 3 hours of raiding and not a single dead input. So yes, "Capture mouse in fullscreen applications" within winecfg works! I would be really interested in why? Is there an explaination? -- 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=49423 --- Comment #19 from Ken Sharp <imwellcushtymelike(a)gmail.com> --- Does this still occur in Wine 9.8 or later? -- 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.