http://bugs.winehq.org/show_bug.cgi?id=27293
Summary: PSO:BB - Cannot type a character name during character creation Product: Wine Version: 1.3.20 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: dev@gaminglounge.com
Created an attachment (id=34903) --> (http://bugs.winehq.org/attachment.cgi?id=34903) Wine 1.3.20 terminal ouput of issue when typing
To join the server in Phantasy Star Online: Blue Burst the user must first register their UserID at the main screen by typing their username and password. (typing at this point works) Once entered the user can either select an existing character or create a new one.
When creating a new character - the last step is to give the character a name. At this point typing suddenly stops working - no text appears and the console is filled with this line with every keypress:
fixme:imm:ImmGetDescriptionW (0x4090409, 0xad9460, 255): semi stub
This is problem - if only for the fact that once started you can't really exit out of the character creation process without forceably terminating the application. We really need to be able to type the name to exit this point in the game.
If new users can't create a character they won't be able to help in troubleshooting bug (#12964) which is needed to get in-game.
http://bugs.winehq.org/show_bug.cgi?id=27293
--- Comment #1 from dk dev@gaminglounge.com 2011-05-27 05:00:16 CDT --- Link to ImmGetDescription function on MSDN: http://msdn.microsoft.com/en-us/library/dd318562(v=VS.85).aspx
http://bugs.winehq.org/show_bug.cgi?id=27293
--- Comment #2 from dk dev@gaminglounge.com 2011-05-27 05:15:52 CDT --- // File name: C:\Program Files\SEGA\PHANTASY STAR ONLINE Blue Burst\PsoBB.exe // Created : 26.05.2011 07:11 // Type : Imports
function ImmSetCandidateWindow(hImc: HIMC; lpCandidate: PCANDIDATEFORM): Boolean; stdcall; external 'imm32.dll' name 'ImmSetCandidateWindow' index 89;
function ImmGetContext(hWnd: HWND): HIMC; stdcall; external 'imm32.dll' name 'ImmGetContext' index 32;
function ImmAssociateContext(hWnd: HWND; hImc: HIMC): HIMC; stdcall; external 'imm32.dll' name 'ImmAssociateContext' index 2;
function ImmNotifyIME(hImc: HIMC; dwAction, dwIndex, dwValue: DWORD): Boolean; stdcall; external 'imm32.dll' name 'ImmNotifyIME' index 73;
function ImmSetCompositionWindow(hImc: HIMC; lpCompForm: PCOMPOSITIONFORM): Boolean; stdcall; external 'imm32.dll' name 'ImmSetCompositionWindow' index 94;
function ImmSetConversionStatus(hImc: HIMC; Conversion, Sentence: DWORD): Boolean; stdcall; external 'imm32.dll' name 'ImmSetConversionStatus' index 95;
function ImmGetConversionStatus(hImc: HIMC; var Conversion, Sentence: DWORD): Boolean; stdcall; external 'imm32.dll' name 'ImmGetConversionStatus' index 35;
function ImmGetOpenStatus(hImc: HIMC): Boolean; stdcall; external 'imm32.dll' name 'ImmGetOpenStatus' index 50;
function ImmGetCompositionStringW(hImc: HIMC; dWord1: DWORD; lpBuf: pointer; dwBufLen: DWORD): Longint; stdcall; external 'imm32.dll' name 'ImmGetCompositionStringW' index 30;
function ImmGetDescriptionW(hKl: HKL; PWideChar: PWideChar; uBufLen: UINT): UINT; stdcall; external 'imm32.dll' name 'ImmGetDescriptionW' index 38;
function ImmReleaseContext(hWnd: HWND; hImc: HIMC): Boolean; stdcall; external 'imm32.dll' name 'ImmReleaseContext' index 81;
function ImmSetOpenStatus(hImc: HIMC; fOpen: Boolean): Boolean; stdcall; external 'imm32.dll' name 'ImmSetOpenStatus' index 97;
function ImmGetDefaultIMEWnd(hWnd: HWND): HWND; stdcall; external 'imm32.dll' name 'ImmGetDefaultIMEWnd' index 36;
// ImmDisableIME Information not available
function ImmIsIME(hKl: HKL): Boolean; stdcall; external 'imm32.dll' name 'ImmIsIME' index 64;
function ImmGetCandidateListW(hImc: HIMC; deIndex: DWORD; lpCandidateList: PCANDIDATELIST; dwBufLen: DWORD): DWORD; stdcall; external 'imm32.dll' name 'ImmGetCandidateListW' index 25;
http://bugs.winehq.org/show_bug.cgi?id=27293
dk dev@gaminglounge.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |dev@gaminglounge.com
http://bugs.winehq.org/show_bug.cgi?id=27293
Luke Bratch l_bratch@yahoo.co.uk changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |l_bratch@yahoo.co.uk
http://bugs.winehq.org/show_bug.cgi?id=27293
--- Comment #3 from dk dev@gaminglounge.com 2011-05-29 20:48:54 CDT --- Created an attachment (id=34958) --> (http://bugs.winehq.org/attachment.cgi?id=34958) Wine 1.3.21 terminal ouput of issue when typing
Same issue is still present in Wine 1.3.21
http://bugs.winehq.org/show_bug.cgi?id=27293
Knightlain pastorrub@msn.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever Confirmed|0 |1
--- Comment #4 from Knightlain pastorrub@msn.com 2011-09-05 20:24:12 CDT --- *** This bug has been confirmed by popular vote. ***
http://bugs.winehq.org/show_bug.cgi?id=27293
Knightlain pastorrub@msn.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |pastorrub@msn.com
http://bugs.winehq.org/show_bug.cgi?id=27293
Alam Arias Alam_GBC@yahoo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |Alam_GBC@yahoo.com
http://bugs.winehq.org/show_bug.cgi?id=27293
dk dev@gaminglounge.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Version|1.3.20 |1.3.29 See Also| |http://bugs.winehq.org/show | |_bug.cgi?id=22805
http://bugs.winehq.org/show_bug.cgi?id=27293
dk dev@gaminglounge.com changed:
What |Removed |Added ---------------------------------------------------------------------------- See Also| |http://bugs.winehq.org/show | |_bug.cgi?id=17302
http://bugs.winehq.org/show_bug.cgi?id=27293
dk dev@gaminglounge.com changed:
What |Removed |Added ---------------------------------------------------------------------------- See Also| |http://bugs.winehq.org/show | |_bug.cgi?id=12975
http://bugs.winehq.org/show_bug.cgi?id=27293
dk dev@gaminglounge.com changed:
What |Removed |Added ---------------------------------------------------------------------------- See Also| |http://bugs.winehq.org/show | |_bug.cgi?id=5163
http://bugs.winehq.org/show_bug.cgi?id=27293
dk dev@gaminglounge.com changed:
What |Removed |Added ---------------------------------------------------------------------------- See Also| |http://bugs.winehq.org/show | |_bug.cgi?id=27716
http://bugs.winehq.org/show_bug.cgi?id=27293
dk dev@gaminglounge.com changed:
What |Removed |Added ---------------------------------------------------------------------------- See Also| |http://bugs.winehq.org/show | |_bug.cgi?id=17667
http://bugs.winehq.org/show_bug.cgi?id=27293
dk dev@gaminglounge.com changed:
What |Removed |Added ---------------------------------------------------------------------------- See Also| |http://bugs.winehq.org/show | |_bug.cgi?id=28423
http://bugs.winehq.org/show_bug.cgi?id=27293
dk dev@gaminglounge.com changed:
What |Removed |Added ---------------------------------------------------------------------------- See Also| |http://bugs.winehq.org/show | |_bug.cgi?id=4781
http://bugs.winehq.org/show_bug.cgi?id=27293
dk dev@gaminglounge.com changed:
What |Removed |Added ---------------------------------------------------------------------------- See Also| |http://bugs.winehq.org/show | |_bug.cgi?id=19593
http://bugs.winehq.org/show_bug.cgi?id=27293
dk dev@gaminglounge.com changed:
What |Removed |Added ---------------------------------------------------------------------------- See Also| |http://bugs.winehq.org/show | |_bug.cgi?id=18415
http://bugs.winehq.org/show_bug.cgi?id=27293
dk dev@gaminglounge.com changed:
What |Removed |Added ---------------------------------------------------------------------------- See Also| |http://bugs.winehq.org/show | |_bug.cgi?id=15963
http://bugs.winehq.org/show_bug.cgi?id=27293
dk dev@gaminglounge.com changed:
What |Removed |Added ---------------------------------------------------------------------------- See Also| |http://bugs.winehq.org/show | |_bug.cgi?id=14900
http://bugs.winehq.org/show_bug.cgi?id=27293
dk dev@gaminglounge.com changed:
What |Removed |Added ---------------------------------------------------------------------------- See Also| |http://bugs.winehq.org/show | |_bug.cgi?id=10636
http://bugs.winehq.org/show_bug.cgi?id=27293
dk dev@gaminglounge.com changed:
What |Removed |Added ---------------------------------------------------------------------------- See Also| |http://bugs.winehq.org/show | |_bug.cgi?id=26744
http://bugs.winehq.org/show_bug.cgi?id=27293
dk dev@gaminglounge.com changed:
What |Removed |Added ---------------------------------------------------------------------------- See Also| |http://bugs.winehq.org/show | |_bug.cgi?id=23696
http://bugs.winehq.org/show_bug.cgi?id=27293
dk dev@gaminglounge.com changed:
What |Removed |Added ---------------------------------------------------------------------------- See Also| |http://bugs.winehq.org/show | |_bug.cgi?id=16035
http://bugs.winehq.org/show_bug.cgi?id=27293
dk dev@gaminglounge.com changed:
What |Removed |Added ---------------------------------------------------------------------------- See Also| |http://bugs.winehq.org/show | |_bug.cgi?id=25786
http://bugs.winehq.org/show_bug.cgi?id=27293
dk dev@gaminglounge.com changed:
What |Removed |Added ---------------------------------------------------------------------------- See Also| |http://bugs.winehq.org/show | |_bug.cgi?id=8034
http://bugs.winehq.org/show_bug.cgi?id=27293
--- Comment #5 from dk dev@gaminglounge.com 2011-10-04 17:59:22 CDT --- Created attachment 36717 --> http://bugs.winehq.org/attachment.cgi?id=36717 Wine 1.3.29 terminal ouput of issue when typing
http://bugs.winehq.org/show_bug.cgi?id=27293
--- Comment #6 from dk dev@gaminglounge.com 2011-10-04 18:15:00 CDT --- Added log for Wine 1.3.29 as well as links to other bugs that call the same functions.
Also, there's a relevant thread in the forums that may be helpful:
http://forum.winehq.org/viewtopic.php?p=67658
http://bugs.winehq.org/show_bug.cgi?id=27293
Dmitry Timoshkov dmitry@baikal.ru changed:
What |Removed |Added ---------------------------------------------------------------------------- Version|1.3.29 |1.3.20 See Also|http://bugs.winehq.org/show | |_bug.cgi?id=10636, | |http://bugs.winehq.org/show | |_bug.cgi?id=12975, | |http://bugs.winehq.org/show | |_bug.cgi?id=14900, | |http://bugs.winehq.org/show | |_bug.cgi?id=15963, | |http://bugs.winehq.org/show | |_bug.cgi?id=16035 | See Also|http://bugs.winehq.org/show | |_bug.cgi?id=17302, | |http://bugs.winehq.org/show | |_bug.cgi?id=17667, | |http://bugs.winehq.org/show | |_bug.cgi?id=18415, | |http://bugs.winehq.org/show | |_bug.cgi?id=19593, | |http://bugs.winehq.org/show | |_bug.cgi?id=22805 | See Also|http://bugs.winehq.org/show | |_bug.cgi?id=23696, | |http://bugs.winehq.org/show | |_bug.cgi?id=25786, | |http://bugs.winehq.org/show | |_bug.cgi?id=26744, | |http://bugs.winehq.org/show | |_bug.cgi?id=27716, | |http://bugs.winehq.org/show | |_bug.cgi?id=28423 | See Also|http://bugs.winehq.org/show | |_bug.cgi?id=4781, | |http://bugs.winehq.org/show | |_bug.cgi?id=5163, | |http://bugs.winehq.org/show | |_bug.cgi?id=8034 |
http://bugs.winehq.org/show_bug.cgi?id=27293
--- Comment #7 from dk dev@gaminglounge.com 2011-10-05 00:10:58 CDT --- @dmitry, why did you remove the bug links that I added? The same imm32 deficiencies are also present in those applications as well. Without linking them we have no idea of what the scope is.
http://bugs.winehq.org/show_bug.cgi?id=27293
--- Comment #8 from Dmitry Timoshkov dmitry@baikal.ru 2011-10-05 00:18:22 CDT --- (In reply to comment #7)
@dmitry, why did you remove the bug links that I added? The same imm32 deficiencies are also present in those applications as well. Without linking them we have no idea of what the scope is.
Those links are not helpful at all.
http://bugs.winehq.org/show_bug.cgi?id=27293
JHaleIT jhaleit@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jhaleit@gmail.com
--- Comment #9 from JHaleIT jhaleit@gmail.com 2012-02-28 09:29:01 CST --- The typing bug is no longer an issue. It works completely fine for me.
http://bugs.winehq.org/show_bug.cgi?id=27293
Jerome Leclanche adys.wh@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |adys.wh@gmail.com Resolution| |FIXED
--- Comment #10 from Jerome Leclanche adys.wh@gmail.com 2012-02-28 09:52:06 CST --- Fixed. Please file a new bug if there are remaining issues.
http://bugs.winehq.org/show_bug.cgi?id=27293
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #11 from Alexandre Julliard julliard@winehq.org 2012-03-02 13:02:10 CST --- Closing bugs fixed in 1.4-rc6.
http://bugs.winehq.org/show_bug.cgi?id=27293
landeel cleberdemattoscasali-wine@yahoo.com.br changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |cleberdemattoscasali-wine@y | |ahoo.com.br
--- Comment #12 from landeel cleberdemattoscasali-wine@yahoo.com.br 2012-03-04 11:27:36 CST --- Confirmed: fixed.
http://bugs.winehq.org/show_bug.cgi?id=27293
--- Comment #13 from dk developer@gaminglounge.com --- Created attachment 47733 --> http://bugs.winehq.org/attachment.cgi?id=47733 Wine 1.7.13 terminal output of typing issue
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.
http://bugs.winehq.org/show_bug.cgi?id=27293
dk developer@gaminglounge.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|PSO:BB - Cannot type a |PSO:BB - Cannot type a |character name during |character name, create a |character creation |party name, or chat
http://bugs.winehq.org/show_bug.cgi?id=27293
--- Comment #15 from JHaleIT jhaleit@gmail.com --- (In reply to dk from comment #14)
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.
Sorry to say, but bug #12964 is not fixed. you can see here that it still crashes: http://cl.ly/image/092x1o1A382K
http://bugs.winehq.org/show_bug.cgi?id=27293
--- Comment #16 from dk developer@gaminglounge.com --- Created attachment 47736 --> http://bugs.winehq.org/attachment.cgi?id=47736 Wine 1.7.13 terminal output of typing issue (Tethealla)
Terminal output for 1.25.10 (Tethealla).
Same results as 1.24.3. The typing issue prevents me from naming a character (and finishing character creation). If I choose a pre-existing character I can select a ship and get into the lobby and run around, symbol chat, etc.. I cannot 'normal' chat or name a party (and therefore create a game).
http://bugs.winehq.org/show_bug.cgi?id=27293
Brian bkohler36@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |bkohler36@gmail.com
--- Comment #17 from Brian bkohler36@gmail.com --- I can confirm is that the bug persists in the executables not patched for Windows 7, and I'm not sure it was ever fixed for those. I've tested in wine 1.7.13 using the Teth12510 executables(patched and unpatched) and the latest Schthack one(patched, I believe). Regarding the unpatched Teth executables, this might be useful: I was able to circunvent the bug by inputting text/character names using ibus-anthy(japanese input method), even names with japanese characters worked flawlessly that way. For the patched executables I was able to input _only_ without ibus-anthy, i.e. I wasn't able to type in japanese.
Now for a short story and an hypothesis on the issue: Recently I had the chance to test the Teth executables on a Windows 7 machine and the bug is there too. For the unpatched executable, in the character naming screen there was some text which apparently indicated which character set is being used("半 かな あ"(half(-width) kana a). Here's a screenshot, the string I mentioned is visible in the lower left corner: http://i.imgur.com/YkBGCz5.jpg . Of note is that that string doesn't ever appear when running under WINE. Anyway, upon pressing the Windows shortcut to change keyboard layouts the text disappears and I can type my character name in english just fine, I think someone reported this already on the AppDB comments. Now for the patched executable: the japanese text shown in the character naming screen here is "半 英数 _A" (Half(-width) Alphanumeric _A"), I can type freely, pressing the key combination causes the text to disappear but I can still type. By now things should be more or less clear: the game was programmed by japanese people and thus supported both western and japanese keyboards and the extra keys they have to change input modes between half/full width kana, thumb-shift, alphanumeric and so-on. Windows Vista probably changed something with how keyboards/IMEs are handled and the game defaulted to kana input only and most western users had no idea how to deal with that, thus some fans hacked the game executables to default to alphanumeric input and order is restored. WINE just happened to handle whatever the problem's at more like Vista/7/8 than 98/2000/XP.
So I think if my workarounds can be reproduced the only thing left for this bug is the current character set not being displayed. It also remains to be seen if users with a proper japanese keyboard are able to change the active character set and type in japanese using patched clients.
http://bugs.winehq.org/show_bug.cgi?id=27293
--- Comment #18 from dk developer@gaminglounge.com --- Interesting. Please correct me if any of this is wrong. There might be something of value in this although I still believe that Wine's IMM/IME implementation just isn't finished yet and any other solution is really just a workaround.
This is written in the context of the 1.24.3 (US) client for reasons explained near the end.
When I run 'wine winecfg' (with 1.7.13) the operating system it defaults to XP, and not Windows 7 (or higher). For me, this is preferable as the last time the native 1.24.3 (US) client worked without issues was on XP. More on that in a second.
On XP the game activated 'Advanced Text Services' in Windows, meaning that (if your native language was English and you were in the US) ((and never had a need to type in another language)) odds are you never saw the language bar. (Installing other software like Office might also activate it - but from a fresh install of EN Windows XP 32bit (or even 64-bit) Advanced Text Services was never active upon reaching the desktop.
PSOBB's installation did activate it and sometimes (it's not clear under what circumstances) people were having problems with this. (It was pretty easy to hit the wrong keys and have the language bar change your language and when that happened (and if you were unfamiliar with what was goin on) you literally might be stuck. When these people posted on the US support forums you were encouraged to 'disable Advanced Text Services'. (I think those forums are still up but a google search should bring up this complaint a lot)
It's possible that the support team didn't want to have to explain how to use a Windows feature if the people never used it before and (for English only speakers) would never have a need. (PSO & PSOBB both provided basic translations and symbol chat to communicate with speakers in another language - in fact this was one of the game's pioneering (pun intended) features.)
So on XP with 1.24.3 (US) you could just disable 'Advanced Text Services' and the problem was solved. If you spoke multiple languages (such as English & Japanese) you were probably already comfortable using 'Advanced Text Services' and the game also worked. Everyone was happy. :)
When Windows Vista and 7 was released those users (that disabled 'Advanced Text Services') started to encounter problems. From what I gather (from the Windows 7 forums - I skipped Vista personally) it's because Microsoft removed the ability to disable 'Advanced Text Services'. Also 'Advanced Text Services' was renamed to 'Text Services and Input Languages'.
At this point it gets murky because US game support (for PSOBB) ended on March 31st, 2008. Windows 7 was released to manufacturing a year later (July 22, 2009). So basically the 1.24.3 (US) client never officially supported Windows 7 (or higher)
Even so there was still a workaround to play the 1.24.3 (US) game client on Windows 7 if you followed these instructions which I believe were used on the support forums for Vista:
- open Control Panel - under 'Clock, Language and Region' click 'Change keyboards or other input methods' - click the 'Change Keyboards...' button - click the 'Add' button and a 'Add Input Language' window will open - find 'Japanese (Japan)' in the list and check the box next to 'Microsoft IME' - click the 'Ok' button - under 'Japanese (Japan)' select 'Microsoft IME' and click the properties button - in the 'General' tab set 'Space' and 'Numeric pad' to 'Always Half-Width'. - under the 'Mixed Japanese/English' tab check the box next to 'Allow conversion in Alphanumeric input mode' - (if you get a message stating '[Editing:Don't use direct input mode] will be OFF. Continue?' click the 'Yes' button - go back to the 'General' tab. - set 'Default Input Mode' to 'Half-Width Alphanumeric' - click the 'Apply' button - (you can change the key to enable this from the 'Advanced Key Settings')
It's important to note that those settings are in Windows and not the game. (and should be something that Wine would support) With these changes you could type on Windows 7 (and presumably Vista and 8 although I haven't tested that).
Meanwhile.. while US users were figuring this out The Japanese version of the client was still being updated. Sometime before December 27, 2010 (which was when the Japanese game support closed down for good) the client was updated to support Windows 7. Unfortunately I don't know which version in particular did this. With that update you no longer needed to use the above workaround (if you were playing in the US on Vista/7).
The Schthack and Tethealla versions of the game client are both based off of the Japanese client. Schthack's version remains a closed-source project so there's not much information about what they've done. Sodaboy however had a ton of great collaboration on his forums. I forget what version Sodaboy started with but eventually someone helped him with the information to patch the exe to support Windows Vista and 7. Because of this my guess is that he must have been using a client that was < the Japanese client which had native Windows 7 support (whatever version that was). Unfortunately (and this is a huge loss) we no longer have access to his forums. All of the necessary files are still publicly archived on pioneer2.net.
So (in my opinion) I would be cautious in trying to solve this bug with the Schthack or Tethealla clients for the following reason:
- we don't know what exactly was changed in the Schthack or Tethealla clients - we do know that the executables were unpacked - the patch could have been injected or it might simply have been hex edited - because of these reasons we can't be sure if their patching process has created side effects - because the patch is directly related to this issue it cannot be trusted
This is the reason I believe we should solve this issue by working with the 1.24.3 (US) client. (It *could* also be solved with the native JP client with Windows 7 support if it could be identified and the files found)
At least with the 1.24.3 (US) client we can be certain that the program runs as originally intended (on XP - which Wine supports as default) and (with the 'Text Services and Input Languages' workaround above) on Windows Vista/7.
This brings me back to my original conclusion that all of those 'fixme:imm' messages in the logs really do need to be addressed for this game to be fully functional without using the original Windows dlls.
Don't get me wrong - after six years of waiting I'd love to see this game running even with hacks on Linux but I think the end goal really should be proper IMM/IME support in Wine. (if possible of course)
Most of the popular servers that are running today won't accept the US client when it tries to connect therefore making it difficult to troubleshoot this bug. (notes: I have not tried the Sylverant server because I'm having trouble compiling it on Windows)
Fuzziqer's khyller (and later Aeon/newserv) projects are capable however and I suggest using them to test. It's not complicated to setup up but there are a few steps. Everything has been documented here if you're interested:
https://sites.google.com/site/winepso/
http://bugs.winehq.org/show_bug.cgi?id=27293
--- Comment #19 from JHaleIT jhaleit@gmail.com --- Well from what I hear is that Schtack's hack has some sort of custom game cheat checker in it. So I'm not sure if that is causing the problem. All the horrid stories I hear about Schack's servers makes me not want to be in there any more. I'll try your method, but where could I get the files to test it out?
http://bugs.winehq.org/show_bug.cgi?id=27293
--- Comment #20 from JHaleIT jhaleit@gmail.com --- Ok I got the psobb without any patches. Just need the game guard patch and whatever else to test this.
https://bugs.winehq.org/show_bug.cgi?id=27293
--- Comment #21 from Austin English austinenglish@gmail.com --- This is your friendly reminder that there has been no bug activity for over a year. Is this still an issue in current (1.7.51 or newer) wine?
https://bugs.winehq.org/show_bug.cgi?id=27293
winetest@luukku.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |winetest@luukku.com
--- Comment #22 from winetest@luukku.com --- Can you retest this bug?
https://bugs.winehq.org/show_bug.cgi?id=27293
--- Comment #23 from dk developer@gaminglounge.com --- Retested on Wine 2.0 under Ubuntu GNOME 16.04 64 bit with the following two clients:
- 1.24.3 (official US client) - 1.25.10 (unofficial patched Teth client)
The issue still exists and I believe performance is affected by the constant spamming of the ImmGetDescriptionW line with every keypress (output was identical between the versions tested):
-snip- fixme:imm:ImeHandleNotify WM_IME_NOTIFY:IMN_SETCOMPOSITIONWINDOW fixme:imm:NotifyIME IMC_SETCANDIDATEPOS fixme:imm:ImeHandleNotify WM_IME_NOTIFY:IMN_SETCANDIDATEPOS fixme:d3d:wined3d_swapchain_set_gamma_ramp Ignoring flags 0x1. fixme:imm:ImmGetDescriptionW (0x4090409, 0xacf3e0, 255): semi stub fixme:imm:ImmGetDescriptionW (0x4090409, 0xacf3e0, 255): semi stub fixme:imm:ImmGetDescriptionW (0x4090409, 0xacf3e0, 255): semi stub .. fixme:imm:ImmGetOpenStatus (0x1462b8): semi-stub .. fixme:imm:ImmReleaseContext (0x3006a, 0x1462b8): stub -snip-
https://bugs.winehq.org/show_bug.cgi?id=27293
nolrinale myriabelmonte@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |myriabelmonte@gmail.com
--- Comment #24 from nolrinale myriabelmonte@gmail.com --- Hello,
I wanted to give a small update several years later regarding this issue, testing with wine-8.19 (Staging)
It is possible to continue playing PSOBB with the new open source emulator server "newserv" available on GitHub which supports this game version.
Testing with the Tethealla Client which is actually the original Japanese PSOBB client Ver.1.25.13 and restoring the IME functionality removing a patch that was added to it afterwards it is possible to type in Japanese and English in the game using IME under Windows 10 as intended.
On wine, is not possible to type in any field which accepts Japanese input, specific fields like this are the Character Creation fields, Party Name fields, Team Name Fields.
However fields which accept only ASCII character such as the Login info at the title screen or the password setting for a party you will be able to type without any issue.
It looks like PSOBB on wine cannot really detect IME at all (i'm using Mozc for these tests)
So to play PSOBB on linux using wine it is recommended to maintain the direct text patch by modifying an unpacked version fo the game exe (psobb.exe) via hex editor Replace A8838F with 9CC38E for only english typing
This way it will allow you to type in english and have a playable game.
PSOBB currently is working on wine without issues, however any texture that moves around is directly not being shown such as scrolling terminals, water effects, ripple effects, etc. To mitigate these bugs a little make sure to run the game with graphic settings set to Mid-End.