Game doesn't save?!

[Yoshi88]

Hi all,

just bought Worms Armageddon (original and everything) since me and my friends realized, how good the old PC classics are when compared to the current XBLA Versions :)

You guys did a great job with patching it so massively. It plays really good, looks almost like a HD Version and is in general much better than i remembered.

But I encountered a problem. I applied the latest Beta Patch and everything works fine except for one thing: To unlock all the functions and extra weapons i started to play the singleplayer training and missions. But it won't save my game. The next time i starte the game, all of my created teams and their progress are gone.

I just wondered: I looked all over the FAQs, the Troubleshooting, ReadMe etc. but i couldn't find anything related. Is this a common error or is the game not even able to save after installing the Beta Patch and i just overread that part?

Many thanks in advance for your help and greetings from Germany ;)

[CyberShadow]

Hi,

Have you installed the latest Beta update (3.6.31.0)?

What is the installation path you used when installing the game?

It sounds like the game fails to save the team file when exiting. The latest version should handle this situation better, providing appropriate error messages, and warnings on start-up if the current directoly isn't writable.

Are you using any anti-virus or anti-spyware software? I recall there was a certain program that conflicted with saving team files.

[Yoshi88]

Yup, installed 3.6.31.0.

Installation Path: C:\Program Files (x86)\Team17\Worms Armageddon

(Changed it from the standard path: C:\Team 17\ Could that cause the problem ?!)

Unfortunately i get no error message at all :(

I'm using Avira AntiVir, the Guard is active in the background (never caused me any problems though.)

But: I didn't install the latest "official" patch from Team17 for EU Disc Users from the homepage before installing the Beta Update, because i thought, it was obsolete since you included so much fixes in the Beta Patches. Maybe because of that? :confused:

If you need further specs or info, let me know. :)

[CyberShadow]

(Changed it from the standard path: C:\Team 17\ Could that cause the problem ?!)Yes.

I don't know why Windows decides to make the file apparently vanish, though.

[Yoshi88]

Reinstalled it in original folder --> Works flawlessly now!

I'm so happy now :D

Thank you for the quick support :)

[StepS]

Yup, installed 3.6.31.0.

Installation Path: C:\Program Files (x86)\Team17\Worms Armageddon

(Changed it from the standard path: C:\Team 17\ Could that cause the problem ?!)


Yes. Never ever install it in Program Files - it is restricted in rights by default on Vista and 7. When running WA under Program Files, Windows seems to create a phantomic temporary working directory somewhere, so you truly don't get any error. Don't do it and reinstall the game to \Team17\Worms Armageddon.

[SupSuper]

Yes.

I don't know why Windows decides to make the file apparently vanish, though.In Windows Vista+, if a non-admin program tries to write to an admin-only folder (Program Files, Windows, etc.), Windows transparently changes the path to C:\Users\<username>\AppData\Local\VirtualStore\<folder name> for compatibility reasons, and the application (should) keep working as if nothing had happened.

This kind of behavior can be controlled from the application either through manifests or avoiding admin folders in the first place.

[CyberShadow]

I know that. We purposefully did not include a manifest in newer Beta updates, to keep compatibility with older versions which kept some settings in the virtualized win.ini file. What I'm puzzled about is why virtualization (http://msdn.microsoft.com/en-us/library/bb756960.aspx) fails for this particular case (the game can't save the team file, or can't load it on the next start).

[Alby1987]

I know that. We purposefully did not include a manifest in newer Beta updates, to keep compatibility with older versions which kept some settings in the virtualized win.ini file. What I'm puzzled about is why virtualization (http://msdn.microsoft.com/en-us/library/bb756960.aspx) fails for this particular case (the game can't save the team file, or can't load it on the next start).

Belive me, I used many old software con 7. It's more common that you can think!