![]() Hopefully the solutions described in this page won't be needed anymore in Install then transfer them to your Steam Deck.Īlso SteamOS 3.5 is apparently going to include multiple locales, so Sorry, something went commented on this gist.Ĭan be used to generate the locale files for any language on an Arch Linux game title, what symptoms of "not working" you're getting, perhaps even some screenshots would be helpful to help you). exe outside of Steam.)Ĭan't help much more than that without details (eg. ![]() Steam store games may work too–haven't tried as I don't have any that require a Japanese locale–but it definitely won't work for launching. (Also the script provided here is only for launching non-Steam games within Steam – both in Desktop and the Deck's Game mode. This creates a file named steam-GAMEID.log in the home folder.ĭon't forget to enable Proton in the game's Properties in Steam > Compatibility either. PROTON_LOG=1 WINEDEBUG=+file,+nls,+msgbox %command% Assuming you've already done that, the Proton log will also be the next thing to check for clues. If it's the latter, double-check that you've extracted the entire archive (preserving all subfolders), that /home/deck/locales/run.sh is executable, and that the game's command line in Steam points to its correct location.You can check the Proton log for clues as to what is the cause. ![]() If it's the former, maybe whichever Windows game you're trying to play is not compatible with Proton for a reason unrelated to the missing Japanese locale files."Play" does nothing anymore after setting the command line)? PROTON_LOG=1 WINEDEBUG=+file,+nls,+msgbox %command% to troubleshoot file accesses, locales/character set conversions and message box contents.Īs in, no visible effect (the game doesn't work either with or without the modified command line), or that it breaks launching the game at all (aka.Make run.sh executable: chmod +x ~/locales/run.sh.Script= ' BEGIN 'Ĭommand= " $(awk -v newlocpath= " $newlocpath " " $script " <<< " ) " eval " $command " Newlocpath= $(dirname " $(realpath " $0 " ) " ) Uncomment ja_JP.UTF-8 in /etc/locale.gen.A full install of Arch Linux is required (commands may need adjustments to work in other distributions). Set the game's launch options to LANG=ja_JP.UTF-8 ~/locales/run.sh %command% to fix locale and encoding issues.įollow these steps instead to generate the files manually.Double-check that /home/deck/locales/run.sh is executable (right click > properties > permissions).Extract the archive using Ark into the home directory on the Steam Deck ( /home/deck).This sets the Wine codepage to Japanese and the Unix character set to UTF-8 without requiring root access or unlocking the readonly system partition of the Steam Deck. Ja_JP.UTF-8 is not provided by SteamOS 3 so requesting it makes the effective Unix locale fallback to C (ASCII) again. The simple solutions shown above to problem 1 and 2 are unfortunately mutually exclusive. ![]() However Steam may override it, so instead set the game's launch options to HOST_LC_ALL=ja_JP.UTF-8 %command% to have Proton set LC_ALL to the desired value. Steam Deck's SteamOS 3 doesn't provide a ja_JP.UTF-8 locale so this leaves LC_ALL. This is equivalent to using Locale Emulator on Windows. ![]() Wine uses the current system locale (set via LANG) or the LC_ALL environment variable to determine which ANSI codepage to use. The Windows ANSI codepage must be set to SHIFT-JIS to fix this. Some games may even completely fail to load due to script compilation errors (common in visual novels). Japanese text displays as mojibake or question marks. #!/bin/sh export LANG=en_US.utf8 Problem 2 ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |