Spring RTS Engine

yes im using Bruces Mapconv Fronted

I would very confounded if the currently released version of mapconv was causing the errors, all it does is make a buffer with the commands and uses system().

an somebody just give me copy of an example mapper.bat, you know when you open it in notepad. just paste what you used for a map, please.

I'm reviving an old thread, YES, its because I am having a similiar issue with my map...

but its strange...

sometimes I load the map (no matter what version, or which I compile it as), and its pink, sometimes I load it, and its not...

its VERY strange...

and depending on the compression ratio on mapconv it does it more/less often...

and somtimes it can't even find the .smf file...

its VERY mind boggling... and I can't figure it out....

mapconv commandline code:

mapconv -i -c 2.8 -x 1350 -n 100 -o Severnaya_Industrial_v94.smf -t texture.bmp -m metal.bmp -a height.bmp -f feature.bmp -l

it's because you changed the name of the smt file after compiling lathan. You CANNOT change the name of the smt, period. You can however change the smf and smd to whatever you like as long as the filenames for the 2 match exactly. Whatever the smf filename is, that's what spring will see.

Forboding Angel wrote:it's because you changed the name of the smt file after compiling lathan. You CANNOT change the name of the smt, period. You can however change the smf and smd to whatever you like as long as the filenames for the 2 match exactly. Whatever the smf filename is, that's what spring will see.

I did not change the name, I learned that allready.

I'm tired of compiling this pain in the ass...

I'm damn tired of it,

nothing is working anymore..

Try getting new copy of nvdxt.exe that has worked for some and also check the there are no spaces in the path.

Your map is very tall, which suggests that it may be very large. This may also cause problems with compiling and loading. Would you tell us the sizes?

My system overclock was fudging with it... sigh

guess my computer isn't as stable at 4.4GHz as I thought...

back to 4.2 GHz for now....

still beats 3.2GHz stock lol.. + 1.0 GHz overclock

if you see the salmon color over the entire map it means the engine can't find the tiles. I had this happen to me once and the tile file wasn't named properly and referenced properly.

Fixing the reference fixed the map, remember, the file with the tiles is referenced in the binary file of the map, so changing the SMD won't work.

Weaver wrote:Did you change the names after compiling? The salmon/cat puke pink colours can be caused by the game not finding the textures which are in the smt file. The filenames are hardcoded into the smf at compile time, changing the names will give a pink map.

This is the problem, no question.

LathanStanley wrote:My system overclock was fudging with it... sigh

guess my computer isn't as stable at 4.4GHz as I thought...

back to 4.2 GHz for now....

still beats 3.2GHz stock lol.. + 1.0 GHz overclock

Guys I think this means he fixed it.