Why the corruption VASL

[Oberst Hausser]

This is just some of the error log which I hope can help....

2020-06-29 16:21:41,216 [0-main] INFO VASSAL.launch.StartUp - Starting
2020-06-29 16:21:41,223 [0-main] INFO VASSAL.launch.StartUp - OS Windows 10 10.0
2020-06-29 16:21:41,223 [0-main] INFO VASSAL.launch.StartUp - Java version 1.8.0_251
2020-06-29 16:21:41,223 [0-main] INFO VASSAL.launch.StartUp - VASSAL version 3.2.17
2020-06-29 16:21:41,567 [0-AWT-EventQueue-0] INFO VASSAL.launch.ModuleManager - Manager
2020-06-29 16:21:43,503 [0-SwingWorker-pool-1778611197-thread-1] INFO VASSAL.launch.AbstractLaunchAction - Loading module file C:\VASL 6.4\vasl-6.5.0.vmod
2020-06-29 16:21:46,774 [0-SwingWorker-pool-1778611197-thread-1] INFO VASSAL.launch.TilingHandler - No images to tile...

....

,,,

Module 6.5.0 engine 3.2.17

At present the opposite player has the same 6.5.0

It just says an error occurred,,.


Yes I removed the beta before rechecking.

I am not sure what to do.

I think it might be best that everyone has 6.5.1 beta with 3.2.17

??

 

[uckelman]

That's not the part of the errorLog with the error in it. Try posting the whole thing.

 

[Oberst Hausser]

To simplify the problem.

Now opened a game saved in 5.0 opened in 5.1.

Now it reports that the game was saved in 5.0 etc

Then it just goes on to say there was an error.

I am going to presume one has to set up a game IN 5.1 from scratch.

It's a bit of a drama, not being a programmer I wonder how in lay terms why this would happen.

Reason= It's 2020

 

[uckelman]

But what is the text of the error message?

 

[DougRim]

I am going to presume one has to set up a game IN 5.1 from scratch.

No, this is not correct. You should be able to open a game in 6.5.1 that was saved in 6.5.0. In fact, I just did so with no problem.

Until we can see the error message you are seeing, we can't possibly guess at what the problem is.

 

[Oberst Hausser]

I cannot post logs because it says it it over 2000 letters.

I also can't attach word docs .

 

[uckelman]

The errorLog is a text file. Rename it to errorLog.txt and you'll be able to attach it here.

 

[Oberst Hausser]

I don't know why but for the moment the problem seems to have resolved.