Vassal always tiles image files

Vassal seems to always tile image file when loading modules even though no graphics files have been changed. It’s not module specific.

Dell XPS 8500
12.0 GM Menory, 64-bit Windows 7
NVIDIA GeForce GT 620
Vassal 3.2.17
Java Version 1.8.0_251

  • SCS Panzer Battles - Chir River version 1.00
  • Loading PB Scen 2-1.vsav …
  • Loaded PB Scen 2-1.vsav

https://forum.vassalengine.org/t/module-keeps-tiling/10719/2

We have not been able to track down why this happens, but it seems to be limited to Windows machines.

An older response thought it was due to files being out of date, which is why I made the comment. Naturally, if the graphics files were updated, then it would be correct to re-tile the image.

Some Windows file properties must be involved, which Java is interrogating.

I just tried loading a Vassal module that I hadn’t accessed in quite some time (2011), and it wasn’t re-tiling.

The problem seems to be prominent in modules for which I have recently edited the graphics files.

I looked at a tiling module, and the module is not in the folder with the graphics files. Vassal could store the paths of the internal graphics files, but then there would be a problem if the file on disk was no longer there. Perhaps it’s due to the date of the module itself.

MODULE Dates:
2017 re-tiles
2016 re-tiles
2020 did not re-tile

So that’ not necessarily the answer.

Maybe someone could look at the re-tiling logic to see what’s being queried …

Have you tried clearing the Tile Cache completely?

Thus spake Hagar:

An older response thought it was due to files being out of date, which
is why I made the comment. Naturally, if the graphics files were
updated, then it would be correct to re-tile the image.

Some Windows file properties must be involved, which Java is
interrogating.

I just tried loading a Vassal module that I hadn’t accessed in quite
some time (2011), and it wasn’t re-tiling.

The problem seems to be prominent in modules for which I have recently
edited the graphics files.

I looked at a tiling module, and the module is not in the folder with
the graphics files. Vassal could store the paths of the internal
graphics files, but then there would be a problem if the file on disk
was no longer there. Perhaps it’s due to the date of the module itself.

MODULE Dates:
2017 re-tiles
2016 re-tiles
2020 did not re-tile

So that’ not necessarily the answer.

Maybe someone could look at the re-tiling logic to see what’s being
queried …

If you have a module where the problem is reproducible every time,
it would help us troubleshoot if we could have that module.


J.

Based on the comments that are displayed when you do this, it seems that clearing cache is the thing you DON’T want to do.
But I went ahead and cleared the cache. It takes a long time to go through all the files.

Nonetheless, sometimes, upon first load, it re-tiles. Upon second load, it doesn’t re-tile. (This is what you would expect.)
Others re-tile all the time. Seems to be module specific.

I’ll send you a module where this it repeatable.

Have a look here: https://forum.vassalengine.org/t/module-keeps-tiling/10719/1

It seems to happen occasionally on Windows when saving a module. If that module is then distributed, everyone who receives it will get the same problem.

You can fix a specific module by unzipping it, updating the DTM stamp on all files, then rezipping the module.

Thus spake Brent Easton:

Have a look here: viewtopic.php?f=3&t=11954[1]

It seems to happen occasionally on Windows when saving a module. If that
module is then distributed, everyone who receives it will get the same
problem.

You can fix a specific module by unzipping it, updating the DTM stamp on
all files, then rezipping the module.

Before you fix the moduld you have, I’d like a copy, so I can see one which
triggers the problem reliably.


J.

After clearing Cache, most modules tiled first, then did not tile on subsequent loads – as expected.
After a lot of testing, the problem may seem to be related to modules that I have made or modified.
If so, then it may be an OS/file attributes problem. If the problem doesn’t manifest itself on your computer, that may be an answer.

Had to try and find the smallest module I could for upload, as many of them are quite large.
Hopefully, this will illustrate the problem (or not).

It always re-tiles upon activation.

File is 10761 kb. Says file is too big.

Alternative upload is here: vassalengine.org/wiki/Special:Upload

Sent.

Following up here: Is this still a problem?