http://bugs.winehq.org/show_bug.cgi?id=27293
dk developer@gaminglounge.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |REOPENED Version|1.3.20 |1.7.13 Resolution|FIXED |---
--- Comment #14 from dk developer@gaminglounge.com --- Just compiled Wine 1.7.13 today and I was really surprised that I am no longer affected by bug #12964. (this is great news) HOWEVER I am still affected by this bug (#27293) ((the typing issue)).
I've attached the terminal output above and as you can see it's almost entirely IME issues.
Just to make this clear - for me the game no longer crashes with bug #12964 making this bug the last blocking issue. I can actually get into game now and play with an existing character on the server. I cannot name my character, create a new game, or chat by typing.
Test results are here: http://appdb.winehq.org/objectManager.php?sClass=version&iId=24454 (I've also uploaded some new screenshots at points where you cannot continue without the ability to type)
This was tested with the official 1.24.3 client. We actually have three different versions of Phantasy Star Online: Blue Burst on the appdb here:
http://appdb.winehq.org/objectManager.php?sClass=application&iId=6505
Why do we have three versions of the same game? Because the Schthack and Tethealla clients have been individually patched by different people. I'm not the maintainer for the Schthack version and therefore I don't follow it's development history much but I do know for a fact that the Tethealla client had a patch applied to it to fix typing issues that appeared with the release of Windows 7. The 1.24.3 client exists as our reference client - it's exe is unmodified and therefore immune to any side effects that may have been caused by the (unofficial) patches in the other versions.
This bug (#27293) affected both the 1.24.3 and Tethealla clients in the past (and probably the Schthack version as well at one point). I see from the most recent comments that this issue appeared to be fixed for some of you - but it's not entirely clear which versions everyone was using.
In any case, on 1.24.3 this bug still exists. The log is filled with 'fixme' messages (IMM/IME) which implies that this bug still exists (or had been fixed but now is back).
I think it would be helpful to know which versions of the client everyone (that replied it was fixed) was using if that assessment still holds true with the latest Wine releases.