Version Update Process Failed

[johnl]

The "Update game" function failed to update a single saved vsav file from 6.6.7 to 6.6.8. The file has only infantry/SW/marker counters. The process reported many "xxx has no GpId" errors for vehicle counters that are not in the file (at least 30) then failed and terminated.

 

[PresterJohn]

Does the update work with no extensions loaded?

 

[DougRim]

The updater does indeed work without extensions. In fact it is much more likely work properly without extensions.

My first thought would be that the source of the problematic counters is an extension that was used to create the counters on the map. But it could be something else. @johnl if you email me the .vsav file at dougerimmer@gmail.com, I can have a look at this.

In terms of the vehicle counters that are referenced in chat, I don't see them on the map image. Were they visible to you before you ran the Game Updater? Should they be part of the scenario? Do you have any particularly old extensions loaded - those that are .mdx rather than .vmdx? It may be that VASL is trying to update old counters from an old extension, whether they are needed for the game or not. If you have such extensions, you might trying removing them and then running the Game Updater. EDIT: Rereading your OP, I see that you already told us that these counters were not part of the game file so I strongly suspect they are part of an old extension that you still have installed.

 

[johnl]

The updater does indeed work without extensions. In fact it is much more likely work properly without extensions.

My first thought would be that the source of the problematic counters is an extension that was used to create the counters on the map. But it could be something else. @johnl if you email me the .vsav file at dougerimmer@gmail.com, I can have a look at this.

In terms of the vehicle counters that are referenced in chat, I don't see them on the map image. Were they visible to you before you ran the Game Updater? Should they be part of the scenario? Do you have any particularly old extensions loaded - those that are .mdx rather than .vmdx? It may be that VASL is trying to update old counters from an old extension, whether they are needed for the game or not. If you have such extensions, you might trying removing them and then running the Game Updater. EDIT: Rereading your OP, I see that you already told us that these counters were not part of the game file so I strongly suspect they are part of an old extension that you still have installed.

I removed the extension pointer in preferences and restarted VASL and the update succeeded so we do have an extension problem.

I'll try to identify the culprit and report back.

Thanks for your help.

 

[johnl]

I removed the extension pointer in preferences and restarted VASL and the update succeeded so we do have an extension problem.

I'll try to identify the culprit and report back.

Thanks for your help.

Here's the bad actors. I had all of the extensions on vasl.info except the "obsolete" list loaded. I expect many users do this. It might be courteous to post a warning about extensions containing counters.

All of these are on the "VASL 5.x Extensions" list.
"5OTO.mdx"
"5SV.mdx"
"5VBM.mdx"
"Berserk.mdx"
"Kreta.mdx"
"RbF4.mdx"
"SpecialForces.mdx"

 

[DougRim]

I had all of the extensions on vasl.info except the "obsolete" list loaded.

This is most definitely a worst-practice. I strongly recommend that you delete any and all .mdx extensions and only restore them one-by-one when absolutely needed for a particular scenario/cg. I have posted about this on GS, FB and Discord. Of course not everyone will have seen those posts.

I expect many users do this.

I certainly hope not! But I have seen it done before and I try to stamp it out whenever I can.

It might be courteous to post a warning about extensions containing counters.

Well, yes, but as per my comments about .mdx extensions, evidence would suggest that these kind of messages don't get high take-up or traction.

 

[PresterJohn]

It seems to be my experience that near half of the players I drop in on will have about 20 or 30 extensions loaded, most of which they first downloaded when they were wearing short pants.

 

[zgrose]

It seems to be my experience that near half of the players I drop in on will have about 20 or 30 extensions loaded, most of which they first downloaded when they were wearing short pants.

Not only that, but they'll have multiple versions of the same extension loaded and blissfully ignore the messages saying such.

 

[PresterJohn]

Not only that, but they'll have multiple versions of the same extension loaded and blissfully ignore the messages saying such.

I see it as a from of disrespect to all the work that has been done in the last few years to improve VASL and make those good (at the time) old extensions redundant.
There is only one extension not on the vasl.info list that I use and that is the VBM overlay tool downloaded from the resources here.

I do think that the next step forward is the inclusion of an extension management capability, especially to allow easy switching between live, pbem and solo/solitaire VASL, as well as weeding out 15 year old extensions.

 

[johnl]

Doug, I appreciate your advice and especially your hard work on VASL. it allows me to play many times more than I would be able if I could only play ftf. I generally just skim thru new postings for items of interest so missed the importance of using only vmdx extensions. I promise to pay more attention to your posts in future.

I would humbly recommend that you add your advice to not use mdx extensions to the download page. The only advice there now is
VASL 5.x Extensions
These are built to work with 5.x VASL, and may still work with 6.0 or later

An admonition not to use these unless you absolutely need to and to remove them if you are having problems might keep people who don't understand the technical side of things from loading them - or not. Or maybe just a short paragraph on the virtues of minimalism. Just a thought.

YMMV
John L