Strange how I can’t find an answer for this, especially since it happened before, but the only fix back then does not work now! This hasn’t happened for 4 years!
Building a new module, working on it feverishly for the last week. I am close to finishing the first draft for playtesting, and now the map WILL NOT SHOW!
The map shows when editing grids and zones, but when starting a new game, either in editing or in a regular game, the map does not show! I know it’s there, because all of the commands to send units to a particular zone or region on the map still works and I get no error when saving. I also know it’s there because, when I take a picture of the map, I get the map. I just can’t see the map when starting a game.
I have 64GB of memory, and I have the MAX HEAP set to 48GB. None of this was changed when it happened, it just disappeared when I went to start a new game while editing.
I’m guessing it’s something simple I either did or am missing, but I can’t think of what that would be.
PLEASE HELP!!!
System Info:
Win 11 Home
Intel i9-10900K
64GB RAM
NVIDIA RTX 4070 w/12GB with latest drivers
Have you unintentionally ticked the box in the Map Window’s config for “include toolbar button to show/hide”? Failing that and the idea above about the divider, it will likely speed up diagnosis considerably if you can upload your work-in-progress module to some form of cloud storage (Google Drive, Dropbox, OneDrive et al) and provide a link.
Could it be too many toolbar buttons? I noticed the map disappeared right after added a toolbar button. I’ll try and use a multi-action button to see if that works.
Okay, this is just beyond frustrating! I replaced the map in this module, everything worked just fine when opening and closing the module - editing and playing straight-up. I come back this morning, go to further edit, and now THAT map won’t open! I can’t even begin to imagine what the heck is going on with this module, and the only recourse I have is to start from scratch, but I have about 40 hours of work in this module.
is last in the buildFile.xml. For some reason, this makes the board disappear. I guess VASSAL parses the XML DOM via SAX, and when it encounters the GlobalOptions, it resets a number of things - including the board. Note, the board is still there (take a screenshot using the camera button and you will see it). Another way to use XML is to use it as a database - that is, as a look-up table.
To fix your issue
Open the module in the VASSAL editor
Scroll down to the [Global Options] element
Right click it and select Move
From the drop-down, select 3: Main Map [Map Window] and then OK.
Save the module
Now, when you open the module again, you should see your map.
Also, you have some hidden characters - particular U+202D - in some file names which can mess things up too. These kind of characters are often put in by Windoze or MacOuze opaquely - and are quite annoying. Perhaps VASSAL should aim at “sanitising” file names before adding them to the module.
Wow! Thanks for tracking this down! I will check this out, although I went a different route and basically rebuilt the module from the ground up using some different interfaces, but this is great to know if I encounter it again!
Where can I donate to the Vassal development team?
It is a Logistics-focused game created by one of our Masters students. I will send you the rules with my “vassalized” addendum with a link to the game once I finish the first draft. Thanks again for the assist!
