http://bugs.winehq.org/show_bug.cgi?id=59686 Bug ID: 59686 Summary: Popotan Po!: No text/fonts when using new WoW64 mode (but works using win32) Product: Wine Version: 11.7 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@list.winehq.org Reporter: ms_313b11f8dd030fbf515e3a6beac6ba2243b23eae@lambsauce. de Distribution: --- Created attachment 80788 --> http://bugs.winehq.org/attachment.cgi?id=80788 Wine log files of the configurations tested Running "Popotan Po!" (ぽぽたん Po!) in a new wow64 mode prefix results in no in-game text. Instead, whenever text is supposed to be rendered, wine has 100 % CPU load according to htop for about 40 to 110 seconds, depending on the situation. Text on normal widgets (e.g. menu bar or window title bar) works fine. Host architecture: x86_64 (Arch running Linux 6.19.13) Guest architecture: i386 Tested with the following Wine packages/versions used on Arch (logs attached): - BAD: wow64 prefix with wine 11.7-1 (https://archlinux.org/packages/extra/x86_64/wine/) - BAD: wow64 prefix with wine-staging 11.7-1 (https://archlinux.org/packages/extra/x86_64/wine-staging/) - GOOD: win32 prefix with wine32 11.7-1 (https://aur.archlinux.org/packages/wine32) Further observations: - The problem does not appear in a win32 prefix (and it never did for the last 10 years or so). - Whether you use wine or wine-staging makes no apparent difference. Steps to reproduce: 1. Create a new wine prefix using winecfg and make wine emulate an 800x600 desktop. 2. Use the appropriate locale (otherwise, all dialogs only show mojibake): export LANG="ja_JP.eucjp" export LC_ALL="ja_JP.eucjp" 3. Install the game using the defaults suggested by the installer. 4. Launch the game. For this issue, there seems to be no difference between "tsuujouban" (通常版) and "koukinouban" (高機能版). Choose "tsuujouban". 5. At that point, if the problem occurs, you might get the 100 % CPU load mentioned above. Also, the whole wine dektop window freezes. Be patient. 6. The intro video starts. (In my case, playback only works in the wow64 prefixes but not in the win32 prefix. Instead, the screen appears all-black or all-white. Ignore that issue.) Use ESC to skip the intro. 7. In the main menu, choose "Config" (コンフィグ). 8. In the top-right corner, you can choose a "Font" (フォント). The name of the font is rendered between the two arrows using itself for demonstration purposes. Due to the issue at hand, the space between the two arrows appears empty as if no font is available. 9. Go back (ゲームへ戻る). 10. Now, back in the main menu, choose "tsuzuki kara" (つづきから). 11. Again, if the problem occurs, you might get 100 % CPU load and a frozen window. Be patient. 12. If everything works normally, saved game states should be listed. Even unused slots show some text like "----/--/-- --:--" (without quotes). However, due to the issue at hand, all lines appear empty (except for the numbers to the left which are, apparently, rendered using bitmaps, just like everything else so far). 13. Go back (タイトルへ). 14. Now, again back in the main menu, choose "hajime kara" (はじめから). The actual game starts. 15. Normally, a text box at the lower bottom appears, along with text in it as the story progresses. However, if the problem occurs, you might get 100 % CPU load and freezes along the way. Be patient whenever that happens. 16. A star symbol appears at the end of the text in the text box. The exact position of the star seems to be fixed. That is, the position seems to be independent of the glyphs used to render the text. As a result, if the problem occurs, the star seems to appear at various positions within the box, with no actually visible text ahead of it but close to where the text *should* have ended. Attempted workarounds: - Using "winetricks corefonts" or "winetricks allfonts" did not help. - Running "fc-cache -fv" also did not help. - Assuming it might be an encoding or locale problem, I tried *really hard* to make the whole thing run with locale ja_JP.UTF-8, with the result that it actually *did* run with that locale somehow. However, the issue persisted. - Using that same experimental prefix, I tried running it with locale ja_JP.UTF-8 again, but this time with "Windows Version" set to "Windows XP" in winecfg, to no avail. - When I tried to make it run with locale en_US.UTF-8, it crashed before I got to the intro. (This is not too surprising.) Further investigation and speculation: - The game seems to only list fonts it considers usable, so probably only fonts that are compatible enough for Japanese. - The config is stored in the registry, and by default (at least in my case), the installation in the win32 prefix as well as the installation in the wow64 prefix both use "FontFace"="ＭＳ ゴシック" according to regedit. Thus, despite already knowing the name of a font face to use, only the win32 prefix can make sense of it while the wow64 prefix cannot. - Even copying a working non-default value like "さざなみゴシック" from the registry of the win32 prefix and then pasting it as the new value into the wow64 registry did not help. - You can actually switch between different fonts using the arrows in the config screen mentioned above, even if you do not see it happening in the wow64 prefix. For example, after switching randomly and then closing the game, the corresponding value in the registry now reads "AR PL UMing TW MBE", for example. The very same font can be chosen normally in the win32 prefix as well. This indicates that the game in the wow64 version knows of the available fonts it considers usable, it just fails to render text properly using them. - For some unknown reason, though, the config screen opens quickly while everything else that normally has some text in it just burns CPU and displays no text at all. - Maybe it has something to do with Unicode stuff? -- 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.