VoronoiTestGodot VS godot-cpp

This approach can be used to easily generate a Voronoi diagram with taxicab distances (i.e., using Manhattan distances). So, to quickly assess the Voronoi map in action, I implemented this algorithm directly in GDScript in Godot to interactively explore maps with different metrics. Disregarding all the details, the pure algorithm code looks like this:

Write C++ classes or functions using C++ bindings for the Godot engine.

Might have sth to do with https://github.com/godotengine/godot-cpp/issues/1057 . All of these errors pop up when godot::Refs are returned by certain engine functions like the one in FastNoiseLite but objects instantiated via memnew work like a charm. Plus with more gdextensions registered these issues seem to happen at more places.

I think part of the problem is that using GDExtension is like a two-way FFI. You can call (C++) extension functions from GDScript, but the same interface and overhead are used to call (lib) Godot functions from the (C++) extension.

Here's a good example (look, there I am!), although it's a bit old and actually led to perf improvement:

https://github.com/godotengine/godot-cpp/issues/1063

I've had some performance problems with GDExtensions: https://github.com/godotengine/godot-cpp/issues/1063

I tried checking out cpp repo for my godot version 4 from this repo

godot-cpp/gdextension/gdextension_interface.h

Thanks! At the moment I've been running into issues with accessing some methods of the AudioServer as well as overriding some native functions (primarily related to audio_stream and audio_stream_player). These issues on the issue tracker cover them: https://github.com/godotengine/godot-cpp/issues/1090 https://github.com/godotengine/godot-cpp/issues/1088 That said, there may be a way around this, it could just be that different bindings need to be used - currently the audio stream and audio stream player code is heavily based on existing classes like AudioStreamPlayerPolyphonic. Worst case I believe Godot itself needs to be updated to expose the appropriate bindings. I'll upload a separate branch for what I have for the GDExtensions version (though it fails compilation) sometime soon. I started this as a traditional Godot module during the 4.0 pre-alpha days but I definitely want to move it to GDExtension so its super easy for people to pull into the official engine release.