- Editado
Path Constraint question
Hello! So today I wanted to join a small jam and decided to try out the path constraint function. I wanted to apply it to the hair of a falling character and started to do the chains.
For the first 3 I did it was ok, but this third one seems to have a strange offset. Did I do something wrong?
I noticed that when it creates the constraint, it starts in tangent mode and offsets all the bones I placed outside the path, and when I change the mode to scaled chain it still remains in offset. I must also add that I did this today and the other 3 yesterday. (it seems to make a difference with bugs in older versions whether I had restarted spine or not)
Image removed due to the lack of support for HTTPS. | Show Anyway
HAH I tried to undo the path but I had saved the project, so I tried to delete the path constraint and the program crashed.
Here the report:
Spine Launcher 3.4.00
Windows 10 Pro N x86 6.2
Java 1.7.0_80 Esoteric Software
32-bit Server VM
Up to date: Spine 3.4.02
Spine 3.4.02 Professional, LWJGL
Intel
Intel(R) HD Graphics 4600
4.3.0 - Build 20.19.15.4444
Started.
Sorry, an unexpected error has occurred:
java.lang.ClassCastException: AS cannot be cast to AJ
at JV.b(SourceFile:157)
at fp.a(SourceFile:91)
at gx.a(SourceFile:28)
at eH.a(SourceFile:181)
at eH.a(SourceFile:152)
at com.badlogic.gdx.scenes.scene2d.ui.Button.b(SourceFile:123)
at fj.b(SourceFile:91)
at gz.b(SourceFile:89)
at eN.a(SourceFile:58)
at eP.b(SourceFile:353)
at o.b(SourceFile:96)
at av.e(SourceFile:332)
at ah.run(SourceFile:236)
at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:312)
at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:745)
at java.awt.EventQueue.access$300(EventQueue.java:103)
at java.awt.EventQueue$3.run(EventQueue.java:706)
at java.awt.EventQueue$3.run(EventQueue.java:704)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.ProtectionDomain$1.doIntersectionPrivilege(ProtectionDomain.java:76)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:715)
at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:242)
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:161)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:150)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:146)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:138)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:91)
Path constraint has so many knobs, it's hard to say if it's a bug or just how you've set it up. The crash is not good. Does it happen every time? Does it happen in 3.5? Unfortunately the log isn't enough to fix it in this case. Can you post or email the project?
I tried to repeat the steps but this time it didn't crash. If and when I'm able to reproduce it for sure, I will post it!
(by the way paths are SO beautiful! Thank you so much for making them!)
Although I still have no idea of what I did wrong 
I guess in a month or two I'll look back at this and laugh at my own noobness.
Ah, ok. Bugs like that are difficult to reproduce and therefore fix. 
The project would still be helpful if you are seeing path behavior that you think is strange. Paths constraint is very complex, but very thoroughly tested and should be working as designed. Some configurations may not be terribly useful, others work correctly but it may not be readily apparent why. Read the docs very carefully about how it chooses the rotation, etc for each bone using the various modes or we can help by checking your project. 
Path Constraints - Spine User Guide
Well I sent it now and I'm also reading the documentation >.< thank you
Using chain mix should have resulted to bones thingtly on the path. Oh, I have no idea S:
I see the bones aren't on the path in 3.4.02 but they are in 3.5.03-beta. I'm not sure exactly what the problem was, but it seems it has been fixed. :angel: You're right that chain scale should always result it he bones being on the path.
Nice art BTW!
Oh, I should go to beta version then! but that won't be up-to-date with the various runtimes I guess S:
Thanks for checking on a sunday evening >.< (and thanks)