When an ADC2 module using PlaceNames for non-standard grid coordinates is converted to VASSAL, the hex coordinates were shown in the Search inventory, but not on the map as a Hex Grid. Tim McCarron showed how to put the coordinates on the VASSAL map as an Irregular Grid (Edit Module \ Map Window \ Map Boards \ Board \ Irregular Grid) so that when the pointer is over a hex, the coordinates show. The procedure is very labor intensive requiring about 20 actions to set one coordinate and with thousands of hexes, one can estimate the time required to fix even a moderate sized map.
Is there any way for VASSAL to transfer this information without making all those actions for each hex?
It would seem like a computer should be able to transfer the information rapidly and without a great deal of assistance from the operator. Is there a way?
Neither frequency of posting, nor hyperbole will help get your issues resolved Please remember, it is Christmas and many people are busy.
Michael Kiefte is the man you need to speak to about changes to the ADC2 to Vassal converter. He wrote and maintains that part of the code. He has been busy lately and we haven’t heard a lot from him. You might like to try pm’ing him directly via the forums. The ADC2 converter is designed to create a playable module that plays the same as the ADC2 version. There may well be issues with existing ADC2 modules (i.e. your issue with two different counters with the same name) that are not currently handled well by the converter. Michael is your man to follow up on these.
The Irregular Grid method is not ideal for reproducing grid co-ordinates. I am not sure what you are doing, but it certainly does not take 20 actions to create a grid point.
An existing Irregular grid can be transferred from one module to another by cut and paste of the buildfile. See the FAQ for details.
Can you post a screen shot of a section of the map showing the grid numberings? I may be able to suggest a way to help you. However, at that point, you are really committed to on-going manual maintenance of the modified module you have created. This may or may not be a good idea!
The only reason the irregular grid was used because it had an obscure
numbering system which the Vassal Hex grid cannot mimic. Im not sure but I
think it might be the old AH obique hex with diagonal numbering system. Isnt
there a class around to handle that? If so that would make life much easier
and simply plop a hex grid on instead of adding 100’s of irregular points to
make it match
That’s no problem, you just set up different zones for each section and add a separate grid for each ‘wrap section’. The big problem is which of the axes are used and in which direction. There are a lot of combinations.
It is the first time that I have posted to the Feature Requests. I have posted to the ConsimWorld VASSAL forum which was responded to by Tim McCarron as I indicated. I also posted a similar message on another VASSAL board asking if there was a better solution than that provided by Tim. This is the first time that I have posted requesting that the feature be corrected in VASSAL
The “20” comes from this: 1. Right click Irregular Grid. 2. Left click Add Region. 3. Move New Region window to a location where it will not be covered by the next window. 4 and 5. Double click next At-Start Stack. 6-9. Type new grid hex (3-4 digits). 10-13. Type Y coordinate (2-4) digits. 14-17. Type X coordinate (2-4) digits. 18. Close (OK) New Region window. 19. Close At-Start Stack window. 20. Delete At-Start stack. While there are hex coordinates with less than 4 digits, the majority, by far, are four digit. Try to correct a few and you will understand. There are exactly 2592 hexes on the ADC2 map.
I did e-mail Michael Kiefte a few months ago (20 Oct 09) as well as going over it with him in detail about a year ago. I have heard nothing from him recently and felt that perhaps others could help.
I am not a computer literate person, so the information that you can hopefully provide needs to be very detailed; such as that provided by Tim on ConsimWorld.
The modules that I am referring to is a different one than Blitzkrieg. It is Afrika Korps. Here is an image showing the converted module with the added grid coordinates. As you can see, the Allied supply unit uses the German supply unit symbol image. That is why I changed the ADC2 module and imported again to VASSAL.
Keep in mind that I am not computer literate; so don’t laugh too loud about this…
In ADC2 each hex (or square) has a number. The numbers begin in the upper left and go left to right and then down a row and left to right again and repeat. I think that all things revolve around this number. If a map grid is established, perhaps the grid coordinate replaces this number, but perhaps not also. Then that hex number is used to place map things and units and markers. So, hex number A has Primary Terrain, Secondary Terrain, Place Name, Additional Attritubes, Hex Lines and Hex Sides. These are fixed in the game and cannot be moved. Then Hex A could also have several moveable units and markers.
Essentially then the problem is to get the $Location$ from PLace Name rather than grid coordinate or Hex Number. You need a switch to tell the import program from which source to draw $location$ name – grid coordinate or place name. I think the tie between the two may be that ADC2 hex number.