Map Flashes On and Off in Map Editor

What causes a map to flash on and off while you are in the map editor adding Zones? Currently using 3.4.12 for this build.

A likely culprit is the image cache clearing due to too little remaining heap. Try setting your max heap higher.

Also, 3.4.12 is neither current, nor the last 3.4. release. We recommend using the current release, especially if you’re editing a module.

I have converted this module to 3.5.7 My map continues to flash on and off

I am getting the following Errors from the Logs:

2021-06-26 04:03:58,491 [4708-main] INFO VASSAL.launch.StartUp - Starting
2021-06-26 04:03:58,553 [4708-main] INFO VASSAL.launch.StartUp - OS Windows 7 6.1
2021-06-26 04:03:58,569 [4708-main] INFO VASSAL.launch.StartUp - Java version 16
2021-06-26 04:03:58,569 [4708-main] INFO VASSAL.launch.StartUp - VASSAL version 3.5.7
2021-06-26 04:03:58,850 [4708-AWT-EventQueue-0] INFO VASSAL.launch.ModuleManager - Manager
2021-06-26 04:04:25,179 [4708-AWT-EventQueue-0] ERROR VASSAL.launch.AbstractLaunchAction - – Load of H:\SCARBOROUGH\Useable Counters\WaterlooNapoleonsLastBattlev2.vmod failed: Not a Vassal module
2021-06-26 04:18:45,852 [4708-SwingWorker-pool-3-thread-1] INFO VASSAL.launch.AbstractLaunchAction - Loading module file H:\SCARBOROUGH\Useable Counters\WaterlooNapoleonsLastBattle.vmod
2021-06-26 04:18:46,413 [4708-SwingWorker-pool-3-thread-1] INFO VASSAL.tools.io.ProcessLauncher - launching C:\Program Files\VASSAL-3.5.7\jre\bin\java -classpath lib\Vengine.jar -Xmx749M -Duser.home=C:\Users\Tom -DVASSAL.port=51892 VASSAL.tools.image.tilecache.ZipFileImageTiler H:\SCARBOROUGH\Useable Counters\WaterlooNapoleonsLastBattle.vmod C:\Users\Tom\AppData\Roaming\VASSAL\tiles\679b51b05c920077faa13a08dfe9f102d88ef062 256 256
2021-06-26 04:18:48,582 [5356-main] INFO VASSAL.tools.image.tilecache.ZipFileImageTiler - Starting
2021-06-26 04:18:48,894 [5356-main] INFO VASSAL.tools.image.tilecache.FileArchiveImageTiler - Tiling images/British Set Up.PNG
2021-06-26 04:18:54,716 [5356-main] INFO VASSAL.tools.image.tilecache.FileArchiveImageTiler - Tiling images/French Set Up.PNG
2021-06-26 04:19:00,022 [5356-main] INFO VASSAL.tools.image.tilecache.FileArchiveImageTiler - Tiling images/Player Aid Card CORRECTED.jpg
2021-06-26 04:19:09,850 [5356-main] INFO VASSAL.tools.image.tilecache.FileArchiveImageTiler - Tiling images/Prussian Reinforcements.PNG
2021-06-26 04:19:14,998 [5356-main] INFO VASSAL.tools.image.tilecache.FileArchiveImageTiler - Tiling images/Waterloo Map ReSized PRIME.jpg
2021-06-26 04:19:23,328 [5356-main] INFO VASSAL.tools.image.FallbackImageTypeConverter - Switching to FileImageTypeConverter…
2021-06-26 04:21:13,465 [5356-main] INFO VASSAL.tools.image.tilecache.ZipFileImageTiler - Exiting
2021-06-26 04:21:13,621 [4708-SwingWorker-pool-3-thread-1] INFO VASSAL.launch.AbstractLaunchAction - Loading module Waterloo Napoleon’s Last Battle
2021-06-26 04:21:13,636 [4708-SwingWorker-pool-3-thread-1] INFO VASSAL.tools.io.ProcessLauncher - launching C:\Program Files\VASSAL-3.5.7\jre\bin\java -Xms512M -Xmx512M -Duser.home=C:\Users\Tom -Duser.dir=C:\Program Files\VASSAL-3.5.7 -cp lib\Vengine.jar VASSAL.launch.Editor --edit – H:\SCARBOROUGH\Useable Counters\WaterlooNapoleonsLastBattle.vmod
2021-06-26 04:21:15,898 [6640-main] INFO VASSAL.launch.StartUp - Starting
2021-06-26 04:21:15,961 [6640-main] INFO VASSAL.launch.StartUp - OS Windows 7 6.1
2021-06-26 04:21:15,961 [6640-main] INFO VASSAL.launch.StartUp - Java version 16
2021-06-26 04:21:15,961 [6640-main] INFO VASSAL.launch.StartUp - VASSAL version 3.5.7
2021-06-26 04:21:15,976 [6640-main] INFO VASSAL.launch.Launcher - Editor
2021-06-26 04:21:20,859 [6640-AWT-EventQueue-0] INFO VASSAL.build.GameModule - Waterloo Napoleon’s Last Battle version v1.0
2021-06-26 04:28:05,452 [6640-AWT-EventQueue-0] INFO VASSAL.tools.io.ProcessLauncher - launching C:\Program Files\VASSAL-3.5.7\jre\bin\java -classpath lib\Vengine.jar -Duser.dir=C:\Program Files\VASSAL-3.5.7 VASSAL.launch.ModuleManager --update-module H:\SCARBOROUGH\Useable Counters\WaterlooNapoleonsLastBattlev2.vmod
2021-06-26 07:54:02,289 [6640-AWT-EventQueue-0] INFO VASSAL.tools.io.ProcessLauncher - launching C:\Program Files\VASSAL-3.5.7\jre\bin\java -classpath lib\Vengine.jar -Duser.dir=C:\Program Files\VASSAL-3.5.7 VASSAL.launch.ModuleManager --update-module H:\SCARBOROUGH\Useable Counters\WaterlooNapoleonsLastBattlev2.vmod
2021-06-26 08:36:42,944 [6640-AWT-EventQueue-0] INFO VASSAL.tools.io.ProcessLauncher - launching C:\Program Files\VASSAL-3.5.7\jre\bin\java -classpath lib\Vengine.jar -Duser.dir=C:\Program Files\VASSAL-3.5.7 VASSAL.launch.ModuleManager --update-module H:\SCARBOROUGH\Useable Counters\WaterlooNapoleonsLastBattlev2.vmod
2021-06-26 08:57:10,697 [6640-AWT-EventQueue-0] INFO VASSAL.tools.io.ProcessLauncher - launching C:\Program Files\VASSAL-3.5.7\jre\bin\java -classpath lib\Vengine.jar -Duser.dir=C:\Program Files\VASSAL-3.5.7 VASSAL.launch.ModuleManager --update-module H:\SCARBOROUGH\Useable Counters\WaterlooNapoleonsLastBattlev2.vmod
2021-06-26 09:53:34,195 [6640-AWT-EventQueue-0] INFO VASSAL.tools.io.ProcessLauncher - launching C:\Program Files\VASSAL-3.5.7\jre\bin\java -classpath lib\Vengine.jar -Duser.dir=C:\Program Files\VASSAL-3.5.7 VASSAL.launch.ModuleManager --update-module H:\SCARBOROUGH\Useable Counters\WaterlooNapoleonsLastBattlev2.vmod
2021-06-26 10:21:57,314 [6640-AWT-EventQueue-0] INFO VASSAL.tools.io.ProcessLauncher - launching C:\Program Files\VASSAL-3.5.7\jre\bin\java -classpath lib\Vengine.jar -Duser.dir=C:\Program Files\VASSAL-3.5.7 VASSAL.launch.ModuleManager --update-module H:\SCARBOROUGH\Useable Counters\WaterlooNapoleonsLastBattlev2.vmod

JVM initial heap (in MB) 8192
JVM maximum heap (in MB) 16348

Disable DirectX D3D pipeline? … I have not done this as I don’t know what this could do to the rest of the computer.

As for the ability to increase RAM, I’m working on a laptop. I do not know if I can increase the RAM.

The map flashing on and off continues.

  • There’s no initial heap setting in 3.5.7. (That was removed in 3.5.4.) Where are you seeing that?

  • 16GB is far, far too large for a maximum heap setting unless you have a colossal map. I’m not sure I could even find a published module that requires more than 1GB. If you have your max heap set to something that’s causing your OS to do a lot of swapping, that could give you effects similar to having a max heap which is too small—in both cases, image data isn’t ready when it’s needed so display of it is delayed.

  • This line in the error log shows that you’re not launching with the heap size you think you are:

The “-Xmx512M” there indicates your max heap is 512MB, which may be too small for the module you’re editing. 512MB is the failsafe used when you’ve specified a max heap which is too large to fit into available RAM, so if you don’t have somewhat more than 16GB of RAM, that would explain why you think you’re running with 16GB max heap but only getting 512MB.

I suggest trying a max heap of 768MB or 1024MB, and then checking in the error log after a restart that you are in fact running with the max heap you’ve set.

It can’t do anything to the rest of the computer. It controls only whether VASSAL uses D3D. It’s probably not relevant for your situation; usually people need this when they’re getting tearing on repaints, which isn’t what you’ve reported.

Ok, have changed the preferences to

This is in the Preferences / Importer window
JVM initial heap (in MB) 1024
JVM Maximum heap (in MB) 2048

Errors Logs Now Read:

2021-06-26 11:40:07,887 [6484-main] INFO VASSAL.launch.StartUp - Starting
2021-06-26 11:40:07,950 [6484-main] INFO VASSAL.launch.StartUp - OS Windows 7 6.1
2021-06-26 11:40:07,950 [6484-main] INFO VASSAL.launch.StartUp - Java version 16
2021-06-26 11:40:07,950 [6484-main] INFO VASSAL.launch.StartUp - VASSAL version 3.5.7
2021-06-26 11:40:08,246 [6484-AWT-EventQueue-0] INFO VASSAL.launch.ModuleManager - Manager
2021-06-26 11:40:53,852 [6484-SwingWorker-pool-2-thread-1] INFO VASSAL.launch.AbstractLaunchAction - Loading module file H:\SCARBOROUGH\Useable Counters\WaterlooNapoleonsLastBattlev2.vmod
2021-06-26 11:40:54,352 [6484-SwingWorker-pool-2-thread-1] INFO VASSAL.tools.io.ProcessLauncher - launching C:\Program Files\VASSAL-3.5.7\jre\bin\java -classpath lib\Vengine.jar -Xmx749M -Duser.home=C:\Users\Tom -DVASSAL.port=52904 VASSAL.tools.image.tilecache.ZipFileImageTiler H:\SCARBOROUGH\Useable Counters\WaterlooNapoleonsLastBattlev2.vmod C:\Users\Tom\AppData\Roaming\VASSAL\tiles\2860012e6f91cd1aa83c31c19628f1f337ecf1de 256 256
2021-06-26 11:40:56,380 [6000-main] INFO VASSAL.tools.image.tilecache.ZipFileImageTiler - Starting
2021-06-26 11:40:56,582 [6000-main] INFO VASSAL.tools.image.tilecache.FileArchiveImageTiler - Tiling images/British Set Up.PNG
2021-06-26 11:41:00,545 [6000-main] INFO VASSAL.tools.image.tilecache.FileArchiveImageTiler - Tiling images/French Set Up.PNG
2021-06-26 11:41:03,337 [6000-main] INFO VASSAL.tools.image.tilecache.FileArchiveImageTiler - Tiling images/Player Aid Card CORRECTED.jpg
2021-06-26 11:41:10,482 [6000-main] INFO VASSAL.tools.image.tilecache.FileArchiveImageTiler - Tiling images/Prussian Reinforcements.PNG
2021-06-26 11:41:13,105 [6000-main] INFO VASSAL.tools.image.tilecache.FileArchiveImageTiler - Tiling images/Waterloo Map ReSized PRIME.jpg
2021-06-26 11:41:16,976 [6000-main] INFO VASSAL.tools.image.FallbackImageTypeConverter - Switching to FileImageTypeConverter…
2021-06-26 11:42:20,763 [6000-main] INFO VASSAL.tools.image.tilecache.ZipFileImageTiler - Exiting
2021-06-26 11:42:20,889 [6484-SwingWorker-pool-2-thread-1] INFO VASSAL.launch.AbstractLaunchAction - Loading module Waterloo Napoleon’s Last Battle
2021-06-26 11:42:20,905 [6484-SwingWorker-pool-2-thread-1] INFO VASSAL.tools.io.ProcessLauncher - launching C:\Program Files\VASSAL-3.5.7\jre\bin\java -Xms512M -Xmx512M -Duser.home=C:\Users\Tom -Duser.dir=C:\Program Files\VASSAL-3.5.7 -cp lib\Vengine.jar VASSAL.launch.Editor --edit – H:\SCARBOROUGH\Useable Counters\WaterlooNapoleonsLastBattlev2.vmod
2021-06-26 11:42:22,153 [2948-main] INFO VASSAL.launch.StartUp - Starting
2021-06-26 11:42:22,184 [2948-main] INFO VASSAL.launch.StartUp - OS Windows 7 6.1
2021-06-26 11:42:22,184 [2948-main] INFO VASSAL.launch.StartUp - Java version 16
2021-06-26 11:42:22,184 [2948-main] INFO VASSAL.launch.StartUp - VASSAL version 3.5.7
2021-06-26 11:42:22,184 [2948-main] INFO VASSAL.launch.Launcher - Editor
2021-06-26 11:42:25,430 [2948-AWT-EventQueue-0] INFO VASSAL.build.GameModule - Waterloo Napoleon’s Last Battle version v2.0

Map continues to flash on and off.

Thanks for showing me where that initial heap came from. That setting was supposed to have been removed in 3.5.4 but was missed. I’ve removed it now, so it will be gone in 3.5.8. (Regardless, it stopped doing anything as of 3.5.4.)

These aren’t the heap settings for the module, but for the Importer, which converts other formats to VASSAL’s. (Presently only conversions from AdC2 are supported.) Nothing you set here will affect the max heap for the module you’re loading.

As you can see here,

changing the Importer heap settings had no effect on the module’s heap settings—because they’re two completely different things.

The max heap setting you need to change is the one for the module. You’ll find that in the Preferences in the Player window, after you’ve opened the module. After setting the max heap there, close the module and open it again. You should find that your change has taken effect then.

As expected, since you’re still using the same max heap for loading the module.

Thanks for telling me where to change the heap size. I’d have never found it buried in there. Might be a good idea to pin this piece of advice somewhere prominent.