REALLY huge .vassal/tiles: what to do ?

Technical Support & Bugs
1

well, I have around a rather huge .vassal/tiles (I use Linux) directory, current of a whopping 4,4+ Gb, how one can reduce the size ?

Best regards from Italy,
dott. Piergiorgio.

2

Thus spake “dott.Piergiorgio”:

well, I have around a rather huge .vassal/tiles (I use Linux) directory,
current of a whopping 4,4+ Gb, how one can reduce the size ?

You could delete it.

–
J.

3

Curses! I found my delete key!

-----Original Message-----
From: messages-bounces@vassalengine.org
[mailto:messages-bounces@vassalengine.org] On Behalf Of Joel Uckelman
Sent: Saturday, February 23, 2013 3:41 AM
To: The mailing list for VASSAL
Subject: Re: [messages] [Technical Support & Bugs] REALLY huge
.vassal/tiles: what to do ?

Thus spake “dott.Piergiorgio”:

well, I have around a rather huge .vassal/tiles (I use Linux)
directory, current of a whopping 4,4+ Gb, how one can reduce the size ?

You could delete it.

–
J.

4

Thanks; and as expected, the tile cache is rebuilt at the next start of the modules…

There’s no issues, vassal-side, in adding .VASSAL/tiles/* in the automated purge list and leave the house cleaning to anacron, aside the rebuilding after ?

so, a suggestion: an option for enabling an automatic clearing of this tile cache at end of the session, better if allows for setting a selective list of tile caches to kept around, e.g. that of modules for monster games or for games with a very large counter/map manifest (e.g.VSQL and VASQL)

I always try/test new or interesting modules (and opening modules in edit mode and looking around…) also for a “try before you buy” sort of approach to new games, so I add new modules very frequently (current count, ~120 modules, hope that there’s no signed char inside Vassal’s module list/selection window :wink: )

Best regards from Italy,
dott. Piergiorgio.

5

Thus spake “dott.Piergiorgio”:

so, a suggestion: an option for enabling an automatic clearing of this
tile cache at end of the session, better if allows for setting a
selective list of tile caches to kept around, e.g. that of modules for
monster games or for games with a very large counter/map manifest
(e.g.VSQL and VASQL)

If someone wants to write code which handles expiring the tile cache,
I’ll consider including it.

–
J.

6

Im not sure I understand the point of the request. Tiling commences when a
module is first loaded and run in a users library, at which point you do not
want to run it again unless version difference detection occurs with the
same file module name.

Then the tiles are removed if the module is unloaded from the library

So my question is, why do you want to remove the tiles if you intend to keep
the module in your library for future use?

It’s kind of redundant to require rebuilding and unloading the tile cache
for a module version each time you run it / unload it

Tim

-----Original Message-----
From: messages-bounces@vassalengine.org
[mailto:messages-bounces@vassalengine.org] On Behalf Of Joel Uckelman
Sent: Tuesday, February 26, 2013 3:59 PM
To: The mailing list for VASSAL
Subject: Re: [messages] [Technical Support & Bugs] REALLY huge
.vassal/tiles: what to do ?

Thus spake “dott.Piergiorgio”:

so, a suggestion: an option for enabling an automatic clearing of this
tile cache at end of the session, better if allows for setting a
selective list of tile caches to kept around, e.g. that of modules for
monster games or for games with a very large counter/map manifest
(e.g.VSQL and VASQL)

If someone wants to write code which handles expiring the tile cache, I’ll
consider including it.

–
J.

7

@Tim: This computer isn’t only for VASSAL… and I’m capable of filling to near 100% my HD without resorting to games, videos and like, so the need of hunting for cruft and storing offline unneded/redundant material happens often enough… I have thrice bringed my HD from even <900 MB to ~10-20 GB during last month; also, if you care to notice, inside /tiles the tiles are stored with random filenames, so one can’t do a manual selective purging (roughly, of the ~130 modules I have, I actively use 20 or so, and another 20 or so is in a sort of “shareware trial” (remember, I live with seven cats, and having a VASSAL module is a prerequisite for being considered to buy) and ~40 are of modules of wg’s I actually own but don’t use frequently, and the remaining 60 or so are either “rejected shareware” waiting for deletion, WIPs and modules with interesting features I kept around as “source code examples” repository…

Hope to have explained the rationale of my inquring about /tiles…

Best regards from Italy,
dott. Piergiorgio.