Is there a way to set the pointer array of image directly instead of constructing a PackedByteArray to create an image? about gdext HOT 6 CLOSED

You should fill the PackedByteArray as early as possible in the chain, avoiding expensive copies each frame (where possible of course). Furthermore, try to reuse the same packed array across frames. It should not trigger CoW if Godot doesn't keep hold of the buffer.

PackedByteArray cannot point to foreign memory, it needs to own it due to the CoW semantics.

Ultimately, we're limited by the APIs that Godot provides, so this is more a Godot instead of godot-rust related question.

from gdext.

After searching for some code in godot, I think the PackedByteArray does not matter in construction of Image object. A pointer and the size are enough.
From the image below, we can know data of godot image was passed by passing a reference named p_data. The reference in C++ is equal to pointer variable ("reference" can be transfromed to "pointer"). So, it's not a matter of godot APIs, but a matter of gdext.

from gdext.

And which public Godot API allows passing a pointer? We don't have access to Godot's internals.

Also, why upvote your own comment? 🤔

from gdext.

And which public Godot API allows passing a pointer? We don't have access to Godot's internals.

Also, why upvote your own comment? 🤔

Isn't this function a public Godot API? The p_data parameter, can just be passed as *vector_ptr.

from gdext.

Isn't this function a public Godot API?

Well no, the public API is documented here:
https://docs.godotengine.org/en/stable/classes

It only has the function you already discovered, which takes PackedByteArray:

TLDR: you have a fair point, but you should bring this up with Godot. We cannot address this on Rust side.

There seems to be a proposal already:
godotengine/godot-proposals#868
It hasn't seen any activity for quite a while, so feel free to write a comment and elaborate your use case.

from gdext.

Closing as answered. Feel free to reference this issue in any potential Godot discussion. Thanks for bringing it up!

from gdext.