Few questions about procedural generation and saving on export

[EduardoLemos567]

Hi,

1. I would like to know if this can be used to procedural generation on demand, like when the camera moves, i generate regions on code and send it to the terrain, also can i remove them, on the fly, all without saving ? Does it works well on memory: adding and removing them when the camera moves ? Any caveats ?

2. Can i choose to save/load from disk after the game is exported ? Like a save file on the player's disk ?

3. Can i also choose to save/load from memory, using my own file serialization method (simple cryptography to avoid players messing with it) ?

4. Also a question/suggestion, since the normal used into the mesh generation is a constant pointing up, cant you avoid setting the normal array on the ArrayMesh and recover the normal as constant on the shader ? Would that save some performance and memory ?

Thanks for the addon, looks and feel amazing.

[TokisanGames]

I would like to know if this can be used to procedural generation on demand, like when the camera moves, i generate regions on code and send it to the terrain, also can i remove them, on the fly, all without saving ?

Regions can be added and removed on demand. There may be a delay regenerating the region map when you call update_maps if there are a lot of regions.

As for doing it when the camera moves, that's on you. We don't control your camera. We only track it to set our LODs.

Does it works well on memory:

Memory is consumed for all of the regions you create. This system allows you to have a large terrain avoiding paying for regions that might be under water and unused.

Can i choose to save/load from disk after the game is exported ? Like a save file on the player's disk ?

That's a Godot question. In Out of the Ashes, we save and load our game to a file without issue. If you mean load or save regions, the API allows you to load region data. Godot allows you to save or load any data to disk.

Can i also choose to save/load from memory, using my own file serialization method (simple cryptography to avoid players messing with it) ?

You should read the Data API.

Also a question/suggestion, since the normal used into the mesh generation is a constant pointing up, cant you avoid setting the normal array on the ArrayMesh and recover the normal as constant on the shader ? Would that save some performance and memory ?

That's a good idea that is worth considering. Thanks.
However upon further inspection, Godot spams with warnings if we don't pass normals and tangents in the vertex data. We could skip them if we don't use the channels.