jelco wrote:Will there ever be a map-to-image feature? Honestly I doubt it given the total lack of use of such a feature but if I get bored enough I may just try to write it. Pretty complicated though when you get multiple overlapping tiles with different maxheights and everything...
Jelco
Oh man that sounds so hard ;-;
Seriously though, if you don't know off hand which grid guide you want, it would be nice for it to just simply be able to iterate through a map and produce an image for each grid guide, and that's all, not do anything special, and just number the images as they come out of the file; tells you everything you need to know. Maybe not call it map to image, but, just dumping all the guides out could be helpful rather than doing each one by hand.
As an aside, I've been using pngs exclusively while using your app, which I have been helping you test, and have not noticed any problems at all, the only barrier to progress was that I have apparently been using interlaced pngs in general for a very long time, which PIL doesn't support at all.
As a further aside, I would like to endorse this handy little app. I'm probably never going to use "-image to map", the supposed core feature of this, because I can't imagine memorising the offsets and scales of how I want to inject it into the map, I just want it IN the map, to the end that I'll probably make a grid guide in the level and paste a grid string in myself, rather than use this feature. Thinking about it, it would be nice to be able to inject it into a map with some default values, so you can just use the map editor to sort it out later without having to first create a shell guide. The objective there is to just get it into the map so you can edit it yourself.
But anyway the reason I endorse it is that editing grid guides, especially to be complicated, such as long chained ramps, can take hours to get perfect, and are easy to ruin by accident. You can use this app to very easily do a lot of things that you simply would spend an eternity doing otherwise.