- Uređeno
Some bugs in 4.0
I am working in Enterprise 4.0.19
Firstly I've noticed that when I save a selection, it initially seems to save everything, but when I return to the selection via the hotkey it actually ONLY saves the bones. Meshes, slots, etc. are all not saved, therefore I cant access any of my alpha, color, or deform keys through the saved selections.
Secondly, I cannot copy/paste alpha keys between animations. Everything else seems to copy paste as usual, but the alpha keys will not. Regardless of whether they are selected as a group or they are selected individually.
Both of these issues create a significant slowdown to my workflow and I would appreciate some help, thanks!
Hi,
I have tried to save selection groups in 4.0.19, and it works even if I selected meshes and slots. How did you select the items?
Regarding alpha keys, you are using the Separate
checkbox of the slot, right? Separate
option is stored in only the animation which you have checked it manually. It means you have to check the Separate
checkbox to paste the keys when you create a new animation, even if it is the same slot. This is not a bug for some reasons, but we’ll improve this. Nate explained about it here:
issue in copying and pasting keys with separated translate
Ok great, so yeah the issue with the alpha copy/pasting was resolved by making sure the settings for the different animations were both set to "seperate". It didn't work when neither were seperated. I don't quite understand why that is a setting specific to each slot and each animation rather than just a global setting though, it seems very cumbersome this way.
With the selection- you have to give it some time. It does initially save. But then, inexplicably, it later stops selecting the slots/images. Just as you are working, within probably 10 minutes, it just stops selecting them with the hotkey. 10 minutes ago I made a selection for 2, just by shift selecting a portion of the tree like I always do. It was working fine for a while. Then suddenly, just now, it stopped working.
Also I've run into an additional problem where I can no longer scale keys in the Dopesheet. It just seems to be disabled. Any suggestions on getting that back?
AnnaB wroteAlso I've run into an additional problem where I can no longer scale keys in the Dopesheet. It just seems to be disabled. Any suggestions on getting that back?
When making the selection hold it for 2 seconds to make the box appear before releasing.
When making the selection hold it for 2 seconds to make the box appear before releasing.[/quote]
Thank you!!
Thank you for telling me about the situation.
I’ve tried to save a spine project file after set a selection group, and slots and attachments selections were not working as you said. Therefore, I made this issue ticket:
https://github.com/EsotericSoftware/spine-editor/issues/602
For your information, I could replicate that bug even if I saved immediately after set a selection group, so time is not related to this problem.
We would appreciate it if you could wait a little longer for the bug to be fixed.
Fixed in 4.0.23! Sorry for the trouble.
Hello,
As I've learnt before, whenever keying shows in orange when auto key is on, it is a bug. So this must be one. AND it makes selected bones and all his children disappear! (:
Here are the screenshots, and the log.
Thanks.
Spine Launcher 4.0.41
Esoteric Software LLC (C) 2013-2021 | http://esotericsoftware.com
Mac OS X x86_64 11.5
ATI Technologies Inc., AMD Radeon Pro 5500M OpenGL Engine, 2.1 ATI-4.6.20
Downloading: Spine 4.0.26 Professional
ERROR: Download interrupted, resuming:
[net.SocketTimeout] Read timed out
at sun.nio.ch.NioSocketImpl.timedRead(Unknown Source)
at sun.nio.ch.NioSocketImpl.implRead(Unknown Source)
at sun.nio.ch.NioSocketImpl.read(Unknown Source)
at sun.nio.ch.NioSocketImpl$1.read(Unknown Source)
at java.net.Socket$SocketInputStream.read(Unknown Source)
at sun.security.ssl.SSLSocketInputRecord.read(Unknown Source)
at sun.security.ssl.SSLSocketInputRecord.readFully(Unknown Source)
at sun.security.ssl.SSLSocketInputRecord.decodeInputRecord(Unknown Source)
at sun.security.ssl.SSLSocketInputRecord.decode(Unknown Source)
at sun.security.ssl.SSLTransport.decode(Unknown Source)
at sun.security.ssl.SSLSocketImpl.decode(Unknown Source)
at sun.security.ssl.SSLSocketImpl.readApplicationRecord(Unknown Source)
at sun.security.ssl.SSLSocketImpl$AppInputStream.read(Unknown Source)
at java.io.BufferedInputStream.read1(Unknown Source)
at java.io.BufferedInputStream.read(Unknown Source)
at sun.net.www.MeteredStream.read(Unknown Source)
at java.io.FilterInputStream.read(Unknown Source)
at sun.net.www.protocol.http.HttpURLConnection$HttpInputStream.read(Unknown Source)
at sun.net.www.protocol.http.HttpURLConnection$HttpInputStream.read(Unknown Source)
at s.Kuj.L(:170)
at s.JrT.L(:436)
at s.Kuj.F(_:111)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Starting: Spine 4.0.26 Professional
Spine 4.0.26 Professional
Licensed to: *****, *****
Started.
OpenAL 1.1, Default audio device
Automatic backup complete.
Automatic backup complete.
Automatic backup complete.
Automatic backup complete.
And now, when I select an attachment in the tree then select another, all in between is selected as if I pressed shift.
AND I can not translate vertices. I barely can select them.
I did a screen recording but can not upload here I guess.
Thanks.
Your log doesn't show anything bad, the error was just an interruption when downloading.
You can upload a screen recording to a site like YouTube or Google drive.
Ideally you could provide 1) your project file (usually we don't need the images), and 2) the steps we need to take to see the problem. That's much better than a video because with a video we have to try to recreate the situation by watching the video, which is hard and not always possible without your project file. If you need to email us files you can use: contact@esotericsoftware.com
The bug you found sounds bad, so we'd be very happy to fix it!
Thanks for the project file. What is happening is that you have set scale Y to zero in the setup pose. Animation values are relative to the setup pose values. For scale, the scale you set in an animation is multiplied by the setup scale. When your setup scale is zero, any value you set in an animation is also zero.
What you can do instead is to leave the scale as 1 in the setup pose and then key the scale to 0 as needed in your animation.
However, a scale of zero is still going to play havoc with math throughout your skeleton. That is why you can't move vertices of the meshes that are bound to the bones with zero scale. What you can do instead is use a scale like 0.0001
. That likely will look the same to you, but makes a BIG difference for the math.
A scale of zero creates a singularity and can be a bit of a surprising special case. We don't want to disallow it since it may be useful sometimes, but it does make for an unexpected gotcha. What we can do is add a warning if zero scale is used on a bone in the setup pose.
Wow, this was interesting. And it makes sense. Good to know.
It works fine with 0,0001 scale as you've recommended.
Thank you very much.