Animations don't allow enable/disable of components about needle-engine-support HOT 7 CLOSED

Correct, that's a current limitation of our animation export. We're exporting animations using the KHR_animation_pointer extension, and that probably needs a special case for enabling/disabling of objects. Will look into it!

from needle-engine-support.

Ah, great! If onEnable/onDisable firing when the animation sets the gameobject itself active/inactive too that would be good as sometimes I would rely on onEnable/onDisable during animations

from needle-engine-support.

@ROBYER1 you can (as a workaround) declare this property on Needle Engine objects too. You are in javascript land after all 😅

Just add the following code somewhere in your scripts, that should do the trick:

Behaviour.prototype["m_Enabled"] = function(value) {
 this.enabled = value;
};

from needle-engine-support.

@ROBYER1 you can (as a workaround) declare this property on Needle Engine objects too. You are in javascript land after all 😅

Just add the following code somewhere in your scripts, that should do the trick:

Behaviour.prototype["m_Enabled"] = function(value) {
 this.enabled = value;
};

I'll be sure to try this!

from needle-engine-support.

I can also add it to our component in the next update until it's properly fixed in the exporter. But just so you know as it might not the last time 😅

from needle-engine-support.

Ah sorry I have to correct my comment above. In this case you have to declare it as a property. But it works the same way

Like this:

Object.defineProperty(Behaviour.prototype, "m_Enabled", {
    set: function m_Enabled(val: boolean) {
        this.enabled = val;
    },
    get: function m_Enabled(): boolean {
        return this.enabled;
    }
});

from needle-engine-support.

This should work in 2.20.0 pre now by default

from needle-engine-support.