Hesiod roadmap

[otto-link]

• Core / HighMap
  • simulation-based procedural
    • improved erosion (Gaea-like or KTT-for-Houdini-like)
    • debris simulation
    • improved flow simulation (less numerical artefacts)
  • prop placement
    • vegetation placement
    • city placement (w/ terrain flattening)
    • roads
  • integration to game engines
    • game engine integration (Unity, Unreal, custom, ...)
    • modular integration to reduce footprint as a dependency
    • "infinite" world
    • world loading/saving, memory management
    • world partitioning
    • chunk streaming
    • LOD management
    • world queries (height, normal, material, biome, objects etc.)
• GUI / Hesiod
  • 3D viewport
    • direct edit in viewport (heightmap, cloud, path...)
    • object placement (predefined, user models)
    • domain tesselation
  • non-square domain Allow non-square grid usage #220
  • bridges
    • Blender
    • Godot (through Terrain3D)
    • Unity, UE...
  • general
    • undo/redo (node, parameters) feat: implement generic undo/redo #265
    • better project save structure (relative/absolute path, storage...)
    • documentation / tutorials
    • less nodes... merge some of them, remove others
    • light/dark mode switching Add light/dark mode switch #616
    • macros (group of nodes + I/O) functionality

[barrulus]

Adding [] light/dark mode switching

[Leonhardmaster2]

I was thinking of adding macros. Store macros in the engine to allow users to make their own subgraphs for eg custom Mountains or similar

[otto-link]

I added it. It's pretty challenging at first sight, I'm not sure the current model and GUI architectures are ready for this 🤔

[barrulus]

could this not be an extension of the work that was done for the python automation?

[otto-link]

I interpreted the macro idea as: you have designed a set of nodes (a subgraph) that you find particularly convenient, and you want to turn that subgraph into a ready-to-use macro that behaves like a single node, with its own inputs, outputs, and parameters.

That’s a fairly complex use case and would require quite a bit of boilerplate.

[barrulus]

Really? Isn't that simply like grouping a bunch of nodes into a graph and then using broadcast/receive to move data from one graph to the next?

[otto-link]

Hum, possibly, this would need some further digging to evaluate this. (but it's a very nice feature, I'm not saying it should not be done)