Saving game or creating log closes Vassal

[cholmcc]

@dsulsberger

Here’s an update on everything I’ve tried since the last post:
…
and still had the problem.

Hmm. Strange. What still bothers me is you get no errors. That really points to something is going on that isn’t captured inside the Vassal application it self (otherwise, that should cause an exception to be thrown, and that would be reported in the errorLog). I still suspect that somehow Windows is the culprit one killing Vassal for some god-forsaken odd reason.

@dsulsberger

I feel like I’m over my head trying to run the debug program. What does the $ mean in the instructions? What would I even be looking for?

As mentioned in How to debug Vassal

Running an application in a debugger is not for the faint-of-heart. Only attempt this if you are willing to put in the work yourself, or you already have experience with such as task.

The $ at the start of the lines is meant to illustrate the command prompt. That is, you should not enter that into the command prompt - only what follows that character.

@uckelman

You should try starting Vassal from a command terminal.

To do that, do

1. Press Windows+R (that’s the Windows key and R pressed at the same time)
2. In the dialog that shows up, write cmd and press OK.
   
   
3. A window will pop up - all black and with light-gray text. This is a command terminal.
   
   
4. In the command prompt, change directory to the place where you installed VASSAL (typically C:\Program Files\VASSAL-3.7.26), by writing in the command prompt

    $ cd "C:\Program Files\VASSAL-3.7.26"
   

   (do not type the $ - that is meant to illustrate the command prompt. See also below).
   
   
5. Now run VASSAL in the terminal by typing

   $ jre\bin\java.exe -jar lib\Vengine.jar
   

   (again, do not type the $ - see also image below)
   
   

The above will start the normal Module Manager from which you can load a module. However, if that does not produce additional output when Vassal crashes (as you attempt at opening a save or log file), then you may need to execute the player application directly.

5. Assuming you have a module in C:\Users\DSuls\Downloads\GTC2_3_12.vmod, you write in the terminal prompt

   $ jre\bin\java.exe -cp lib\Vengine.jar VASSAL.launch.Player --load C:\Users\DSuls\Downloads\GTC2_3_12.vmod
   

   to launch the module directly. See example below, where I run the module C:\Users\45246\Documents\Wargames\Vassal\AnzioBeachhead.vmod directly.
   
   

@dsulsberger

I may end up switching to an older machine that still has vassal running correctly on it

If it turns out that you can run the same Vassal version with the same module, and have no problem creating a new save or log file, then it really starts to point to something on your newer machine.

Yours,
Christian