Tween Conduct Challenge After Replace to Model 3.8.7 – Cocos Creator

After updating to Cocos Creator model 3.8.7, we’ve encountered a regression in how tween behaves when concentrating on inactive nodes.

In earlier variations, tweens would nonetheless execute even when the goal node was lively = false, which allowed us to run delayed logic like the next:

node.lively = false;
tween(node)
.delay(0.25)
.name(() => {
node.lively = true;
})
.begin();

This conduct was crucial to our animation circulation and labored completely in prior variations. Nevertheless, as of three.8.7, it seems that if the node is inactive when the tween begins, the tween doesn’t run in any respect, breaking all associated logic throughout our venture.

This modification has triggered important points and damaged many current techniques that depend on tween-based activation sequences.

We’d wish to ask:

1. Is that this an intentional change in 3.8.7?
2. If sure, may you please level us to the associated changelog or documentation?
3. If not, we consider it is a bug and would respect it being addressed as quickly as attainable.

Thanks to your help, and we stay up for your steerage.

We respect your continued work on enhancing the engine.

Pls observe that the conduct you point out, has already mentioned within the subject of 引擎从3.8.3升级到3.8.6后，tween缓动细节差异导致bug – Creator 3.x – Cocos中文社区

If the goal of the tweet is Node, then the pause, resume, and destroy states of the tweet have to be related to Node. I feel the conduct of Creator 2. x is affordable, in any other case customers would want to handle varied states of their very own Tween. If a node is in a disabled state with lively set to false, it’s illogical for its properties to proceed to be up to date by TweenSystem. So in v3.8.4, we made this optimization to keep up consistency with Creator 2. x.

The Launch Word v3.8.4 states this:

Contemplating that there are nonetheless some customers who might not need Tween to affiliate with Node standing, we plan so as to add an interface in 3.8.7 for customers to shut this affiliation. See:

Thanks to your response.

I consider this conduct must be explicitly uncovered as an engine macro setting.

This function has a crucial affect on how tween-based logic features throughout tasks, and adjustments to it may well simply trigger widespread unintended negative effects if not correctly managed.

Making it configurable by way of a clearly named engine macro would enable builders to choose in or out deliberately, relying on the model or venture wants.

Thanks once more to your continued help.

sure good publish, liked to examine it, will come once more quickly to get the up to date information

Hello @Tom_k , customized enginge like this ?