Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Ah sorry for not being specific. By common problems I was mostly referring starting it up and actually getting it to work before the recent patches. I've actually been trying Gedosato but have been having a very hard time wrapping my head around it. Haven't heard of "tsfix" though! Is that something that I should be looking into?
I just switched the languages and its still the exact same problem :/ .
Its set to default English from what I can see.
This game doesn't even use Unicode, as much as that frustrates me. I write all my software with Unicode support, and then incredibly, a lot of Asian games wind up ported to Windows without it. I sit there completely flabbergasted as they use ANSI for everything and then stuff like this happens.
Not only is it a portability issue, but Unicode software actually runs faster on Windows than ANSI. It has been this way since Windows 2000.
I would have said this sooner, but I didn't see this post until now.
If that's the case, then it suggests that tweaking the Windows display setting for non-Unicode applications to Japanese might have an effect. I'm sorta guessing the game is trying to display an error message and failing miserably.
http://windows.microsoft.com/en-au/windows/change-system-locale#1TC=windows-7
To be clear, this is different to changing the overall system language.
The game probably doesn't care about the system locale, especially for a Steam game where language settings are handled by Steam. I have almost complete confidence that it's an Intel HD GPU issue and forcing the Nvidia GPU will absolutely solve his issue. Have seen this same exact issue countless times and that's invariably what it is.
Which is just one reason why I'm not terribly happy about the way Windows 10 manages software updates. It's been known to swap out newer drivers with older ones simply because the system manufacturers aren't keeping up with the times. The NVidia debacle (where computers would get stuck in a rebooting loop while NVidia's updating software and 10's own updating mechanics constantly switched between a newer and an older driver release) would probably be the most well-known example of this, but I'd imagine it's also causing problems for a lot of Intel HD users (whether they know it or not).
... they're sorta handled by Steam. The idea is that you can switch releases of a game using its Steam properties panel. But there's nothing stopping a developer from putting multiple language strings into one single build (or simply putting the wrong ones in full stop): Steam's got no control over what happens in that case; Namco would be to blame for any related problems.
Anyway, there's no harm in testing either solution. :)