0
Fixed (Unreleased)

Curve editor in Area Clock 2D is not updating the curve

Vicenzo Pegado 2 years ago updated by Lazlo Bonin (Lead Developer) 2 years ago 3

I just bought Chronos, and started doing the tutorial. 
But, in the step 9 (Adding an area clock) I encountered a small bug. 
https://support.ludiq.io/forums/2-chronos/topics/32-adding-an-area-clock/

Was said that i could edit "a curve in the inspector that allows us to specify how the time scale will progress along the area clock". And, indeed, i am able to do that. I can even save the curve as a preset. So far so good. 

But, that is not useful at all, because the curve in the Area Clock 2D component is not updated accordingly. Stay the same as in the default configuration. 

I will provide pictures below, to illustrate the situation. 

And I thank you in advance for the help. 

Image1 - The default configuration. 


Image2 - the curve editor


Image3 - Editing the curve



Image4 - Saving as a preset



Image5 - Clicking out of the editor - the curve stays the same as before. Was not updated. 



Image6 - Clicking again to edit the curve, it stays the same as if it was never edited. 

Image7 - But the preset still there. 



Chronos Version:
2.4.12
Unity Version:
2017.2.0f3
GOOD, I'M SATISFIED
Satisfaction mark by Vicenzo Pegado 2 years ago
Pending Review

Hi Vincenzo, sorry you're experiencing this issue.

If you click on your preset again after step 7, does it select the preset and apply it to the curve?

Hello, Lazlo.

Thank you for your quick response. :)

If i click in the preset, it apply the changes to the curve in the editor, but not to the curve in the component. It remains the same don't matter what i do. 

I feel like the editor have some invisible save (or apply) button that i'm not being able to click. But i suppose this button don't exist and the changes are supposed do be update automatically. 

If you need any further information that will help you (and me) to solve the issue, just ask. ;) 

+1
Fixed (Unreleased)

Hi Vincenzo,

Sorry for the very late reply.

I've hunted the bug and it appears to be a Unity bug in 2017.2.

See:

It's unclear from these threads whether Unity will actually fix it or considers it already fixed. I commented on both issues to bring it to their attention.

I've found a workaround that works for both 5.6 and 2017.X and will push a fix version on the asset store.

Thanks for your report & patience!

Lazlo