[BUG] Folding line at first deformation point will lock the path

Ran_TH

To reproduce the issue:
Create a deform path
Then do "Fold line" at the first point

Then the path will get 'locked' and logs will show this error

[INFO ] Open Curve range must be 0 until node.size-1
[INFO ] node size = 1, pointNo = 3, time = 0.0
[ERROR] java.lang.ArrayIndexOutOfBoundsException
[ERROR] java.lang.ArrayIndexOutOfBoundsException

Unfolding the first point will fix the issue,
However it wasn't obvious, and caused confusion with users.
I hope to see it fixed, at least if user folded the first point it should not 'lock' the whole path.

Live2D Cubism 4.2.02
Windows 10

Enoko(Staff)

@Ran_TH

Thank you for your continued use of our product.

Thank you very much for reporting the problem.
We apologize for any inconvenience caused.

The problem was not reproduced in our environment.
Please take and paste a video capture of the problem so that we can better understand how it occurs.
Please make sure that the log palette is also visible.

In addition, please send us the full log file.
Please refer to this page for instructions on how to obtain the log file.
https://help.live2d.com/en/other/other_22/

Please submit the log file you have obtained from this upload page.
https://biz.datadeliver.net/posts/Ux43LQPzD5QR

We apologize for the inconvenience.

Ran_TH

Thank you for your response.

This is the expected fold line behavior, if you Fold line at the middle point.


This is when you fold line at the first point, which makes the whole path 'locked'.


I have submitted the log file to link you sent.
Thank you.

Enoko(Staff)

@Ran_TH

Thank you for your reply.
We will check the file you sent us.
We would appreciate it if you could give us some time.

Thank you!

ueno(staff)

@Ran_TH
We apologize for the delay.
We are investigating this phenomenon.
We may contact you again to assist you in investigation.
We apologize for the inconvenience and would appreciate your response at that time.

Thank you for your report.
Best regards.

Enoko(Staff)

@Ran_TH

Thank you for waiting very long.
We have fixed the bugs you reported in 5.0.03 beta1.
Please try it.