Soft selection is enabled through the new Mesh Tools view:Then when you make a selection, vertices within range of your selected vertices show up a shade of cyan/blue:When you move the selected vertices, the blue nearby vertices are also affected based on how far away they are. Eg, here I moved the vertex down:This works for translation, rotation, and scale on vertices. Here's rotation:This can be much easier than moving each vertex one at a time, as this GIF from the blog shows:Here's a pro tip: you can ctrl + alt + click to remove a soft selected vertex from the soft selection. Note if you then select a new vertex, soft selection will be applied again.

Erikari hat geschrieben:I like how he totally walks like a boss and then you slightly zoom on him after 2:11 Can't wait for the devs to say the new runtimes aren't causing issues in our game to start using it!

Thanks!

I've only been animating with preview active for the short time it's been there. It's a lot of fun tweaking animations with it running. You instantly see all the small nuances of the animation if it's playing while you're editing.

i'm curious about the lighting on the tint black section on the tank. How do you achieve that partial illumination on the side of the tank? is it just the glow from the explosion or is there a way yo light up a clipped section of the sprite?

Maybe it's something that has no connection to the actual update, i'm sorry if it's off topic.

If you download the Spine installer and run it again, you'll get the latest example projects and you can see the tank firsthand. The selection in this screenshot is the clipping attachment, which is clipping a 3 vertex, additive blended mesh:Clipping can get expensive, so it's best to clip as few vertices and attachments as possible. Be sure to test CPU usage for what you are doing at runtime before going too crazy with it. While the tank and the new coin example use clipping for lighting effects, that is not its only usage. Eg, the spineboy portal.

Nempatriarch hat geschrieben:i'm curious about the lighting on the tint black section on the tank. How do you achieve that partial illumination on the side of the tank? is it just the glow from the explosion or is there a way yo light up a clipped section of the sprite?

Maybe it's something that has no connection to the actual update, i'm sorry if it's off topic.

The glow on the side of the tank is done by using a Clipping to mask out an attachment set to Additive blending.

Another example of this effect is used in the Coin example that comes with the latest launcher.

I'd just like to say that all the editor updates are awesome of course, but I appreciate the attention you also are giving to improving the runtimes and the repos. Your previous move to keeping the runtimes in pace with latest editor release features was huge, and now moving to versioned branches for the repo is another big improvement. So thanks for the awesome work.

Any thoughts on separating the individual runtimes into their own git repos? For one, reading the commit history would be a lot more useful, as it would not be interspersed with other platforms I'm not using. Would also make importing just what I need as a git submodule for example a lot easier.

I'm considering moving the runtimes to individual git repositories and making them submodules of the main repository. It's a bit complex to unwind the example projects, but it's on my "will look into this option asap". FWIW, every runtimes specific commit is prefixed with `[runtimename]` so you can filter the logs more easily.

We discussed it a bit here:Separate repos · #758Submodules would be convenient for users to pull in the Spine Runtimes, but quite inconvenient for runtime development. Git submodules are a bit of a half-baked Git feature (look, a haiku. uhhh I hate mornings). I would much rather Git implements a better solution to the problem of pulling in part of a repo without causing the repo maintainers grief.

Hi I am new to the forum and have been using Spine for just a few months.

I just updated my Software today and started working on a file i made from the previous version. it worked but after saving the file and closing the program, when I started it up again, I am getting this error message.

"Sorry, an error occurred while reading the project file.

project version: 3.6.34spine version: 3.6.34"

help... i am running late on deadlines and this update has set me behind T_T

What was the previous version you were using? Spine saves backups every 15 minutes in the backup folder so if you're lucky you might find a very old version, try matching the editor with that version by downgrading it, and then go on working.