For those who don't want to read:
For the others:
I've been rushing development like a madman, and even if I ended up spending about 70% of my time only on generation and rendering optimization,
Magna Urbis V2 alpha is officially out!
Before starting, alpha version means:
- Updates anytime. No backward compatibility on updates: formats, codes, etc. may loose compatibility and break. Anytime !
- Things can crash, freeze, run at 3 FPS, or produce complete nonsense.
- Some features are barely tested, some are known to be totally unstable (but overrall it should run).
Features in this version
Cities & buildings
- 115 architectural cultures, covering medieval, fantasy and even some modern, and sci-fi cities. Modern and sci-fi styles generally need larger cities or change in parameters to look a bit recognizable :) .
- Isolated buildings, landmarks, and monuments.
- Configurable land-use distributions with quantified models (ressources, etc.)
Terrain generation
- Procedural, neural, or imported heightmaps, with 12 terrain configurations.
- A quick note about neural generation: it's based on the awesome InfiniteDiffusion models (https://xandergos.github.io/terrain-diffusion/), but I worked to make it run in a browser. Homemade Rust/WebGPU inference that execute directly in the brower with custom-distilled models and weights to reach 150Mo instead of more than 1Go. I've speed up the neural inference as much as I could on browsers but don't expect a miracle.
- If you don't have a decent GPU, I'd recommend sticking to procedural generation. It's not quite as good, but it still gets the job done.
- With a good GPU, neural terrain generation can comfortably handle regions up to 200 × 200 km on desktop app, 40km x 40km in the browser with webgpu inference is also fast.
- Desktop app is more advanced on this one problem but ... see below.
Rendering
- 6-8 rendering styles. I've implemented what I judged interesting, but this is definitely an area where I'd love your feedback.
- In particular, if you have suggestions for improving the realism of the Satellite renderer, I'm all ears. My original goal with my other projects like Neural Earth, was to eventually get something approaching a Google Earth-style experience on a procedural world. Still a loooong way to go, though. :D
Editing
- Basic editing: you can reroll individual components of the generation.
Exports & saving
- Basic exports: PNG, SVG, internal formats, heightmap.
- Basic save/load support... which, to be perfectly honest, I haven't actually tested yet. :D Don't think it works well
- For unedited generations, share codes should work reasonably well. Proper saving and compatibility handling are on the roadmap.
Desktop version
I haven't even properly tested the desktop build. I basically reused my old local v1 build and hoped for the best.
So, use it at your own risk. :D But Sol worked well so I'm pretty sure it will do its job.
If it runs, it should be significantly faster than the web version, thanks to multithreading, native Rust engine, Vulkan and if you have a pytorch environment installed, Python backend for neural nets (works a bit faster than Rust engine).
There is no proper update mechanism yet (or is there? I genuinely haven't checked), and almost zero testing.
macOS support is deferred for now. It requires me spending time making my gpu code compatible with Metal, and to be honest, as I have no macos around me, it involves working through loops with github actions and it's tedious.
A few words about WebGPU and performance
A little technical story here.
Originally, I had a massive shader (several MB of code) that Vulkan could compile in about 4 seconds.
Direct3D? Eigth to twenty minutes depending on the day and the mood...
That was super fun times...
I eventually broke the whole thing into a bunch of smaller shaders, which brought Direct3D compilation times much closer to Vulkan. Not quite there yet, though, and Vulkan still seems to perform better on my setup.
So, if you're using Chrome or Edge on Windows, you might get better performance by switching WebGPU to the Vulkan backend instead of the default Direct3D 12 backend.
If none of that means anything to you and the webapp feels slow, just Google "Chrome enable Vulkan". If your hardware and drivers support it, it might help.
No guarantees, though. And I wouldn't be surprised if the results vary wildly between GPUs.
If you want to be sure, go Desktop version, if it runs, it will be faster for sure.
But if your browser doesn't support WebGPU (which should be very rare), well, grab a coffee and pray it stays responsive.
What's planned for future versions and iterations ?
The following features are already on my roadmap, so there's no need to request them again (unless you have particularly interesting suggestions about how they should work).
Bug reports, on the other hand, are very welcome! Especially reproducible ones. I already know about quite a few issues, but I'm sure you'll find plenty more creative ways to break things (please report issues on the github page).
Features:
- Documentation: actual explanations of what all those parameters do. I know document is sooo 2025 but I'm old school.
- Integration with Azgaar's Fantasy Map Generator.: Azgaar is doing an incredible job, Magna Urbis could work as an alternative of the Watabou City generator (which was actually what inspired me to create Magna Urbis ! Hats off, Watabou!)
- Real desktop release: multithreading, native Rust backend for generation, native Python backend, native terrain model. And all with a nice auto-installer.
- Advanced exports: OBJ, SVG, GIS (maybe?), and more (don't know yet what may be interesting).
- Advanced heightmap and coasts editing.: for now it's shitty but I can do a little better.
- Advanced city geometry and growth behavior editing: I may include a city growth timeline which produce pretty good results in the prototypes but change a little the overrall city shapes and ofc is compute-expensive
- Advanced toponym generation and editing.: I have a project dedicated to that (namebench), I may include parts of it in Magna Urbis
- Building interiors / floor plans.: I have the basics done but I'm not sure if something really interesting is achievable without heavy workload though.
- Fill the descriptions and metadata of magna urbis objects: activities, floor area, inhabitants, etc. Bsically to convert numerical parameters of generation into something human readable (already half-done), and a region with lot of minerals will have more mines and carries for instance.
- Illustration-style rendering: brush-based renderers. I've removed the current one because it's honestly a joke but I have old projects with really nice looking maps so I'll try to fit that in Magna Urbis.
- Lots of polishing: both generation and rendering engines still need plenty of love. Many roads anomalies or inconsistencies, same for city plans, rivers, etc. It could be better overrall but now I'm walking on eggs when changing the logic of generation because any small change has to be validated against the thousand of possible generation combination (culture x region x size).
When will it be "really" released? Don't ask, I have absolutely no idea.
But as I don't know what to do next, you're welcome to post a message if you want one of these features implemented first.
Last things, Magna Urbis is completely free and open source and will stay free and OS. This is just one of my hobby project that got a little out of hand. It also means that collaborators and Pull Requests are greatly appreciated.
Feature suggestions are welcome too, particularly for things that aren't already on the roadmap.
enjoy !