[mandrill7]

Okay, I'm stupid.

I put my map_c (saved as an uncompressed .tga greyscale at 1 pixel - 50 m) in a folder with cmap.jar and disect.bat and I right clicked on disect.bat and.......... nothing happened. Well, the disect.bat icon flashed for a millisecond. But the map_c was not dissected and no c_map. table was created.

So what am I doing wrong?

[fly_zo]

read readme again ....

you need to rename your file as instructed in order to get it dissected ( not as map_C.tga )

Z

[mandrill7]

Well, just tried that. I renamed to Mymap_c.tga and clicked on transform.bat. But again nothing happened.

The map_c.tga file is divisible 32 x 32 and greyscale and uncompressed. It should be operable.

Is there something wrong with how I am trying to run the .bat program? This is my first time trying to do something like this?

[fly_zo]

from readme :

2) DISECTING TGA FILE
Place MWmap_c.tga into a folder where
CMap.jar is.
Run:
disect.bat
This will create newMWmap_c.tga and MWmap_c.tga_table files
which are in format which IL2 can understand. MWmap_c.tga can
be any image you modified or created from scratch. MWmap_c.tga
must have dimensions which are multiple of 32x32 (for example
1536x1312) and have color depth of 1 byte (i.e. grayscale image).

[asheshouse]

Have you got Java installed?

[Redwulf__32]

Hi Mandrill,

This one might be easier to use. No Java, .NET or other surplus junk needed. "Old fashioned" complied Windows application (has a manual and it's faster too).

viewtopic.php?t=9486

[tsb47]

Make sure there is only one layer in the image.

Are you using GIMP? GIMP appears to have a bug which may tell you that the image only has one layer when, in fact, there are still multiple layers. Go into GIMP and "flatten" the image to ensure that there is only one layer. Then save and try again.

[mandrill7]

Thanks, Redwulf. I d/l-ed the alternative application and tried it out. I got a little farther along. It opened my map_c.tga and then I attempted to create a map_c.table.

But after a few seconds, the application stopped and appeared confused. It then aborted the process and told me the map was "too complex".

I checked in PSP that the map is only 1 layer. It is. And it is in greyscale and just uses black and white.

The map is quite large - over 10,000 pixels wide. And it has a lot of little lakes and a few large rivers. No sea coast at all. (Central Russia).

Any guesses or suggestions as to what I should do???? I could white out some of the lakes, but I don't want to do that unless I genuinely have to.

---------------------

I later went and made a little map_c test map with just some black flood fills on a 640 x 640 white square. The map c toolbox program promptly made a nice dissected map_c and map_c.table out of this little guy. So I guess my Smolensk map really must be "too complex".

[Redwulf__32]

Thanks, Redwulf. I d/l-ed the alternative application and tried it out. I got a little farther along. It opened my map_c.tga and then I attempted to create a map_c.table.

But after a few seconds, the application stopped and appeared confused. It then aborted the process and told me the map was "too complex".

I checked in PSP that the map is only 1 layer. It is. And it is in greyscale and just uses black and white.

The map is quite large - over 10,000 pixels wide. And it has a lot of little lakes and a few large rivers. No sea coast at all. (Central Russia).

Any guesses or suggestions as to what I should do???? I could white out some of the lakes, but I don't want to do that unless I genuinely have to.

Hi Mandrill,

Had that issue myself, that's why I put the "complexity check" in the application. Do a histogram of your raw map_c file. Make sure white is white i.e. every pixel with a value above 127 is 255 (make sure anything below 100 is 0 at the same time), this is the usual cause of "map too complex", this can occur during your processing of the raw map, especially if you use antialiasing. My Denmark map_c is 14784 by 11072 pixels (somewhat larger than yours, I think), is very complex wrt twisty-turny coastlines, lakes, rivers and now compresses comfortably to about 25 Mb (limit imposed by TGA format is 67108864 bytes), tga_table to 625 Kb.

Hope this helps, don't hesitate to PM me if problems persist.

EDIT: Oh make sure it's grayscale i.e. 8 bits per pixel, you'll need the grayscale to soften the coastlines. Welcome to the madness btw :wink:

[dunkelgrun]

Something that has affected my tga's from time to time is forgetting to delete the invisible layers. In Gimp, merge visible layers but make sure 'Delete Invisible Layers' is checked. Also, don't forget to remove the Alpha Channel from your final layer.

:cheers:

[mandrill7]

I'm easily confused re the Alpha channel, as I'm not even sure the old edition of PSP I use even has one. How do I check for it and remove it, if it exists?

Thanks as always.

[mandrill7]

I checked the map_c and realized I had made a silly mistake. I have a working map which consists of a layer of map_c over a layer of map_h, both the same size. I can play with the transparency of the layers to see both the rivers/ lakes and the height of the terrain.

When I made the map_c from the working map by blending the layers, I forgot to make the top layer 100% opaque and as a result, I got an off-white/ faint gray map, instead of a white one!!! :oops:

I made a new map_c and checked it over after enlarging it. There were still some gray spots. I have no idea where they came from, but I messed with the histogram control, as Redwulf suggested and blitzed them out.

I discovered that I have to "tidy" the map_c a lot because the neat lines I thought I had drawn in suddenly don't look so neat at 400% size increase. So I will try the map_c toolbox program again in a few days.

[Skunkmeister]

Always draw your map_C at its full size. I will save you a lot of aggravation when you finally get it in game.

[mandrill7]

Always draw your map_C at its full size. I will save you a lot of aggravation when you finally get it in game.

Uh-huh........ Well, you PTO guys don't have to place rivers that are 100's of miles long into river valleys and work from the map_h to do that. :wink:

BTW what does the map_c do anyway?? The other maps establish what is land and what is water, elevation, textures, etc.

[Redwulf__32]

Always draw your map_C at its full size. I will save you a lot of aggravation when you finally get it in game.

Uh-huh........ Well, you PTO guys don't have to place rivers that are 100's of miles long into river valleys and work from the map_h to do that. :wink:

BTW what does the map_c do anyway?? The other maps establish what is land and what is water, elevation, textures, etc.

Hi Mandrill,

Map_c is very important, it's the one that defines what is land and what is water.

Map_h defines the elevation above sealevel of both land and water (yes, lakes, rivers can be above sealevel). Pushing your lakes, rivers to sealevel will ensure the infamous Indiana Jones "steep canyons of certain death".

Map_t defines the textures put on the map - lowland, midland, city, water, etc. BTW use water to make areas navigatable by ships. Using water inland will leave ugly black blotches while using non-water to sea has no effect except making it non-navigatable by ships (or making reefs if the corresponding map_c value is just shy of 128).

map_c is 50m/pixel, map_h and map_t 200m/pixel

The ed maps define the ingame maps.

Map_f and the rest are more obscure.

Hope this helps....