Spotlight Spotlight

If you like Hearts of Iron 2 or World War II themed wargames, I suggest you take a look at Struggling Leaders of World War II, which is in preparations for second game. You can participate in many ways.

Visit Forums Visit Forums

Visit our forum, join the discussion, find likeminded people from around the world and have a good time. Play multiplayer games, develop ideas, have fun. Evolving community aided by evolving software to meet all our needs and desires. Thats Domain of Lord Ederon Forums.

Want to Help? Want to Help?

Do you like this site and would like to help? You can do so by contributing content or money. All help is highly appreciated.

The Map Editor The Map Editor

A map editor for HoI2DD/A and V/R.

News News

MapUtility 1.2.1 is out, with some minor fixes and improvements. Download at the links section on the right, as usual

Changelog:

MapUtility v1.2.1

MapViewer v6.2.1
-Fixed some problems with extracting readonly files

MapMaker v2.2.1
-Radish headers exported to separate file
-Making initial radish files and making adjacents now have better status updates
-Speed improvements in reading and writing radishes
-Bound boxes now made from lightmap1, not radishes, which is much faster
-When a border is not found, no longer causes an infinite loop, but simply returns the value without the border

MapExtractor v1.0.1
-Fixed some problems with extracting readonly map files

Version 1.2 of MapUtility is out. As usual, download at the links section to the right.

 

Changelog:

Global
-Now supports different map sizes, lightmap offset sizes, and numbers of lightmaps, and method of reading different id formats, all set in settings.txt (though support is not complete)
-Index.tbl values can now be two bytes wide as well as the previous four bytes
-ObjectEditor added
-MapExtractor added
-index.tbl now reads and writes UInt16s when working on two bytes
-Log files now have a header

MapViewer v6.2
-Fixed GUI title
-Logfile at log.txt
-Tweaked sizes of displaying and exporting images
-Can view CK lightmaps
-Got rid of GUI export button, as it was more trouble then it was worth
-Scrolling (!!!)
-With scrolling, some sliders are no longer necessary and have been removed
-Now displays information about the current pixel
-Now gives message when completely done extracting
-Now colorscale images are saved correctly

MapMaker v2.2
-Changed recommended MAXPROVINCE number for HoI to 2608, as that is the correct one.
-Fixed message reporting lack of images.txt
-Fixed minor problem with finding adjancies
-Now will read a file called adj-mod.txt to change adjancies
-Errors will be logged to errorLog.txt
-Fixed problem with creating tiles.bmp, now the original palette is used
-When making lightmaps, shading is slightly more flexible
-Now after creating initial lightmaps, will automatically check for block existence, and removed corresponding option 11
-Now supports varying numbers of lightmaps (3 or 4)

Version 1.1 is released! Download at the links section to the right.

MapUtility v1.1 Changelog

Global
-Reduced memory usage slightly (in Leaf and MapBlock classes)
-Renamed psd.txt to images.txt
-Will no longer report lack of ids.csv

MapViewer v6.1
-Problem with extraction memory usage fixed
-Fixed problem with extracting borders, all pixels used to be considered borders, causing creation of lightmaps to fail
-You can now see a grid overlay
-Can use commandline "-extract" to do -extract(0,0,72,72,13,5) and create a automatic psd.csv
-Can now view and extract tiles
-Added version number to various places
-Warning if lightmap1 is not found, which suggests that MapViewer is not in the same place as the game exe
-Fixed problem with "-extract", now the folder "exported maps" will be created
-settings.txt made, including an option to keep MapViewer separate from the game files

MapMaker v2.1
-Made messages while creating adjacent file shorter
-Now the MAXPROVINCE number will be saved to a new file settings.txt, so you don't have to type it in every time
-Added version number to title
-Shorter messages while creating tiles
-Fixed problems with creating index.tbl
-Improved messages for making initial radish files
-Removed references to photoshop files when missing images.txt, as different images can be used, not just photoshop files
-Fixed a minor error with shading
-Improved boundbox making messages
-Added an option to check whether all blocks exist, and whether there are duplicates

 

MapUtility beta 1.0.6 is out.

Please test and report bugs/errors/inconveniences

Download at "Download Center" under "Related Links" or  here.

Version 1.1 will probably come out later today (It is GMT+7 here)

The first full version (v1.00) is out. Download at links on right.

Please provide feedback on what to improve.

Lots of updates. Lets go from least exciting to most exciting. As always, see the download section for links.

First: Version 5 of the Specs. Since support for .bmp, .jpg etc was added, these had to change a bit

Next: Version 5 of the MapViewer. You can now extract files through the commandline, so that you don't have to do it through the sliders. For arguments, type "-help" without quotes.

Finally: Version 1 of the MapEditor. So far, this cannot do lightmaps. But it can do everything else. (Though making radishfiles might be bugged)

BTW: You have to download CoreLib.dll again. (It is different, even though it still says version 1.0.0.0)

Updates:

Version 0.4 of specs. These should be more understandable

Version 4 of the MapViewer. This allows you to extract parts of the map into image files. Unfortuantly you still have to merge them into a photoshop file.

CoreLib.dll: MapViewer v4 requires this.

See the downloads list for links.

Soon, these specs will be set in stone, so if you want changes you must state them now.

Here are the specs:

Version 0.2 of the Map Editor Photoshop File Specifications

Data:
In the same place as the application will be a file called psd.txt.
This file should contain all of the .psd files, each file on a different line

The city field of the .psd files will be filled in like so: x;y
Where x is the x-offset, and y is the y-offset
X=1 is 32 pixels, X=2 is 64 pixels, and so on

Bottommost layer:
Divided into blocks of 32x32 pixels. Each block will either be filled with black, to signify that it should be transcribed, or kept transparent to prevent copying.
Notes:
a) A separate text file should be included to describe what pixel on the big map (0, 0) is
b) Transcription is described only blocks of 32x32. Either a block is completely included or it is not
c) This layer should be called "Base"

Province ownership layer
Colored with RGB values according to the province that owns the pixel.
Notes:
a) What a certain RGB value represents will be determined by a separate .csv file, in this format:
ProvinceId;Red;Green;Blue;Optional Comment;There can be as many semicolons as you want;But the first four sections must be as specified
#Lines can also be blank or commented out as a whole
42;49;20;44#This comment is illegal
b) This layer should be called "ProvID"

Grayscale layer
Colored with a grayscale, to determine the index into colorscales.
Notes:
a) The index will be value/4 (Note that remainders are truncated, so a val

Version 3 of the Map Viewer is available. It has grids and numbers to know the needed offsets. Look to the right for download

The file "provinces.csv" is available. The editor uses this file to decide what colors map to what provinces. You can change the RGB mix, but this is for those that want a starting point. Note that deleting the extra IDs can be helpful.


Syndicate   Print