Why does my VASSAL module attempt to load a map I deleted? I initially attempted to use a single map to make my module and discovered I couldn’t fit the VASSAL hex grid to the whole map thus decided to split the map into 4 pieces, each with its own name . I deleted the original map, then added the 4 map sections, each with a hex grid.
So when the module loads, it attempts to load the non-existent map, and ‘hangs’ for about 10 to 30 seconds. Afterwards, the images complete ‘tiling’, and the modules works fine.
I even went back and added the deleted map (and a ‘blank’ images to load) and the modules still hangs, even longer than before.
The module is too large to attach and I do not want to post it on the Modules page with this error.
Why does my VASSAL module attempt to load a map I deleted? I initially
attempted to use a single map to make my module and discovered I
couldn’t fit the VASSAL hex grid to the whole map thus decided to split
the map into 4 pieces, each with its own name . I deleted the original
map, then added the 4 map sections, each with a hex grid.
The map image is still in the images directory of the module. That’s
why it’s being tiled the first time the module is loaded. If you’re not
using that image, remove it from the module using a ZIP archiver. (A
module is just a ZIP archive.)
So when the module loads, it attempts to load the non-existent map, and
‘hangs’ for about 10 to 30 seconds. Afterwards, the images complete
‘tiling’, and the modules works fine.
Nothing is hanging. There’s some work during tiling during which we
get no feedback from Java about progress, which is what you’re seeing.
Progress bars won’t be like this in VASSAL 4; I don’t want to sink
effort for smoothly estimating progress into VASSAL 3.2.
OK, I have an app called “The Unarchiver” which allows me access to the information contained in the module. But I don’t know or can’t seem to figure out, once I delete the unnecessary files, how to get it BACK into a vmod file.
I tried ‘compressing’ in (into a ZIP file) then changing the suffix but the VASSAL engine tells me that is an invalid VASSAL file when I attempt to open it.
OK, I have an app called “The Unarchiver” which allows me access to the
information contained in the module. But I don’t know or can’t seem to
figure out, once I delete the unnecessary files, how to get it BACK into
a vmod file.
I tried ‘compressing’ in (into a ZIP file) then changing the suffix but
the VASSAL engine tells me that is an invalid VASSAL file when I attempt
to open it.
Compare the directory structure of your original module with the one
you’ve recompressed. They will not be the same.
Agreed but that still does not allow me to open the recompressed file with VASSAL. Could it be a MAC thing and I’m using the “Unarchiver” but using MAC’s “Compress” feature thus perhaps not getting a ‘true’ ZIP file?
Agreed but that still does not allow me to open the recompressed file
with VASSAL. Could it be a MAC thing and I’m using the “Unarchiver” but
using MAC’s “Compress” feature thus perhaps not getting a ‘true’ ZIP
file?
I’ll tell you what’s misplaced in the recompressed file if you upload
it somewhere and provide a URL.
Must be LENIX issue. I can not return my unzipped file back into a vmod file that would allow my MAC and VASSAL 3.2.12.
When I unzip (by using my “The Unarchiver” app or iZip), I get a folder with all the images and other hints in the directory. I can delete unnecessary files.
Then when its time to return to a VASSAL file, I have used both the MAC ‘compress’ feature’ and the iZip feature to ‘re-zip’ the folder.
I tried to open the Zipped file directly from the engine, I tried simply changing the extension then using the engine, I tried trying to ‘open’ the folder. All without success.
Thus, obviously VASSAL requires a specific zipping/unzipping method that is associated with your LENIX machine.
Well, on a Mac, you can always use Unix tools if you are comfortable using
the command line.
You would get that by using the Terminal app in the Application > Utilities
folder.
Compare the directory structure of your original module with the one
you’ve recompressed. They will not be the same.
Agreed but that still does not allow me to open the recompressed file
with VASSAL. Could it be a MAC thing and I’m using the “Unarchiver” but
using MAC’s “Compress” feature thus perhaps not getting a ‘true’ ZIP
file?
Yes, I uploaded a working module. What I want to do is remove the extraneous items left over from using a previous module. I used my Chancellorsville module without realizing that the previous images and maps still remained. I’ll never do that again. I’ll always start with a brand spanking new module.
tar,
I am not comfortable going into terminal without someone holding my hand. Never was comfortable in MS-DOS.