Patching via GameSpy fails: "wrong locale"

[HanaTool]

Hello,

I've read here numerous times that:

1. Patching via online lobby at GameSpy will do everything correctly AND

2. Manual patching (alternative) should be done consecutively from the very first one.

Both methods fail and I am unable to access any online games.

I 've bought a LEGAL copy of the game in China (all in-game content is in English). Out-of-the-box version is 1.0. Online lobby first loads patch 1.3 (goes well), then 1.4 resulting in the message "Patching Error: You're trying to apply the patch to a wrong locale"

Alternative manual patching does not work, as not a single patch, be it 1.01, 1.10 or 1.2, agree to execute with my version 1.0 ... :(

[arasfu]

The same happen to me!!!!!!!
And no one helps! The photo of the first cd (to understand the version for THQ..) is at: http://forums.relicnews.com/showthread.php?t=73982

I've paid for a game that now I can't patch to play online and I can't patch to install WA.. Thanks THQ!!!!!!

[Moe]

Ok since a bunch of people have reported this problem with the chinese version I'm starting to suspect a faulty setting in the game somewhere. Please contact the official tech support at THQ.

[HanaTool]

Hello, Moe

Thanks for quick reply. I've tested all imaginable combinations and sequences. The conclusion: only patch 1.3 installs without this non-compatibility warning. Neither earlier patches (1.01, 1.10, 1.2) nor 1.4 work at all. And, of course, the game doesn't let you into the online lobby without the latest patch.

Installation of 1.3 leaves the following version mark on the game's main menu screen:

DoW Engine 1.30 Warhammer 40,000: Dawn of War 1.0

By the way, the game version isn't really "Chinese" as absolutely everything including installation menus is in English.

[TBS]

Something is very wrong there - 1.3 should NOT be able to install on 1.0. Contact THQ so they know theres a problem.

Also post a warnings.log from "1.0" and "1.3" please.

[arasfu]

for now THQ answered that I must contact euro assistance!!! A good beginning!!!!!!!!!!

[HanaTool]

Hello everyone,

Here's what I did. I noticed that in the w40k.INI file of my out-of-the-box "version 1.0", it is stated version 1.2. This probably explains why 1.3 always installs so smoothly.

Then, in the w40k.INI of the version upgraded to 1.3, I changed english_china to english. This allowed to run patch 1.4 without interruptions (final warnings log is below).

The newly upgraded 1.4 game (with english stated in the Regions.INI) refuses to start with a warning "Could not load localized text. Please make sure you are running this utility from your Warhammer\Root\ directory.

If I now change english to english_china in the Regions.INI, the game starts. However! I didn't go beyond the settings (little graphic choises menu) as it scared me with text rubbish all over the place: instead of meaningful words in the drop-down menu and buttons, it states "$510018 No range" everywhere.

So what shall I do to resolve this localized fonts situation? The game is already patched up to 1.4.

-----------------Warnings log-------------------

07:43:07.14 W40K started at 2005-10-04 07:43
07:43:07.14 OS NT 5.1, 512MB Physical Memory
07:43:07.14 RUN-OPTIONS
07:43:07.14 WORKING-DIR C:\Program Files\THQ\Dawn of War
07:43:07.14 USER HP_Owner
07:43:07.14
07:43:07.20 APP -- Executed syscmd GraphicsConfig.exe -rungame through dlltie.dll
07:43:07.20 APP -- Exiting to open Graphics config tool
07:43:07.20 AppInitGlobal -- Failed load for step: 'Config'
07:43:07.20
Application closed without errors

---Graphic settings log (procedure aborted due to weird menu language, as described)---

07:41:56.05 GRAPHICSCONFIG started at 2005-10-04 07:41
07:41:56.05 OS NT 5.1, 512MB Physical Memory
07:41:56.05 RUN-OPTIONS -rungame
07:41:56.05 WORKING-DIR C:\PROGRA~1\THQ\DAWNOF~1
07:41:56.05 USER HP_Owner
07:41:56.05
07:41:56.05 MATHBOX -- Version=5, Cpu=unknown:f=15,m=4, Mode=SSE
07:41:56.06 Graphics Configuration Utility
07:41:56.06 LOCALIZER -- Requested string ID '510012' does not fit in a valid key range!
07:41:56.06 LOCALIZER -- Requested string ID '510000' does not fit in a valid key range!
07:42:26.00 LOCALIZER -- Requested string ID '510012' does not fit in a valid key range!
07:42:26.00 LOCALIZER -- Requested string ID '510016' does not fit in a valid key range!
07:42:26.00 LOCALIZER -- Requested string ID '510133' does not fit in a valid key range!
07:42:26.00 LOCALIZER -- Requested string ID '510001' does not fit in a valid key range!
07:42:28.69 LOCALIZER -- Requested string ID '510012' does not fit in a valid key range!
07:42:28.69 LOCALIZER -- Requested string ID '510002' does not fit in a valid key range!
07:42:28.69 LOCALIZER -- Requested string ID '510132' does not fit in a valid key range!
07:42:28.69 LOCALIZER -- Requested string ID '510132' does not fit in a valid key range!
07:42:28.69 LOCALIZER -- Requested string ID '510132' does not fit in a valid key range!
07:42:28.69 LOCALIZER -- Requested string ID '510132' does not fit in a valid key range!
07:42:28.69 LOCALIZER -- Requested string ID '510132' does not fit in a valid key range!
07:42:28.69 LOCALIZER -- Requested string ID '510132' does not fit in a valid key range!
07:42:28.69 LOCALIZER -- Requested string ID '510132' does not fit in a valid key range!
07:42:28.69 LOCALIZER -- Requested string ID '510132' does not fit in a valid key range!
07:42:28.69 LOCALIZER -- Requested string ID '510132' does not fit in a valid key range!
07:42:28.69 LOCALIZER -- Requested string ID '510132' does not fit in a valid key range!
07:42:28.69 LOCALIZER -- Requested string ID '510132' does not fit in a valid key range!
07:42:28.69 LOCALIZER -- Requested string ID '510132' does not fit in a valid key range!
07:42:28.69 LOCALIZER -- Requested string ID '510132' does not fit in a valid key range!
07:42:28.69 LOCALIZER -- Requested string ID '510132' does not fit in a valid key range!
07:42:28.69 LOCALIZER -- Requested string ID '510132' does not fit in a valid key range!
07:42:28.69 LOCALIZER -- Requested string ID '510132' does not fit in a valid key range!
07:42:28.69 LOCALIZER -- Requested string ID '510132' does not fit in a valid key range!
07:42:28.69 LOCALIZER -- Requested string ID '510132' does not fit in a valid key range!
07:42:28.69 LOCALIZER -- Requested string ID '510132' does not fit in a valid key range!
07:42:28.69 LOCALIZER -- Requested string ID '510132' does not fit in a valid key range!
07:42:28.69 LOCALIZER -- Requested string ID '510132' does not fit in a valid key range!
07:42:28.69 LOCALIZER -- Requested string ID '510132' does not fit in a valid key range!
07:42:28.69 LOCALIZER -- Requested string ID '510132' does not fit in a valid key range!
07:42:28.69 LOCALIZER -- Requested string ID '510132' does not fit in a valid key range!
07:42:28.69 LOCALIZER -- Requested string ID '510135' does not fit in a valid key range!
07:42:28.69 LOCALIZER -- Requested string ID '510135' does not fit in a valid key range!
07:42:28.69 LOCALIZER -- Requested string ID '510135' does not fit in a valid key range!
07:42:28.69 LOCALIZER -- Requested string ID '510016' does not fit in a valid key range!
07:42:31.01 LOCALIZER -- Requested string ID '510092' does not fit in a valid key range!
07:42:31.01 LOCALIZER -- Requested string ID '510093' does not fit in a valid key range!
07:42:31.01 LOCALIZER -- Requested string ID '510028' does not fit in a valid key range!
07:42:32.59 LOCALIZER -- Requested string ID '510012' does not fit in a valid key range!
07:42:32.59 LOCALIZER -- Requested string ID '510013' does not fit in a valid key range!
07:42:32.59 LOCALIZER -- Requested string ID '510003' does not fit in a valid key range!
07:42:32.59 LOCALIZER -- Requested string ID '510084' does not fit in a valid key range!
07:42:32.59 LOCALIZER -- Requested string ID '510050' does not fit in a valid key range!
07:42:32.59 LOCALIZER -- Requested string ID '510082' does not fit in a valid key range!
07:42:32.59 LOCALIZER -- Requested string ID '510052' does not fit in a valid key range!
07:42:32.59 LOCALIZER -- Requested string ID '510053' does not fit in a valid key range!
07:42:32.59 LOCALIZER -- Requested string ID '510054' does not fit in a valid key range!
07:42:32.59 LOCALIZER -- Requested string ID '510074' does not fit in a valid key range!
07:42:32.59 LOCALIZER -- Requested string ID '510056' does not fit in a valid key range!
07:42:32.59 LOCALIZER -- Requested string ID '510070' does not fit in a valid key range!
07:42:32.59 LOCALIZER -- Requested string ID '510048' does not fit in a valid key range!
07:42:32.59 LOCALIZER -- Requested string ID '510057' does not fit in a valid key range!
07:42:32.59 LOCALIZER -- Requested string ID '510058' does not fit in a valid key range!
07:42:32.59 LOCALIZER -- Requested string ID '510069' does not fit in a valid key range!
07:42:32.59 LOCALIZER -- Requested string ID '510016' does not fit in a valid key range!
07:42:32.59 LOCALIZER -- Requested string ID '510089' does not fit in a valid key range!
07:42:32.59 LOCALIZER -- Requested string ID '510132' does not fit in a valid key range!
07:42:32.59 LOCALIZER -- Requested string ID '510065' does not fit in a valid key range!
07:42:32.59 LOCALIZER -- Requested string ID '510064' does not fit in a valid key range!
07:42:32.59 LOCALIZER -- Requested string ID '510063' does not fit in a valid key range!
07:42:32.59 LOCALIZER -- Requested string ID '510065' does not fit in a valid key range!
07:42:32.59 LOCALIZER -- Requested string ID '510064' does not fit in a valid key range!
07:42:32.59 LOCALIZER -- Requested string ID '510063' does not fit in a valid key range!
07:42:35.47 LOCALIZER -- Requested string ID '510006' does not fit in a valid key range!
07:42:35.47 LOCALIZER -- Requested string ID '510007' does not fit in a valid key range!
07:42:35.47 LOCALIZER -- Requested string ID '510045' does not fit in a valid key range!
07:42:37.42 Cancelled - changes not saved
07:42:37.42
Application closed without errors

[Moe]

All text fields in DoW are filled by calling those strings. There are a bunch of tables somewhere that tell the game what "$6102" means, for example. Now obviously those things differ for the Chinese and the English version. When you set your locale to English, the patch (which is both international and English) probably thought you were running the English version, and proceeded to apply the English changes. And now those tables don't match anymore. That's at least my theory, I'm not sure if that can be fixed at all.

[arasfu]

still no answers from THQ.. Only bounced back my email claiming that I must ask to european support.. and european support not answers!!

[dustpuppy0001]

I have the exact same problem here. I asked THQ support, then THQ europe (2 weeks ago) and got this:

http://forums.relicnews.com/showthread.php?t=72712&page=2&pp=15

in summary: It's a known bug, they're working on it, but don't expect anything before the 1.5 patch.

Yes, that sucks. I bought this game only to play online, and now it doesn't even work. I finished the laughable single player campain in 1 day and now I'm waiting for them to fix that fscking patch for weeks.
Come on, it can't be *that* hard to fix some localization strings! :madashel:
<rant off>

[Moe]

I'm sorry to hear this guys. All I can tell you is that Tranj from THQ mentioned that they would be releasing a hotfix to address a few "critical issues" before patch 1.5, I'm hoping that this will be one of the things that are being addressed in the patch.