Hi
When I open a module with the new version there is a “tiling images”. What 's this exactly and when is it done? Always when opening?
Thus spake Donegal:
Hi
When I open a module with the new version there is a “tiling images”.
What 's this exactly and when is it done? Always when opening?
Starting with 3.2, we slice large images into pieces (“tiles”) which
are stored on disk, in order to avoid image decoding and scaling while
you use VASSAL.
Tiling should happen only when the tiles for a module aren’t present
in the tile cache, i.e., the first time you open a module, and
thereafter if you modify the images in the module.
–
J.
I made a module for a certain collectable card game (not planning on releasing it; it’s just for me personally). The cards are 215MB, which is tolerable (for me), but the tiles are 2.55 GB! That’s giga … which is insane.
In light of that, I’d rather prefer the image decoding & scaling in-game. Is there any way to force tiles not to be made & revert to the old method of in-game decoding & scaling? I do like the new features from v3.2, so I’d like to play with it (and not an older version) if possible.
Thus spake demagogue:
I made a module for a certain collectable card game (not planning on
releasing it; it’s just for me personally). The cards are 215MB, which
is tolerable (for me), but the tiles are 2.55 GB! That’s giga … which
is insane.
Drive space is cheap these days. It’s not unreasonable to use that much
space for tiling.
In light of that, I’d rather prefer the image decoding & scaling
in-game. Is there any way to force tiles not to be made & revert to the
old method of in-game decoding & scaling? I do like the new features
from v3.2, so I’d like to play with it (and not an older version) if
possible.
No, there’s no way to prevent the tiles from being written to disk
without modifying the code.
V4 will do all of the tiling in-memory, so this won’t be an issue
for you then.
–
J.
Yeah in the big scheme of things it’s not too much. It’s only because my HD filled up & I’m living abroad right now, and it’s not easy to get an external HD where I’m at. Thanks for the answer. It’s easy to just use the old version for that one game, wait till I get back to the US to get a new HD, and very nice to hear v4 makes it a moot issue eventually anyway. Cheers. 
So - where the heck is this “tile cache” on disk
I don’t like it when programs “hide” things from the owner of the machine 
Thus spake Fre20741:
So - where the heck is this “tile cache” on disk
I don’t like it when programs “hide” things from the oner of the machine
The tile cache is not hidden. It’s in the directory where VASSAL stores
its user data (along with preferences and the errorLog and such), the
location of which follows the standard practice for the various
platforms on which VASSAL runs.
Look here for the location of VASSAL’s user data:
vassalengine.org/wiki/Error_Logs
The tile cache is in the “tiles” subdirectory.
–
J.
Placing this data in a directory structure which is by default hidden from the user by the operating system qualifies as being “hidden” in my book of definitions. But thank you for the hint of where to look