PzC 1.11 exe screwing map strings ?

[Chris10]

Does anybody else experience this ?
I have copypasted PzC 1.11 exe into my PzC East building folder and it screws completely ALL map strings (inlcuding those for terrain type) when opening the big map which has been edited with the last editor coming with 1.10
Could it be related to the fact that the missing terrains for desert muddy/frozen have been added but places are occupied by Massis
tiles ?...But how can this be related to the map strings ?...I only used map strings for city/airfield/harbor and river tiles so this doesnt seems plausible...
When launching with PzC 1.10 everything is fine
Dont know what to do

1.10.exe Ploesti and Königsberg



1.11.exe Ploesti and Königsberg and Ocean tiles

[VPaulus]

Chris... ask Alex.

[Razz1]

I see your using the Massi tile mod.

Was this enabled through GME or is it part of your regular file?

Try loading it up in the 1.11 editor, then save.

That fixed all the problems in 1.10.


I still have a problem with maps on 1.05 and earlier.

I have to load up a stock map first, then my map.

Otherwise, the question marks do not appear and others can not play my maps.

In fact I have a map Operation Goodwood from a member that has the same problem. I believe that map was started in 1.10.

I do know the hotfix patch for the editor fixed the problem in the past. However now I must load a stock map in version 1.10 or later.

Very annoying.

By the way... I haven't seen a map string problem yet.

[4kEY]

Was 1.11 supposed to address the city name scrambler?

[Chris10]

I see your using the Massi tile mod.
Was this enabled through GME or is it part of your regular file?
Try loading it up in the 1.11 editor, then save.
That fixed all the problems in 1.10.

Iam building the mod in a complete folder to make it full accessable to everybody without having to fiddle around with
other things and make sure clean install without hassle. So people have only to throw their exe into
the folder and go..so all files are parts of the gamefolder...

Even considering using Massis tiles (before muddy/frozen desert tiles were added) there where there is ocean or shallow water there is ceratinly no escarpment or desert as be seen in the last image..so the mess doesnt seem to follow a pattern

The weird thing is ALL map strings are completely messed up...not only custom strings like city names

Was 1.11 supposed to address the city name scrambler?

[El_Condoro]

I had a similar problem with my D-Day scenario - the names seemed completely whacked when I opened the scenario in the game. When I checked in the editor they seemed fine so I saved the scenario and tried again - this time the names were AOK. I think this might be what Razz is saying to do. It might be that a couple of extra terrain names are added to the pzloc, which pushes all other names down the list. Not sure - just guessing really!

[Chris10]

I had a similar problem with my D-Day scenario - the names seemed completely whacked when I opened the scenario in the game. When I checked in the editor they seemed

yeah...thats exactly what happens

Sso I saved the scenario and tried again - this time the names were AOK.

I will have to make copys and backups and copys and backups of the backups before I will try anything funny...as you might understand Iam scared to death to screw the big map up cause I have already placed and named 300 untis and it was a mountain of work...puuhhh

It might be that a couple of extra terrain names are added to the pzloc, which pushes all other names down the list. Not sure - just guessing really!

hmmm...strings are always added to the end of the pzloc with increasing numbers and not to the beginning...

What is strange though is that the pzloc has the desert terrain specifications whereas in any regular pzloc file starts with string 22 as up to 21 its terrain strings which are hardcoded.




EDIT
ok..after making backups of backups of backups of backups which were copys of the original I open the big map in 1.11 editor and saved it...launched with 1.11 exe and all of a sudden the shit works as before.........well...nvmd

[fsx]

Chris, you have to load and save all your 1.10 scenarios with the 1.11 scenario editor!

viewtopic.php?f=121&t=38210#p358275

LOOK AT SUCH CONFIGURATIONS:
* using a 1.10 scenario with 22+2 terrains with 1.11 exe -> not ok __________________ If I load&save the scenario with the 1.11 editor and redo the test -> ok, save+reload -> ok
* using a savegame from 1.10 with mixed strings and loading in 1.11 -> not ok, but it is not a problem. If I start a new scenario with 1.11 all savegames I make are okay.

[VPaulus]

Sorry Chris, I forgot to tell you about that post from fsx.
Thanks fsx.

[Rudankort]

Hello All!

Strings issues have become so complicated, it is almost impossible to test all possible combinations. 1.11 should have resolved all issues related to PzC/AK campaigns and DLCs, and also handles custom scenarios better than 1.10. In particular, 1.11 editor always takes exact number of terrain types from terrain.pzdat, and the number of default strings it generates (i. e. Sea, Shallow Sea, Lake etc.) always matches that number. 1.10 editor (as well as the game itself) always used 22 terrain strings, no matter how many terrain types were there in the terrain.pzdat. For this reason, there can be some tricky issues when migrating from problematic 1.10 to 1.11. However, 1.11 should load older content correctly, and this is confirmed by the fact that all past DLCs (which were created with the old versions of the game and never patched) still work in 1.11.

I'm not sure what exactly happened in this particular case, because I don't have your scenarios, pzloc files and terrain.pzdat file. I'm happy that the issue seems to have resolved. But if it happens to anyone again, please send relevant files to me (or maybe the entire mod), and I'll investigate and fix the issue.

[VPaulus]

Thanks Alex.

[Chris10]

Thnx Alex and all others...
it seems that after saving the map with 1.11 editor it also removed the remaining terrain strings from the visible pzloc and now strings start
with 22 (in reality 23 when having in mind stringO) as in any other pzloc.
So,yeah...Iam almost positive the issue had somehow to with the terrain strings...