Maps have ran away

[custardpie]

Having the last problem fixed I have a couple of new issues.

When I try to load a saved log for a couple of games the loader cancels the request. This is only happening for a couple of scenarios, one geo with overlays and one Red Barr again with an overlay. Other scenarios with overlays work.

I tried reinstalling VASL and now have a much bigger issue my other games still load but the maps do not. I have checked the board directory and that is still correct. Any ideas why this is happening do I need to change the directory?

Thanks
Ian

 

[DougRim]

Revert back to vassal3.5.8 and delete all the bd files that won’t open.

 

[custardpie]

Revert back to vassal3.5.8 and delete all the bd files that won’t open.

Thanks, that has got my boards back but I still can't load two logs most recent files but can load older ones

Thanks
Ian

 

[Vinnie]

The move to the latest version has been problematical. I'm running 3.5.8 and 3.6.2 just now. The version conflict has been bad but I'm confident they will have it fixed soon.

 

[Steve E7]

I just had issues loading my maps, and had to roll back my vassal version

 

[uckelman]

I just had issues loading my maps, and had to roll back my vassal version

Can't be fixed if you don't describe the issues in sufficient detail.

 

[Steve E7]

I upgraded vassal to the latest version, and could not see the maps
As this thread suggested, rolled back to 3.5.8 and the boards were visible again.
VASL 6.6.2

 

[Robin Reeve]

VASL 6.6.3.1 solved that problem for me.

 

[von Marwitz]

I upgraded vassal to the latest version, and could not see the maps
As this thread suggested, rolled back to 3.5.8 and the boards were visible again.
VASL 6.6.2

I think that VASL v6.6.3.1 was released to address this particular issue (that's where it got the .1 from).

von Marwitz

 

[Steve E7]

Yes, installing VASL v6.6.3.1 to use with Vassal 3.6.3 worked

 

[Elfego Baca]

Whew! After removing v6.6.3 and installing v6.6.3.1, I "found" my missing mapboards. TY!

 

[agoldin]

I had the same issue, which was fixed with the same solution.
Thanks for posting!