Slitherine

huertgenwald wrote:In DLC 40, scenario 2 (Albert Canal) i found 2 wrong town names in the south eastern part of the map

a) one town named "Scheldt River" (no river nearby)

b) one town called "Albert Canal Bridge" ( canal is a good distance up north)

Don't know if that's related to patch 1.10 or if it was wrong from the start (i started DLC40 before patching to v1.10)

PS: There's a town on the map called Wsterlo, should have been Westerlo instead, right ?

PPS: I opened the map in the scenario editor and actually not only 2 but mostly all town names are mixed around.

Huertgenwald, could you check your saves from Eben Emael, are names wrong now too? (After reloading, they were probably OK if you played the scenario without reloads). Also - if you have time, that is - could you start any other Grand Campaign, save a scenario and reload - the names will probably twisted too?

If you have the same problem as I described, than I think it is definitely something to do with 1.10 exe, since 1.05 made no such problems. I even reinstalled Afrika Corps again (thus wiping out any unknown changes to most files), also deleted and reinstalled all DLC's, and the name problem persisted. So it's no fault of mine.

Not the most pressing of problems, but is does sligthly ruin the educational aspect of Panzer Corps.

A SHORT check on Eben-Emael and 2 scenarios in DLC39 seem to indicate that those savegames are OK.
A check up with the scenario editor suggests correct town names (no guarantess though!)

Than I am really flabbergasted, since it was the savegames that gave me problems. Scenarios were always OK when run for the first time (not from a savegame) or when open in the editor.

It must be those damn English. Or Russians. Or French. Or whoever.

Scenario The Hague: Town Names scrambled right from the start (round 0, troup placement)

Rotterdam renamed to Hellevoetsluis
The Hague renamed to Utrecht

BTW: Just for clarity and information: I use the original english version, although i'm german.

orlinos wrote:More news from the name string bug front.

1. Advancing to a new scenario in the Grand Campaign (by a cheat or from a save, even a save with wrong names) - the name strings are correct.

2. Saving and reloading the scenario - corrupts the names. Advancing to the next scenario - again means proper strings in the next scenario - until saved and reloaded. So I guess the problem is created during saving or loading the game?

This is my experience as well. Starting a scenario everything is fine. Loading a scenario from a save game and all of a sudden Kharkov becomes Burlak.

I analysed my "the hague" scenario a bit further:
Format: Hex, wrong name, correct name

• 19,2 Katwijk aan Zee HOOFDDORP
  23,1 Katwijk AMSTELVEEN
  21,5 Rhine Delta WESTEINDERPLASSEN
  14,7 Nieuwe Maas River KATWIJK AAN ZEE
  16,9 Dordecht LEIDEN
  26,10 Hoofddorp MAARSSEN
  13,11 Utrecht, also : (11,12), (13,13), (11,14) THE HAGUE
  16,14 Gorinchem ZOETERMEER
  23,12 Valkenburg AFB, also 16,8 WOERDEN; 16,8: is correct !!!
  28,13 Maassluis UTRECHT
  20,16 Amstelveen GOUDA
  14,17 Rhine River Tributary YPENBURG AFB
  23,19 Ockenburg AFB SCHOONHOVEN
  17,20 Hellevoetsluis, also : (15,20), (14,22), (17,22) ROTTERDAM
  10,21 Ypenburg AFB MAASSLUIS
  9,25 Westeinderplassen HELLEVOETSLUIS
  25,24 Schoonhoven GORINCHEM
  19,26 Woerden DORDECHT

Reading the pzloc file, i saw that an offset of +6 is added to the town name variable, meaning IDS_STRING16 is substituted with IDS_STRING22 etc..

Can this be reproduced by the "powers that be" ?
Do you need a savegame ?

HtH

Hi!

These are the 6 new terrain types.


What could you do?

Use a new terrain and movement file.
Add manually the 6 terrainstrings to the pzloc.

OR:

Use a new terrain and movement file.
Use an 1.10 english!! scenario editor.
Save the scenarios (having now version 1.10).
playing with version 1.10


If you have questions, you could talk to me in german at DMP (link below).

In einem anderen Thread wurde ein Patch von LordZimoa angekündigt (dt., franz. u. russ. Text) plus einige Bugfixes. Auf den werde ich warten.
In another Thread LordZimoa announced a future patch with german, french and russian translations plus several bugfixes. I'll wait for that.

viewtopic.php?f=121&t=36609

Natürlich könnte man mal versuchen, die pzloc-Datei des jeweiligen Szenarios zu korrigieren und zu testen, ob das funktioniert.
Of course you can always try to manually modify the scenario-specific pzloc-file and see if that works out.

Well, i followed my own advice and tried a hotfix for "The Hague.pzloc".

I changed :

IDS_STRING16 -> IDS_STRING22
IDS_STRING17 -> IDS_STRING23
etc..

That seems to work fine (made a short playtest including an AI round).

But as already said, i don't want to mess too much with my game.
So i'll wait for the patch which i hope will be made avaible rather sooner than later.

There will be an official fix. It's only a matter of waiting a little longer.

VPaulus wrote:There will be an official fix. It's only a matter of waiting a little longer.

Do you have any information how this patch will work? Will the whole files be replaced or will any file be edited to change the String-ID's programmatically? The reason for this question is because I use localized pzdat-, pzbrf- and pzloc-files for the Grand Campaign.

Sorry, but I don't have that kind of information.
The only person who could answer is Rudankort, but he has having problems with his Internet connection, and that's the reason why he didn't intervene in some of the threads.

VPaulus wrote:Sorry, but I don't have that kind of information.
The only person who could answer is Rudankort, but he has having problems with his Internet connection, and that's the reason why he didn't intervene in some of the threads.

No matter, so we have to wait (and see).

Curiouser and curiouser! I'm in DLC 42 again. It seems, that the game substitutes English names of ordinary terrain strings (hills, clear, forest, airport etc.) for Russian ones. If I open a scenario from '42 in Scenario Editor, I also see Russian strings on the map and in the menu "Map Strings". I just checked, only 42 is affected, not other DLC's.

If I load a scenario using the editor in my backup 1.05 folder, there is no trouble with names.

This seems to be something else than the "name corruption after reloading problem", although it might be connected.

I have to admit, I am fascinated. Where are these Russian names coming from? If I understand correctly, the strings for other languages are in the folder "Localization", but changing its name doesn't solve the problem. Interesting.

The same I noticed updating the 1.05 scenarios to 1.10 (DMP-Ostfront).
In the 1.05 scenario-file are the strings for terrain in german. But if I use the scenario in an english PC, all strings are in english.
In the 1.10 scenario file these strings are also in german in the pzscn (I used an english scenario editor for upgrade) and are in german, if I use an english PC-version.

It seem, the program now uses the strings from the pzscn file, not the language-related.

But, the format of the pzscn file is different between the original for example barbarossa and the files comes with the 1.10 patch.
And as I wrote, if I update the 1.05 file to 1.10 the format looks like the "old" 1.05. If I see in an AfrikaCorps file, its totally different.
The Old type starts with strings (Axis..), the new one not.

If I make a new scenario the file begins with the strings.
Are the scenario-files cames with 1.10 "compiled" or "packed" ??

A bad side effect of the string bug is that if you occupy a location that is supposed to give you a captured unit, if the city name is incorrect you won't get the unit.

How is that possible, dragos ? Have you tested this properly ?
In theory the captured unit should be linked to a map hex, regardless of the name assigned to that hex.

It happened to me in Novgorod scenario. Bronnitse is suposed to give you a captured unit. Upon reloading mid-scenario, I captured the city (now having a different name), and next turn no unit appeared there