When the layer time is reversed, NearestKeyIndex() behaves unexpectedly. It always returns 1, which messes up all calculations. I've searched online for a solution, but it seems this problem has been discussed for over 10 years. Do you have any plans to address this issue or add more functionality for working with keyframes? Alternatively, a suggested workaround would be greatly appreciated to help me complete my project.