You do not actually *need* the hexgrid in VASSAL. That will limit the things you can automate, but will not affect the game itself. If you only want to create a super quick game to play with friends you can get by without using 99% of VASSAL's features. However, if this is a game you'll want to post for others to use, people expect certain "features" to be present. One of those expectation is for VASSAL to report moves--ie "Unit XXX moves from 0019 to 1217." VASSAL will do this, if you have a hexgrid defined. Another expectation is that units will snap to the center of the hexes so the map will not get messy from sloppily placed counters--again defining a hexgrid will allow VASSAL to *automatically* align counters within a hex. The defined hexgrid in VASSAL, allows VASSAL to "see" where counters are being moved, as well as keep the map clean. It allows things like moving to specific locations, reporting movement, and centering (or offsetting for that matter. --guy
________________________________ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of wolfwolf4242 Sent: Friday, August 04, 2006 11:14 AM To: [email protected] Subject: [vassalengine] Re: Pre-made maps Gary, If you can elaborate more that would be great. I think what I am not getting is why we need the VASSAL hexgrid if a hexgrid has been already drawn on the map in my grpahics program. Thanks Jeff --- In [email protected] <mailto:vassalengine%40yahoogroups.com> , Gary Krockover <[EMAIL PROTECTED]> wrote: > > I put hexgrids on all of my maps now - this gives me a bit more control than what is generated in VASSAL. For example, for this map that I'm working on, the hexgrid over the water is one color, and over the land another: > > http://www.garykrockover.com/uploads/EOTID-WIP-Italy.jpg <http://www.garykrockover.com/uploads/EOTID-WIP-Italy.jpg> > > What my tutorial starts to show (I need to finish that one of these days) is that I first generate the hexgrid in VASSAL on a blank map. I then save that map as a png (using VASSAL) and then grab the black color of the hexgrid and add that as a layer to my scanned image of the map that I'm making. I then stretch, skew, rotate and otherwise fit the scanned map to the hexgrid from VASSAL. I then use that hex grid and color it or do what I want and lay it on top of the map that I'm making. This way, when it's all done, I open up that module that had my blank map and then add the map that I drew. I leave the hexgrid enabled, but I uncheck the box that asks to draw the grid. So, the grid is there, it's just invisible. My map lines up perfectly with what VASSAL has set up so now my counters will snap into place properly. Hopefully that makes sense, I can elaborate more if needed. > > GJK > > At 10:19 PM 8/3/2006, you wrote: > >Thanks for the quick reply. I notice in the map making tutorial > >Gary matches a VASSAL generated gird to the grid on the actual map. > >Why the need for the VASSAL grid? > > > >Thanks! > ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________ ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________ [Non-text portions of this message have been removed] Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/vassalengine/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
