MapConv Designed badly.
Posted: 18 Jul 2010, 12:23
It does like three or four separate jobs which IMHO should be three or four separate programs, and have a script/frontend do all the in-between works.
I know that some people would think that keeping it all together is smarter because its simpler for end users. but that's why you have front ends/scripts.
what I personally want to make feasible is creating maps out of tiles in the first place instead of just ridiculously large images
I've been running it on Linux, browsing through the source etc, trying to make sense of exactly what it does.
----
As far as I can tell so far:
It splits up the huge image into 1024x1024 bmp files then does something to them so they are 1024x1024 bmp.raw files
It calls the compression tools to make dds files in there somewhere(not sure if the raw files are dds)
It creates the minimap from the texture image.
It joins them into smf (spring map file), and smt (spring map tile)
then you have to use 7zip to join them all together into the sd7 archive(with any other resources and the smd (spring map description?))
----
What I want is creative control over each step(as much as permitted by the map spec), so its modular and people can write better intermediary utilities that perform certain jobs better, instead of having to replicate/replace MapConv with their version of an all in one tool.
I'm writing up some documentation on what exactly mapconv does. and also I want to create a really good specification of the map format. so if Behe or others can fill in some of the blanks from my knowledge that would be great !!
I know that some people would think that keeping it all together is smarter because its simpler for end users. but that's why you have front ends/scripts.
what I personally want to make feasible is creating maps out of tiles in the first place instead of just ridiculously large images
I've been running it on Linux, browsing through the source etc, trying to make sense of exactly what it does.
----
As far as I can tell so far:
It splits up the huge image into 1024x1024 bmp files then does something to them so they are 1024x1024 bmp.raw files
It calls the compression tools to make dds files in there somewhere(not sure if the raw files are dds)
It creates the minimap from the texture image.
It joins them into smf (spring map file), and smt (spring map tile)
then you have to use 7zip to join them all together into the sd7 archive(with any other resources and the smd (spring map description?))
----
What I want is creative control over each step(as much as permitted by the map spec), so its modular and people can write better intermediary utilities that perform certain jobs better, instead of having to replicate/replace MapConv with their version of an all in one tool.
I'm writing up some documentation on what exactly mapconv does. and also I want to create a really good specification of the map format. so if Behe or others can fill in some of the blanks from my knowledge that would be great !!
