Weird GDNative property behavior

msik314

I'm experimenting with native scripting and exposing properties in the editor. I've run into a pair of strange issues that don't seem correct to me. Both the issues seem to me like I'm doing something wrong, but I don't know what. This is the current state in the editor. Notably the speed is set to 120 and the vertical axis is set to 1.

Problem 1: SOLVED Even though the vertical axis is set to one, the C++ class never sees it set to anything other than 0. Moving the left stick sideways results in the sprite moving diagonally. The keyboard and dpad controls still work normally. EDIT: Defaulting this to 0 makes it work as expected, so this really is a symptom of the other problem.

Problem 2: The movement speed is defaulted to 0.0f. If instead I default it to something less than about 4, the script works as expected, and the editor value of 120 is used. If I default it to something like 8 or 120, the script stops functioning because the C++ side only sees the value of 0. Then, changing the value and recompiling the library doesn't restore the functionality of the script.

EDIT: I failed to mention this earlier, but I'm using MinGW-w64 on Windows in case that matters.

dotted

My very first guess is you need to add setters and getters for the reason that this is how the engine will be able to inject the editor values into the object.

msik314

@dotted said: My very first guess is you need to add setters and getters for the reason that this is how the engine will be able to inject the editor values into the object.

I don't think that's the answer because defaulting things to 0 and then setting them in the editor still works. I tried it with the vertical axis and it let me move as expected. I guess that solves my first problem, but the second one still is open. Also the godot-cpp example uses this syntax for properties.

TwistedTwigleg

Maybe its GDNative 1.1 syntax instead of GDNative 1.0? I think there was some changes between versions, so its possible the Godot-Cpp example wasn’t updated or something. In the Godot C++ source, you have to define setters and getters for any exposed properties, so it might be a requirement now for GDNative (not sure).

As for the second issue, are you setting m_speed anywhere in your code? I didn’t see anything where I looked, but the init function isn’t included in the screenshot, so if you are setting m_speed there then I would see if removing it helps. Another thing to check is if you make the variable, m_speed, public if that fixes the issue. I’m not sure how Godot maps properties, but it could be that the variable has to be public for the Godot code to access it via the register_property function, though I’m just guessing.

msik314

I guess I phrased it poorly, but the problem is not that it never updates. The problem is that it only updates if the value provided as the final argument of te register_property() call is 0 for integers or close to 0 for floating point numbers.

dotted

Try setters and getters. The problem may be one of casting values in the engine when it updates the property.

msik314

@dotted said: Try setters and getters. The problem may be one of casting values in the engine when it updates the property.

I finally got around to making getters and setters. Turns out it still doesn't work.