Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

LeanTween.delayedCall() is bugged/unreliable, will occasionally not perform call #177

Open
JegoMx opened this issue Apr 4, 2023 · 3 comments

Comments

@JegoMx
Copy link

JegoMx commented Apr 4, 2023

We're using delayedCall() throughout our project but have noticed that every now and then (and more frequently at higher timescales) the action given to the function is not executed. The tween starts, and attaching an .setOnUpdate() method with a Debug.Log inside shows that the tween is running, until it suddenly stops for seemingly no reason.

It doesn't seem like it is getting cancelled, it just simply... stops. I have tried attaching the debugger/leaving Log calls all throughout the LeanTween class but can't seem to figure out what is causing this issue.

Needless to say this is a very frustrating issue and we're in the process of removing all calls to the bugged method. Is there some sort of setting that we might have configured wrongly, or is this truly a bug? I have found other similar bug reports on google, but those threads mention that the issue should be resolved in later updates. We're using the latest Asset Store version 2.51 on unity version
2020.3.15f2 LTS.

@Eversor
Copy link

Eversor commented Feb 26, 2024

Hello @JegoMx did you happen to find the culprit? I'm having the same issue with a live game and it's pretty bad. Could it be that the garbagecollector is destroying the tweens that have not completed yet? I'm having the same exact unreliability in recreating the issue. Versions are 2.51 and 2022.3.5f1

@JegoMx
Copy link
Author

JegoMx commented Feb 27, 2024

Hey @Eversor , unfortunately we never did, and moved to a DOTween instead. It's been a while since having this issue, but iirc it had something to do with the tweens being recycled/reused before they were actually finished.

@Eversor
Copy link

Eversor commented Feb 27, 2024

Yes, i can definitely confirm the issue could be that, checking the source-code there is nothing preventing to hold a reference to a cancelled and then reused tween. If one were to cancel using the reference you would cancel the new tween instead. I also moved to DOTween that is essentially overlapping all the functionalities.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants