I try to load a vlog file with vassal from the command line, but I keep getting an error:
$ vassal -l test.vlog Here_I_Stand_3.2.vmod
VASSAL: File ‘test.vlog’ of unknown type
I can load the module (vmod) from the command line and I can load the vlog from the vassal gui.
Anyone have an idea what is wrong here?
OS: Arch linux
Vassal version 3.2.13
Thus spake Yos-T:
I try to load a vlog file with vassal from the command line, but I keep
getting an error:
$ vassal -l test.vlog Here_I_Stand_3.2.vmod
VASSAL: File ‘test.vlog’ of unknown type
Have you tried just ‘vassal -l test.vlog’?
–
J.
Yes, I have. I have tried multiple variations, but all give the same error message.
Thus spake Yos-T:
Yes, I have. I have tried multiple variations, but all give the same
error message.
Post your log here so we can take a look.
–
J.
Thanks for having a look at my problem!
I just tried on a Windows 8 system and there it works fine. I tried a Windows PowerShell and cygwin and both work, so the log file itself seems ok.
Thus spake Yos-T:
Thanks for having a look at my problem!
I just tried on a Windows 8 system and there it works fine. I tried a
Windows PowerShell and cygwin and both work, so the log file itself
seems ok.
It works for me when the module is already known by the Module
Manager. My guess is that when it isn’t working for you, the MM
doesn’t know where to find the module.
–
J.
Thanks for the support, but that was not my problem.
The vassal batch script that came with the package (from the arch repository) reads:
#!/bin/bash
cd /usr/share/java/vassal && java -classpath lib/Vengine.jar VASSAL.launch.ModuleManager "$@"That’s not going to work with relative paths… But it’s easy to fix 
Thus spake Yos-T:
The vassal batch script that came with the package (from the arch
repository) reads:Code:
#!/bin/bash
cd /usr/share/java/vassal && java -classpath lib/Vengine.jar
VASSAL.launch.ModuleManager “$@”That’s not going to work with relative paths… But it’s easy to fix
Send us a patch?
–
J.
Sure, can you point me to the procedure on how to sumit a patch?
The patch would be in file /dist/VASSAL.sh
change:
cd "$INSTALL_DIR" && java -classpath lib/Vengine.jar VASSAL.launch.ModuleManager "$@"to
java -classpath "$INSTALL_DIR"/lib/Vengine.jar VASSAL.launch.ModuleManager "$@"Thus spake Yos-T:
Sure, can you point me to the procedure on how to sumit a patch?
The patch would be in file /dist/VASSAL.sh
change:Code:
cd “$INSTALL_DIR” && java -classpath lib/Vengine.jar
VASSAL.launch.ModuleManager “$@”to
Code:
java -classpath “$INSTALL_DIR”/lib/Vengine.jar
VASSAL.launch.ModuleManager “$@”
That’s a sufficiently small change that I’ll apply it manually.
Bug 11667 is tracking this:
vassalengine.org/tracker/sho … i?id=11667
–
J.
Thus spake Joel Uckelman:
Thus spake Yos-T:
Sure, can you point me to the procedure on how to sumit a patch?
The patch would be in file /dist/VASSAL.sh
change:Code:
cd “$INSTALL_DIR” && java -classpath lib/Vengine.jar
VASSAL.launch.ModuleManager “$@”to
Code:
java -classpath “$INSTALL_DIR”/lib/Vengine.jar
VASSAL.launch.ModuleManager “$@”That’s a sufficiently small change that I’ll apply it manually.
Bug 11667 is tracking this:
Fixed in trunk@9166.
–
J.
It seems that this has broken the call of help files.
If you don’t start Vassal from within its install directory, the help menu does no longer work.
Under Linux I have added a line “Path=…” in my Vassal “desktop” file to circumvent the problem (and I guess it’s better practice ;-), but the help doesn’t work when launched from the command line (for instance with a “/dist/VASSAL.sh” like in this thread).
Fixed for all my regular installations.
Thanks.