RmB303

Hi.
(First post, and couldn't find a bug report forum)

I cannot run 4.0.22-beta.
Every time I select that version in the launcher, the launcher closes and Spine never opens.
Version 4.0.20-beta runs just fine every time.

Running on macOS 10.15.7
RmB303
  • Posts: 2

Nate

@RmB303 Sorry about that, 4.0.22-beta had a problem on macOS. Please try 4.0.23-beta or choose Latest beta.
User avatar
Nate

Nate
  • Posts: 10750

RmB303

@Nate Beta 23 works fine - didn't notice there was a newer version! Thanks.
RmB303
  • Posts: 2

Nate

4.0.24-beta is now available and brings separate keying of X and Y for translate, scale, and shear! It also allows keying RGB separately from alpha.
Spine: Changelog: v4.0.24 beta
User avatar
Nate

Nate
  • Posts: 10750

Friebel

Nate wrote:4.0.24-beta is now available and brings separate keying of X and Y for translate, scale, and shear! It also allows keying RGB separately from alpha.
Spine: Changelog: v4.0.24 beta
Cool!

Using 4.0.26-beta here I only see one key-button next to these transform (I would expect this button to be split on X and Y) and when moving an x-keyframe in the graph on for example translate, y still moves along over the time axis. Also I only see 'Translate', 'Rotate' or 'Scale' as a property-row in the Graph or Dopesheet, not TranslateX/TranslateY etc. So far I'm not seeing buttons to sync/not-sync x and y in the UI neither.

So don't see a change really, but I'm probably missing something here?! How can we put keyframes on only x or y of the transforms in the editor?
User avatar
Friebel
  • Posts: 48

Nate

When you select a bone in animate mode, it has 3 new checkboxes:

When checked, you'll get separate X/Y timelines for that bone in the current animation. The same goes for slots to separate RGB and alpha:

This allows us to support both combined and separated timelines. It's slightly more efficient to use combined timelines (fewer timelines the less work to apply an animation) unless you key only X or only Y, but the main reason we allow combined timelines is that fewer timelines are easier to manage. If all translate timelines were separate X and Y timelines, it could mean 20+ additional timelines for a moderately complex skeleton (1 extra timeline per bone that keys translation).
User avatar
Nate

Nate
  • Posts: 10750

foriero

I suppose we are two weeks from 4.0 full release right?

And multi monitor is around 3 months away, right? :-)
Founder & CEO Foriero s.r.o.
https://studio.foriero.com
User avatar
foriero
  • Posts: 439

Kani

Hi,
Any ETA on cocos2d-x runtimes? Beta and manual integration is ok :)
Kani
  • Posts: 1

raaan127

Hello,
From version 3.8 and below, I can box select a bundle of keyframes and stretch them but it seem to be no longer exist in spine 4.0
How can I be able to do the same in 4.0?

stretch-keyframes.jpg
You do not have the required permissions to view the files attached to this post.
User avatar
raaan127
  • Posts: 11

Nate

In v4.0+, make the box selection, then wait about half a second until the edges turn blue, then you can drag the edges. This allows you to box select without having the big box in the way, unless you need it.
User avatar
Nate

Nate
  • Posts: 10750

Rajah

Nate wrote:In v4.0+, make the box selection, then wait about half a second until the edges turn blue, then you can drag the edges. This allows you to box select without having the big box in the way, unless you need it.
Long time Spine user here, I switched to the v4-beta today, overall, fantastic and exciting new features - but I searched for this for about an hour lmao I was all panicked the dragging option would have been disabled (for no reason?), I almost switched back to good ol' Spine v3 because I couldn't figure how to expand my anymation anymore. It's a major change to a core feature when you're an old time user and I think I'm not the only one who will be confused - But maybe you made a notice about this somewhere and I missed it? Sorry if that's the case.

This new selection system works fine tho, it's very pleasant.

Thank you for your hard work I'm very satisfied with this update otherwise.
Rajah
  • Posts: 1

Nate

Sorry Rajah! The delay is pretty low, I expected people to find it after a couple tries. Maybe lowering it a little more would help.
User avatar
Nate

Nate
  • Posts: 10750

SysOp

Hi guys, for some unknown reason, when trying to run latest launcher, I'm getting this:



I'm on Windows 7, 64 bits. Never had this issue with previous launcher. Here's, in fact, the two of them:



Anybody has any idea what's going on? Thanks in advance.

EDIT: More information - I don't have any antivirus running, I don't have any programs that might hook its process or something, that I know of. Tried disabling firewall, disabling AMD Radeon overlay, doesn't work either.
EDIT2: Seems like my multi-monitor management software might be the culprit, but it's hard to know.



I just can't simply uninstall that software. Can you guys revert this new system back or make it less sensitive? I don't see why this is a good idea at all. It was working perfectly fine before.

EDIT3: It also detects Comodo Firewall .dlls and won't run because of it. I can't uninstall that either.
User avatar
SysOp
  • Posts: 18

Nate

It's likely Comodo Firewall causing the problem. Another user had the same problem with it:
Unable to launch

Comodo Firewall attaches to Spine's process and mucks around with things even if Comodo Firewall is disabled. That is quite nasty behavior, especially for what is supposed to be a firewall. You said you can't install it, is that because you need a software firewall? If so I can suggest using Windows Firewall Control instead, as I mentioned in that thread.

We have had lots and lots of problems with antivirus wrecking Spine. Sometimes they prevent Spine from running at all. Sometimes they let most of Spine work, but break some parts so it crashes later. Sometimes they let Spine run for a while, then delete or modify Spine's files later. When this stuff is happening, it creates a lot of noise for us. It becomes difficult or impossible for us to tell whether a crash is because there is a legitimate problem we need to fix, or if an antivirus has caused the problem. Users suffer crashes and other problems, contact us about them, and it takes a lot of our time to research the issues.

That is why it's much better to know that other software is poking holes in Spine so it can be fixed up front. Running software that mucks around in every application running on your computer is generally a bad idea. It causes problems with other software, it slows everything that runs on the computer, and it provides very little to no actual protection.

I know you are having a specific problem and would like to solve that. I expect uninstalling Comodo will be sufficient, so I hope that is possible. I doubt UltraMon is a problem. Process Monitor logs a whole lot of stuff for many reasons and not all of it is not important.
User avatar
Nate

Nate
  • Posts: 10750

SysOp

Hey, uninstalled Comodo and it works!



I thought disabling it was enough, but I was wrong. I'm done with Comodo, is not the first time something similar happens.

Thanks for the help and for providing alternatives. ! Curve editor, here I go :D
User avatar
SysOp
  • Posts: 18

Nate

Great to hear!

Comodo is really bad. I wonder if we should detect it specifically and make it clear that it should be uninstalled. I hate that they create pain for Spine users and work for us!
User avatar
Nate

Nate
  • Posts: 10750


Return to Spine