Geo at: . . . . . . . CRASH

[Caydr]

Trying to use mother's map conv so I can place fancy feature and all that crap. Anyway, while the standard converter works fine and the map compiles and is goregeous, as soon as I switched to mothers (and put the geos on the feature map), it gets to "Geo at:" and then crashes.

Code: Select all

mapconv.exe -l -i -c 1.5 -n 50 -x 1200 -m GD3metal.bmp -a GD3height.bmp -t GD3texture8192.bmp -f GD3feature.bmp -o Altored_Divide.smf

As I said... with the above minus the -f part for the feature map, it compiles fine. There are no typos, and all filenames correspond to actual proper files.

Anyone have an idea how to fix this?

[NOiZE]

how about YOU read the wiki first, like everyone else?

really, every tiny problem u start posting on the forum right away instead of searching for documentation...

[Caydr]

Golly, and here I was thinking that looking through it for the last 30 minutes, using the forum's search function, reading all the available mapconv documentaion (for both the standard version and mother's), consulting with Fizzwiz, then MRD, was enough. Would you be so kind as to direct me to a better place to look than a forum for map making? kthx

[NOiZE]

http://spring.clan-sy.com/wiki/Create_maps

read carefully!!!

height and metal 1/8 +1

feat 1/8

[Caydr]

I've read that over many times in the last couple of days. Where does it mention a crash at geo placement? Or even just crashes, period.... I don't see how that file applies at all to the situation at hand.

It says something about mapconv going into crack addict mode or something, but that's when a geo is placed in an impossible location, which clearly is not the case being as the locations are identical to where they were before, when using the other map compiler, and it worked. And all geo spots were on flat, buildable ground.

[NOiZE]

probally happens because one of your maps has wrong dimensions?

[Caydr]

Or not. All my maps have the proper dimensions according to the document you provided, and I've also tried several variations as recommended by a thread discussing that topic which I read recently.

In other words, I'm not just posting at the drop of a hat because I can't be bothered to research things. There's a problem that's undocumented and I need to find a way past it. Where else but here should I ask?

[NOiZE]

But you do not tell us the precise problem.

tell us your dimensions you are working with aswell!

well maybe you got a geo close to an edge of the map?

[NOiZE]

also -x 1200 is pretty high... although i don't know the max...

[Caydr]

All my geos are well away from the edges of the map.

My texture map is 8192x8192 (was shooting for a 20x20 but the filesize was monstrous, so I'm setting for a 16x16)

My height map is 1025x1025

My metal map is 1024x1024 or 1025x1025 (I've tried both)

My feature map is 1024x1024 or 1025x1025 (I've tried both)

1200 is well within limits, as I has it set to 2000 at one point and there was no issue.

Whether to add an extra pixel to the metal and feature maps is up to debate right now if you can find the relevant topic.

[NOiZE]

if texture map is 8192x8192

then

height map should be 1025x1025

metal map should be 1025x1025

feature map should be 1024x1024

Notice the wiki page about map making is a bit messy, well messy quite a lot... but there are 2 mothers mapconv's, a optimized version and a non-optimized version.

I use the non-optimized version, as the optimized version crashed directly for me

hope this helps..

[Forboding Angel]

also, geos go one the feature map, not the metal map.

[SwiftSpear]

You have black as blank on the feature map and metal map, right? White is all colors at 255, and therefore basicly tells the compiler your whole map is full of geos and metal spots.

[Lindir The Green]

the Geo at: thing happens to me too, so I just use an older version of mother's mapconv.

But I keep getting errors loading the tile map withthat one.

So I guess I will just have to wait for sharpmap (which buggi said would come out around christmas )