Finally made something with the procedural crater heightmap generator I've been working on. It's also an experiment in using procedural texture creation for all the final textures (even the splats), which I don't think turned out very well. I'm probably just pretty bad at creating natural-looking textures with NeoTextureEdit.
I tried to balance the map (for BA units) between vehicles and kbots. Kbots get you two more metal spots, and easy access to the big central crater. Vehicles can only get into the crater via two ramps.
Looks interesting.
Checked your code a bit, it seems like it was written for LÖVE. I thought you also had something going for Spring?
I'd be interested in integrating something like this in the Scenario Editor as a module if there was a Spring version. Thoughts?
There is a Spring version, but it doesn't work for outputting large images for texturing (because of Spring's overhead, memory limit, and synced/unsynced seperation). Ultimately, I want to clean up the code in the LOVE version so that the non-UI part of it can just be included as a module in whatever, and then put it back into the Spring version. (The Spring version's algorithms haven't been updated to what the LOVE version now does.) If I did that, I imagine it could become a Scenario Editor module, though I haven't tried out Scenario Editor. I'm also thinking I could make a choose-your-own-crater map, that wouldn't have pretty textures, but would create randomized crater maps (with a lot of map option control over size and number of craters, symmetry, metal amount).
I was thinking of including it as a way to generate a new map (or a subsection of it). Doing textures (diffuse) is doable in Spring too, although noticeably harder. I can help you out with that (I'll make a simple API), just tell me when you've cleaned it up so I can try out.
I haven't yet done any work on map generators in Scenario Editor, but I figure there are going to be many different approaches so making it modular makes sense.
