I have sent email to spine
Bug after lastest update
- Изменено
I am getting an error when trying to export a .gif sequence on mac - is that the same bug?
Hi!
When I export to JSON, I get this error:
Spine Launcher 1.5.1-full
Licensed to:
Windows 7 x86 6.1
Java 1.7.0-u6-unofficial Oracle Corporation
OpenJDK Server VM
Up to date: 1.6.09
Spine 1.6.09-full, LWJGL
NVIDIA Corporation
GeForce GT 320M/PCIe/SSE2
3.3.0
Started.
Uncaught
java.lang.StringIndexOutOfBoundsException: String index out of range: -1
at java.lang.String.substring(String.java:1875)
at yp.a(SourceFile:88)
at adf.a(SourceFile:794)
at aea.run(SourceFile:57)
at an.d(SourceFile:249)
at ar.run(SourceFile:225)
at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:251)
at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:711)
at java.awt.EventQueue.access$000(EventQueue.java:104)
at java.awt.EventQueue$3.run(EventQueue.java:672)
at java.awt.EventQueue$3.run(EventQueue.java:670)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.ProtectionDomain$1.doIntersectionPrivilege(ProtectionDomain.java:76)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:681)
at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:244)
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:163)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:151)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:147)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:139)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:97)
It's really weird, It's a very simple project (just one animation). If you want, I can send you the spine project
Thanks in advance.
mlwcards написалI am getting an error when trying to export a .gif sequence on mac - is that the same bug?
yes, I think they are the same bug
Damn, sorry! Uploading a fix right now.
anther one,
when I try to create BoundingBox for skin placeholder, it must be error!
What is wrong with creating a bounding box for a skin placeholder? Note the skin placeholder must be empty( must not have an attachment).
Nate написалWhat is wrong with creating a bounding box for a skin placeholder? Note the skin placeholder must be empty( must not have an attachment).
crash!
Ah I see it now, fixing...
For the bounding box problem (which is unrelated to the export crash) just be sure to make a skin visible before adding the bounding box. It's fixed in the next version.
Nate написалFor the bounding box problem (which is unrelated to the export crash) just be sure to make a skin visible before adding the bounding box. It's fixed in the next version.
I got it, thx~
Nate написалFor the bounding box problem (which is unrelated to the export crash) just be sure to make a skin visible before adding the bounding box. It's fixed in the next version.
and I have a suggest about bounding box,
bounding box should become attribute of attachment (just like color of slot or length of bone)
Currently bounding box is difficult to correct use of (user just need describe the pictures)
and is hard to understand ( in which situations we need to switchover image attachment or bounding box attachment ?? ) image attachment should be contain bounding box, should not be a new attachment type!
if do that ,
runtime become more efficient , editor become more easy use about bounding box
Having one bounding box for one image is just one use case. Bounding boxes could be used separately from what images are shown. Eg, you might have the same bounding boxes but many skins with hundreds of images. Or you might be using bounding boxes for physics, where the images shown don't affect the bounding boxes. Also as Spine gets more complex, there will be more attachment types, such as a mesh instead of a region.
yeah~~~
you're right!
popular is more important !
We are having the same problem, when is gonna be released the new version? Or is it possible to download the previous version?
You can revert to a previous version in the settings. A fixed version (1.6.11) is being upload, should finish in the next 10 minutes or so. Sorry for the delay!
Running! Thank you