Can't edit teams – no crash, just blank fields

[soustruh]

Hi all,
I have a strange problem with my WA. I have the latest patch, tried to fix the issue with performing clean install, but nothing helps.

The problem is that I can't edit any of my teams. When I enter the Edit screen, it looks like shown in the attachment. However, when I look at the teams statistics, everything looks fine. The game is definitely capable of writing to the teams/wg.wgt file, as the modification time of the file always changes after playing the game.

When I edit the teams in TeamEd, these changes are reflected in the game. I'd like to point out that I used TeamEd yesterday for the first time, so I don't think it corrupted my file somehow. I just couldn't think of another way of editing my team.

Can you help me? I'd love to be able to edit my teams in the game and I'd hate to create new wg.wgt file as I don't want to lose my achievements and statistics. :-(

EDIT: I just tried deleting my wg.wgt file and after creating new team, I still can't edit it – the problem seems to be somewhere else… I also tried deleting custom flags and graves, but that didn't help neither.

[GreeN]

Did you move your W:A installation folder, or something? It would be logical to assume you would see those blank lists if the game could not locate your flags, graves and speech folders. (Normally located in C:\Team17\Worms Armageddon\User\)

[soustruh]

No, I didn't move my folder, it's always been installed in the same folder on my computer. I also checked the registry, but everything seems correct and the right folder is listed there.

I also think that wouldn't affect loading of the worms' names, would it – but everything else work flawlessly: the teams work, I can choose among them or view their statistics, any changes to flags and graves made in TeamEd reflect in the game. The only thing that doesn't work is this menu screen, which won't load even the worms' names. :-(

[SgtFusion]

Which version of Windows are you using?

[franpa]

Make sure you're using the latest version of the game (Yes, the latest beta update).

[soustruh]

Of course I use 3.6.31.0, no newbie here. :-) Windows 7 x64. I can't swear if I already used this one, when I had no trouble editing my team, or whether it was x86 version (I upgraded from 2 to 6 GB RAM)… But in the times when everything worked fine, I definitely used Windows 7.

It just came to my mind that I can copy my whole game folder to another (Win XP) computer and try to find out, whether the problem is related to some missing files or is caused by my Windows configuration (registry, x64 version etc).

[SgtFusion]

Have you tried running the game as administrator?

[soustruh]

Although I know I shouldn't do that, I use my PC as administrator all the time… :-)

[SgtFusion]

No, I mean: Have you tried right-clicking on the game and selecting "Run as Administrator"?

[soustruh]

Tried now – didn't help. :-(

EDIT: I just tried copying my whole game folder to another computer with Windows XP as I mentioned above. The problem persists, but instead of showing weird blank screen, the game crashes, so now I have at least the errorlog.txt – see the attachment. :-)

[Deadcode]

That crash occurred when W:A attempted to add the first entry to the listbox of gravestones.

Make sure the following files exist under your main Worms Armageddon folder:

Graphics\CreateTeam\Graves\[ Gravestone 1 ].bmp
Graphics\CreateTeam\speech.bmp

If they do exist, then view them to make sure they aren't corrupted. The first one is a still-frame of the first animated gravestone; the second one is cropped picture of a worm with a speech bubble containing a question mark.

[soustruh]

I love you, Deadcode! :D The origin of my WA installation is Czech installation CD, so filenames of all graves were localized to:
[ Náhrobek 1 ].bmp.
I just renamed them to:
[ Gravestone 1 ].bmp and so on and everything works fine!

Thanks a lot!

[Thurbo]

Whoa, that's god-awful. Does that mean neither Czech player is able to edit teams?

[StepS]

Whoa, that's god-awful. Does that mean neither Czech player is able to edit teams?

After updating the game via official update. (And whether he had this localized version)

[Deadcode]

I love you, Deadcode! :D The origin of my WA installation is Czech installation CD, so filenames of all graves were localized to:
[ Náhrobek 1 ].bmp.
I just renamed them to:
[ Gravestone 1 ].bmp and so on and everything works fine!

Thanks a lot!

I'm so glad that helped! :D Honestly I didn't think it would be that simple...

You're very welcome, soustruh!

Oh, and maybe we should make it fall back on those alternate filenames in the next version.

[soustruh]

Thanks again for solution to my problem. :-) I'll try to contribute to this problem a few days later, I am quite busy these days. I'll perform a completely clean install, apply 3.6.31.0 and let you know what's happened.

Re Thurbo and Stepanesss: I am quite sure I've played and patched this Czech version many times, but a few months ago I've experienced serious problems with my install, which I repaired, but I really can't tell exactly how. :-) I'll try to replicate as much as possible and post my findings here…

[bonz]

Looks like someone overambitiously translated every English word they could find on the disk.

[soustruh]

Well, more than a year after I tried to perform a clean install of the game and then patch right to 3.7.0.0. The problem still persists, so a manual filename change is needed… By the way, the localised filenames contain triple space (Náhrobek***1, where * stands for space) which need to be changed to single space (Gravestone*1). Maybe GFXUpdate.exe could take care of this, check, whether these files are present, and download them if they're not?

[Deadcode]

Well, more than a year I tried to perform a clean install of the game and then patch right to 3.7.0.0. The problem still persists, so a manual filename change is needed… By the way, the localised filenames contain triple space (Náhrobek***1, where * stands for space) which need to be changed to single space (Gravestone*1). Maybe GFXUpdate.exe could take care of this, check, whether these files are present, and download them if they're not?

Oops! I had forgotten to address this problem. I've now implemented a fix which will be in the next update.