I’m using version 3.1.0 of VASSAL, but this problem was occuring with the Beta release as well:
All my modules are working fine, except for one (Afrika II). It’s not a problem with the Module, because I’ve had others download it from the site and it works fine on their computers. I’ve also had someone email me their working version of the module, and it hasn’t worked on my computer.
Their working versions are the same version as mine, and are the exact same file size.
Here’s what’s happening: I’m not getting any information for 98% of the counters in the game, they appear as black. When I go into Edit Module, I don’t see any palette information (images) for the counters that are missing. I do see the information for the 2% of counters that aren’t black in the game…
In the [Game Pieces Palette], there is no mention of any counters whatsoever, except for the four counters that are appearing in the game.
I just unzipped the module and the counter images are there - I’ve just lost all reference to them. (This is the extent of my VASSAL knowledge, btw)
All my other modules are fine, I can’t understand how Afrika II seems to be losing counter information, only on my computer, and not on others’.
uckelman: I’ve set Afrika II with the following settings now, and restarted it, with the same problem, which I will describe below.
OFF: Prefer memory-mapped files for large images?
OFF: High quality scaling?
OFF: Disable DirectX D3D pipeline?
JVM initial heap: 256
JVM Maximum heap: 512
I start up VASSAL and double-click Afrika II. The startup wizard opens, I select either a saved game or start a new game (and select a pre-made setup).
The Markers (counters) window opens up. Its counters are visible (I assume because they’re scaled up, everything seems to work when it’s scaled up to full size). All other windows open fine. The map window opens up, the map takes a few moments to load, and the counters are all there, but they’re all black. (See attached image).
If I zoom out, the counters stay black. But if I zoom in, I can see the counters just fine. Also, if I leave my mouse pointer over a stack, the stack opens and I can see the counters just fine (see attached image).
There are no error messages in the Afrika II controls window.
Thanks for the detailed account of the problem. I’m certain now that this
has nothing at all to do with running out of memory. My guess is that it’s
another weird Windows graphics pipeline bug, either in Java or your video
What version of Java are you using? (You can check this by going to Help >
Show Error Log in the Module Manager, and looking for a line which says
“Java version …”)
Are you using the most up-to-date version of your video drivers?
With High Quality Scaling, the scaling is happening in software, in some
code I wrote. With that turned off, scaling is done either by Java or by
your video hardware. My guess is that your video hardware and Java are
not playing well together.
If you wouldn’t mind, I’d like to keep working on this with you, to see
if we can pin down exactly what the problem is. If you want to do this,
please do answer my question about your Java version and your video
This means that disabling of the D3D pipeline is off, which means that the D3D pipeline is actually on. There are at least one known (and other potential) bugs when the D3D pipeline is turned ON on a Windows machine. Could you please try turning this option ON, and see if this affects this problem you have when the High-quality scaling option is turned OFF?
Check on your video drivers and, if you update them, let us know if there’s
The current version of Java is 1.6.0_12, which has some Windows graphics
fixes in it. It’s possible that the problem won’t happen with that version;
after checking on your video drivers, try upgrading Java and check again.
If neither of those things eliminate the problem, then I have an idea of
something else to try, but I’d like to know the results of these first.
Just a quick update, I’m teaching a workshop using my laptop and a funky projector setup for the next week, so I don’t want to mess with my drivers or anything until I’m finished. But I -will- get back to you.