# Vassal always tiles image files

**URL:** <https://forum.vassalengine.org/t/vassal-always-tiles-image-files/10783>\
**Category:** Technical Support & Bugs\
**Created:** [June 27, 2020, 11:05pm UTC](https://forum.vassalengine.org/t/vassal-always-tiles-image-files/10783 "2020-06-27T23:05:50Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![Hagar](https://forum.vassalengine.org/user_avatar/forum.vassalengine.org/hagar/32/50_2.png) [@Hagar](https://forum.vassalengine.org/u/Hagar)\
**Post date:** [June 27, 2020, 11:05pm UTC](https://forum.vassalengine.org/t/vassal-always-tiles-image-files/10783/1 "2020-06-27T23:05:50Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![Brent\_Easton](https://forum.vassalengine.org/user_avatar/forum.vassalengine.org/brent_easton/32/10_2.png) [@Brent\_Easton](https://forum.vassalengine.org/u/Brent_Easton)\
**Post date:** [June 28, 2020, 12:18am UTC](https://forum.vassalengine.org/t/vassal-always-tiles-image-files/10783/2 "2020-06-28T00:18:36Z")

</div>

[https://forum.vassalengine.org/t/module-keeps-tiling/10719/2](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.

---

<div class="post-metadata">

**Author:** ![Hagar](https://forum.vassalengine.org/user_avatar/forum.vassalengine.org/hagar/32/50_2.png) [@Hagar](https://forum.vassalengine.org/u/Hagar)\
**Post date:** [June 28, 2020, 7:09pm UTC](https://forum.vassalengine.org/t/vassal-always-tiles-image-files/10783/3 "2020-06-28T19:09:41Z")

</div>

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 …

---

<div class="post-metadata">

**Author:** ![JoelCFC25](https://forum.vassalengine.org/user_avatar/forum.vassalengine.org/joelcfc25/32/2687_2.png) [@JoelCFC25](https://forum.vassalengine.org/u/JoelCFC25)\
**Post date:** [June 28, 2020, 7:35pm UTC](https://forum.vassalengine.org/t/vassal-always-tiles-image-files/10783/4 "2020-06-28T19:35:07Z")

</div>

Have you tried clearing the Tile Cache completely?

---

<div class="post-metadata">

**Author:** ![uckelman](https://forum.vassalengine.org/user_avatar/forum.vassalengine.org/uckelman/32/10020_2.png) [@uckelman](https://forum.vassalengine.org/u/uckelman)\
**Post date:** [June 28, 2020, 8:52pm UTC](https://forum.vassalengine.org/t/vassal-always-tiles-image-files/10783/5 "2020-06-28T20:52:29Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![Hagar](https://forum.vassalengine.org/user_avatar/forum.vassalengine.org/hagar/32/50_2.png) [@Hagar](https://forum.vassalengine.org/u/Hagar)\
**Post date:** [July 2, 2020, 11:59pm UTC](https://forum.vassalengine.org/t/vassal-always-tiles-image-files/10783/6 "2020-07-02T23:59:27Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![Brent\_Easton](https://forum.vassalengine.org/user_avatar/forum.vassalengine.org/brent_easton/32/10_2.png) [@Brent\_Easton](https://forum.vassalengine.org/u/Brent_Easton)\
**Post date:** [July 3, 2020, 12:10am UTC](https://forum.vassalengine.org/t/vassal-always-tiles-image-files/10783/7 "2020-07-03T00:10:53Z")

</div>

Have a look here: [https://forum.vassalengine.org/t/module-keeps-tiling/10719/1](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.

---

<div class="post-metadata">

**Author:** ![uckelman](https://forum.vassalengine.org/user_avatar/forum.vassalengine.org/uckelman/32/10020_2.png) [@uckelman](https://forum.vassalengine.org/u/uckelman)\
**Post date:** [July 3, 2020, 12:15am UTC](https://forum.vassalengine.org/t/vassal-always-tiles-image-files/10783/8 "2020-07-03T00:15:46Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![Hagar](https://forum.vassalengine.org/user_avatar/forum.vassalengine.org/hagar/32/50_2.png) [@Hagar](https://forum.vassalengine.org/u/Hagar)\
**Post date:** [July 3, 2020, 5:48pm UTC](https://forum.vassalengine.org/t/vassal-always-tiles-image-files/10783/9 "2020-07-03T17:48:31Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![Cattlesquat](https://forum.vassalengine.org/user_avatar/forum.vassalengine.org/cattlesquat/32/241_2.png) [@Cattlesquat](https://forum.vassalengine.org/u/Cattlesquat)\
**Post date:** [July 3, 2020, 5:51pm UTC](https://forum.vassalengine.org/t/vassal-always-tiles-image-files/10783/10 "2020-07-03T17:51:46Z")

</div>

Alternative upload is here: [vassalengine.org/wiki/Special:Upload](http://www.vassalengine.org/wiki/Special:Upload)

---

<div class="post-metadata">

**Author:** ![Hagar](https://forum.vassalengine.org/user_avatar/forum.vassalengine.org/hagar/32/50_2.png) [@Hagar](https://forum.vassalengine.org/u/Hagar)\
**Post date:** [July 3, 2020, 6:17pm UTC](https://forum.vassalengine.org/t/vassal-always-tiles-image-files/10783/11 "2020-07-03T18:17:47Z")

</div>

Sent.

---

<div class="post-metadata">

**Author:** ![uckelman](https://forum.vassalengine.org/user_avatar/forum.vassalengine.org/uckelman/32/10020_2.png) [@uckelman](https://forum.vassalengine.org/u/uckelman)\
**Post date:** [May 27, 2021, 10:23pm UTC](https://forum.vassalengine.org/t/vassal-always-tiles-image-files/10783/12 "2021-05-27T22:23:41Z")

</div>

Following up here: Is this still a problem?
