Folks,
I’m running into problems when I try to start a game using a Vassal module created for playtesting the forthcoming GMT game The Supreme Commander. The module appears to load correctly, but when I attempt to create a game I get an Uncaught Exception error, details of which are copied below. Others can run this module with no problems. Similarly, I am able to run numerous other Vassal modules without issues. If anyone has any pointers to what the problem might be I would be most appreciative.
Thanks, Paul.
05 May 2009 20:07:24.994 0 – Starting
05 May 2009 20:07:24.996 0 – OS Mac OS X
05 May 2009 20:07:24.996 0 – Java version 1.5.0_16
05 May 2009 20:07:24.996 0 – VASSAL version 3.1.4
05 May 2009 20:07:25.213 0 – Manager
05 May 2009 20:09:56.731 0 – Loading module file /Users/pmarjora/Desktop/TSC v1.vmod
05 May 2009 20:09:56.734 0 – Loading module The Supreme Commander
05 May 2009 20:09:56.736 0 /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/bin/java -Xms256M -Xmx512M -DVASSAL.id=1 -cp /Users/pmarjora/Desktop/VASSAL-3.1.4.app/Contents/Resources/Java/Vengine.jar -Xdock:name=The Supreme Commander -Xdock:icon=/Users/pmarjora/Desktop/VASSAL-3.1.4.app/Contents/Resources/VASSAL.icns VASSAL.launch.Player
05 May 2009 20:09:59.271 1 – The Supreme Commander version 1.0
05 May 2009 20:09:59.271 1
05 May 2009 20:10:06.857 1 java.lang.IllegalArgumentException: Invalid ICC Profile Data
at java.awt.color.ICC_Profile.getInstance(ICC_Profile.java:753)
at com.sun.imageio.plugins.jpeg.JPEGImageReader.setImageData(JPEGImageReader.java:596)
at com.sun.imageio.plugins.jpeg.JPEGImageReader.readImageHeader(Native Method)
at com.sun.imageio.plugins.jpeg.JPEGImageReader.readNativeHeader(JPEGImageReader.java:554)
at com.sun.imageio.plugins.jpeg.JPEGImageReader.checkTablesOnly(JPEGImageReader.java:309)
at com.sun.imageio.plugins.jpeg.JPEGImageReader.gotoImage(JPEGImageReader.java:431)
at com.sun.imageio.plugins.jpeg.JPEGImageReader.readHeader(JPEGImageReader.java:547)
at com.sun.imageio.plugins.jpeg.JPEGImageReader.getWidth(JPEGImageReader.java:602)
at VASSAL.tools.image.ImageUtils.getImageSize(ImageUtils.java:323)
at VASSAL.tools.imageop.SourceOpBitmapImpl.getImageSize(SourceOpBitmapImpl.java:121)
at VASSAL.tools.imageop.SourceOpBitmapImpl.fixSize(SourceOpBitmapImpl.java:101)
at VASSAL.tools.imageop.AbstractOpImpl.getSize(AbstractOpImpl.java:128)
at VASSAL.build.module.map.boardPicker.Board.bounds(Board.java:593)
at VASSAL.build.module.Map.setBoardBoundaries(Map.java:1669)
at VASSAL.build.module.Map.setBoards(Map.java:736)
at VASSAL.build.module.map.BoardPicker.setup(BoardPicker.java:467)
at VASSAL.build.module.GameState.setup(GameState.java:269)
at VASSAL.build.module.WizardSupport.showWelcomeWizard(WizardSupport.java:200)
at VASSAL.launch.Player.launch(Player.java:88)
at VASSAL.launch.Launcher$1.run(Launcher.java:161)
at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:461)
at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:269)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:190)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:184)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:176)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:110)
I was looking at the bug report you field earlier this evening. What you’re
seeing is a combination of two problems:
Some JPEG in the module has a bad color profile. Unfortunately, I can’t
tell you which one, because the filename isn’t included in the error message.
If you fix that JPEG (opening it and resaving it in a program like The GIMP
would most likely be sufficient to fix it), the problem will go away.
When we check image dimensions, were not expecting corrupt images. I’m
planning to fix this for VASSAL 3.1.5.
The one you want is svn5566 or later. This doesn’t fix problem #1, but
now you should see a message in the chat pane telling you which image
is the offending one, so you’re not hunting blind.
I have now identified the corrupt image. If I unpack the module and correct the problematic file is there a simple way to repack the module so that Vassal can use it? I tried zipping the folder using Stuffit, and changing the extension to .vmod, but Vassal no longer recognizes it as a module.
Assuming from the use of Stuffit that you are on a Mac, you could
also try to use the built-in Zip utility. Apple has, however,
fiendishly disguised it by calling it “Create Archive of ” in
Tiger (10.4) and “Compress ” in Leopard (10.5). It is
available as a command in the Finder’s File menu. It will create a
standard zip file.
What I don’t know is if there is anything in Vassal that is linked to
the file size of the images that might be causing the resulting file
to not be recognized.