Rewriting the whole plugin in C++?

[kubajz22]

Is your feature request related to a problem? Please describe. Some of the parts of the plugin are quite performance hungry, especially the detail layer. And considering you probably have multiple of those it might be interesting to compare it with an implementation in GDNative. In my case I actually need a lot of detail layers and a huge terrain and each detail layer consumes a lot of FPS. I've already rewritten some of the scripts. (Takes a surprising amount of time.) Now when I think about it, I'm not sure if it's feasible for me to do the whole thing, but it might be if others help.

[Zylann]

Detail layers aren't particularly optimized to begin with. The part that takes time could be shared in some way. Also it has to sample vertical bounds which could be stored in a hierarchical way but it makes things a bit more complicated. I dont plan to rewrite the plugin in C++ in the near future, but it might happen longer term.

[kubajz22]

Ok, in the meantime I'll continue working on it. I could make a PR in the future if I'm actually successful.

[darrylryan]

@kubajz22 I don't think its worth rewriting things for Godot 3.2 but it might be worth writing it for Godot 4

[tay10r]

I opened #261 and have started implementing some things in C++, such as an Erosion Library. There's also FastNoiseLite which may be handy.