Unity SpriteShape Preview Package

I have been waiting for this for a long time, glad its finally here. I have been using it for a few hours now and have some feedback and questions.

1. The RGBA values are linked to the wrong channels from the inspector. The R is adjusting the A, the G is adjusting the B, and vice versa.
2. When I set sprite to medium or low, the corresponding medium / low collider doesn't match it.
3. You should be able to manually overide selected angles.

I am using latest Git release of the plugin as 18:00 GMT - 21.3.2018, and Unity 2018.1b11.

 

Looks great! Any chances of extending the bezier spline deformation so it could be used for animating/deforming 2d characters aswell?

Rayman legends uses a bezier patch deformation technique for their character animation/rigs. You get that nice deformation instantly for free without the need to manually paint skin weights in a 3d software:

 

I am getting a crash when I roll a ball (circle collider) over a SpriteShape. I have included a screepcap below to show exactly what the SpriteShape collider looks like.

When rolling the ball along there, sometimes it crashes in seconds, sometimes it takes 5 minutes, but it will always crash. Built to Windows.



The Output Stack:

0x000002549E3F85AC (Mono JIT Code) (wrapper managed-to-native) UnityEngine.Collision2D:FreeContacts (intptr)
0x000002549E3F84E0 (Mono JIT Code) UnityEngine.Collision2D:Finalize ()
0x000002549E30A649 (Mono JIT Code) (wrapper runtime-invoke) object:runtime_invoke_virtual_void__this__ (object,intptr,intptr,intptr)
0x00007FFA54F78535 (mono) mono_gc_is_finalizer_thread
0x00007FFA5509CF66 (mono) mono_unity_class_get
0x00007FFA54F78865 (mono) mono_gc_is_finalizer_thread
0x00007FFA54FE40C3 (mono) mono_thread_interruption_request_flag
0x00007FFA5509A05F (mono) mono_unity_class_get
0x00007FFA7B4D1FE4 (KERNEL32) BaseThreadInitThunk
0x00007FFA7DF1EF91 (ntdll) RtlUserThreadStart

No files generated in the crash folder.
There are no errors in the editer, I tried performing the same actions in the same place, no problems at all.

Unity 2018.1b12

 

When I click on Edit Spline no control points show up, and also the option to change the point mode is grayed out. Any suggestions?



edit: I found a solution. Resetting my workspace to Default fixed the problem for some reason.

 

thankyou, been waiting for this a long long time

 

I'm not sure how to explain this, but I noticed that if I create a new sprite shape profile and add a sprite on top but not on bottom, any created shape will disappear when the camera moves down

Also, I honestly think the offset slide should be for the sprites not the fill texture.
Sometimes the user may want the collider to go over the sprites he set up. Specially for ground surfaces and the collider offset will just not be efficient if your shape isn't a flat surface

Here are some screenshots:

https://imgur.com/a/cbMmT

Other than that, great job! Been waiting for this for a while now!

 

Hello!

I am playing around with SpriteShape, but was wondering how I could go about accessing/modifying different points on the Spline via script? I tried looking at the Scripting API, but my tinkering so far has led to no results. I would appreciate any tips that could point me in the right direction!

 

3 questions:

1. Is the spline editor used in this tool available as a separate component / is it possible to create my own without having to actually reeimplement in some major way? I'd love to use it as a general tool. It could even be used to implement "meta-friezes", as UbiArt calls them (which are basically multiple friezes (smartsprites) driven by a single spline).
2. Is there a keyboard shortcut/global setting to toggle Edit Spline? First thing I noticed was how much it bothers me to have to click my way out of the scene view to enable it.
3. Is it possible to move multiple selected points at once? I feel like I've already done it, but now it doesn't seem to work and I'm thinking it might be a bug. Edges between selected points are not highlighting either, if they've ever done that.

Also, some suggestions on improving the workflow

• Shift+clicking to a add new point on cursor position. Ferr2D does it and it seems to make quite a lot of sense, although I have not used it yet. That is to say, I know it is possible and not being able to do it makes me uncomfortable.
• Shortcuts to change point modes (if possible, one that pops up a context menu in cursor position with all point related settings)
• Esc my way out of Edit Spline to allow selection of another object. The only way I've found how to do this currently is switching tools, which is not really that bad, but because I like the Rect Tool better to work in 2D I find it quite annoying to use since it is bound to T. I'd very much like it better if I could just Esc back to my last selected tool.

I'll probably come up with some more questions / suggestions as I test it, but so far, I like very much what I've seen. Please, keep it up!

 

Thank you so much! Can't wait to play around with it!

 

So I can't seem to find SpriteShapeController - it says it is missing an assembly file or something.


This is my manifest.json

Code (Boo):

1. {
2.   "dependencies": {
3.   "com.unity.2d.common":"1.0.8-experimental",
4.   "com.unity.2d.spriteshape":"1.0.9-experimental"
5.   },
6.   "registry": "https://staging-packages.unity.com"
7. }

And in my C# script I am

Code (CSharp):

1. using Unity.Experimental.U2D //whatever it's called

 

Good news!
Just submitted it
ID: 1019411

 

Yes, I know about those. What I meant about the meta-friezes thing was something like this:

Multiple SpriteShape equivalents being driven by the same curve.

Oh. Funny, I though I'd tried bashing through the entire keyboard. Well, I was very sleepy by that time. Thanks!

Wow, that sounds very counter-intuitive for me. Is there a UX/Technical reason as to why it's necessary to hold Shift while doing it instead of just having the points selected and dragging one?

Thanks for the attention!
Also, I'm sorry if I've been sounding too bratty about this. It's just that this is a tool of major importance for me, so I'm very much worried about it being consolidated in a less than perfect manner. It's already very good, but it could easily be better and I'm sure other people might have some nice ideas about it as well.

 

I can't believe I missed that the sprites are place on the spline based on their pivot haha

 

Hi Venkify,

I was just wondering if you saw my post regarding the inability to reference the SpriteShapeController. I have the correct Manifest.JSON and using headers.

 

Okay, thank you

 

Yes, that's very much what I meant. What I thought of in terms of implementation was having a Spline Component in the main GameObject, the children each having one of the SpriteMeshes. In the parent object I would put my MetaSpriteMesh thing, which would reference a base Spline (in this case the one in the same object) as well as a list of tuples of all affected SpriteMeshes and their individual Vector3 (or even full-on Transform) offsets. Using the imported sprite's pivot to avoid the need of manual offset is cool though, haven't though of that. For some cases it surely would be handy.

Thanks! I'll surely be following the development of the tool.

 

Is this going to be available to use in unity 2018.1?

 

same question

 

same

 

It's available right now to use with the public 2018.1 beta so it's almost definitely going to be available to use in the full release of Unity 2018.1.

Whether it's going to lose its "experimental" tag before the full release of Unity 2018.1 is unknown but I would lean towards assuming not. But it's available now for testing so if you want to use it, you can.

 

How do I set spline detail from the code? This is what I currently have

Code (CSharp):

1.  //Add the sprite shape components needed to make the generation
2.         SpriteShapeRenderer ssR = newTree.AddComponent<SpriteShapeRenderer>();
3.         SpriteShapeController ssC = newTree.AddComponent<SpriteShapeController>();
4.  
5.         //Make a reference to the spline
6.         Spline mySpline = ssC.spline;
7.  
8.         //TODO : Set the spline detail so it can render stuff
9.        ------- stuck here ----
10.  
11.         for (int i = 0; I < points.Count-1; i++){
12.  
13.             //Set up our spline points
14.             mySpline.InsertPointAt(i, points[i] );
15. }
16.            

 

My first thought: This feature demands native support for Vectors/Splines/.svg !

I just returned from some years Unity absence and this is a nice surprise. Exactly what we need.
So far no bugs for me.

Transparency in fill & border produces visible overlay problems (obviously), when the fill has +Offset. 0 Offset on Fill + Bottom Pivot on the Border on the other hand leads sometimes to little gaps. But I guess this can be minimized with carefull sprite planning. I just pushed the Endless/Purple assets around and it seems to be more glitchy the thicker the border is.

 

Sorry for the plethora of issues,


but "ArgumentException: shapeParams.splineDetail (0) must be within 4 - 32." comes up, and I cannot figure out how to use the struct.

 

A minor usability request:

When editing a Sprite Shape Controller, the Sprite Index Slider goes from 0 to 63, regardless of how many Sprites are defined in the Sprite Shape list. Would be nice if that slider would max to the actual number of items in that list. (But this probably may be not so trivial to implement, since every range can have a different number of sprites in it's list...)

Related: Also nice to have would be a "Random Sprite Index" checkbox in the controller. This is probably easy to script, I did'nt try it yet. But, of course, it would be cooler to have this without additional user code.

 

Okay! I am currently trying to spawn a SpriteShape along a user's mouse input to create, say, a tree

 

I will try this a little later but first I have a number of questions:

• Does this support holes in the sprites? This is something I implemented in our internal version of Ferr2D by introducing the concept of subterrains. The subterrains were individual Ferr2D components, allowing full edge editing etc. but they were bound by the parent terrain and would be fed into the parent's triangulator with reverse winding. Very useful for complex layered terrains.
• Does it support local overriding of the edge graphic at a control point, ignoring the angle?
• Most importantly, does it come with source?

 

Thank you for your help! I appreciate the support you've been giving to us

 

Is there a way to modify control points on their z?

 

Could you make colliders work better considering also the height of the spline? I'm trying to use the new feature to build a sort of 2d race track but i can't make my collider match both the inner and outer bound of the path.
Also, there are gaps because of the texture not being applied properly.

 

I discovered that it was an error on my side, there were some pixels at the border that were slightly transparent.
As about the collider i guess that you should add the chance of having different kind of colliders/collider modes.
Right now i can think of having a polygon collider for the shape, one edge collider for outer border and one for inner border (so we have four modes: polygon collider, inner border, outer border, both borders).
And obviously it should actually match the different heights of the shape, right now it doesn't.
I'm using a workaround and setted all my heights to 0.8 but i can't have different height values as you said.
This way you can use this tool in a way that i guess you didn't thought about before such as 2D race games with a track.

 

Not sure wether this is supposed to be posted here,

I tried this on 2018.1.0b12, 2017, 2018.1.0.b13 and just now 2018.2.0b1, but I fail to open the SpriteShape on my windows 8.1 There are missing scripts and the samples don't render. As shown in the spoiler:

Spoiler

The manifest.json that came along seems to be right, just like on github. It has been unzipped. I imported it to the projects assets folder.

Maybe this is useful
ProgramData>Unity>cache>npm>packages.unity.com>com.unity.2d.spriteshape>.cache.json gives:
"{\"error\": \"not_found\", \"reason\": \"document not found\"}"

Any idea what I am doing wrong? I am really looking forward to use this tool.

 

Ofcourse, Rustum

Spoiler: ExpandedProjectView

 

@Venkify Yes that's exactly what i'm trying to work on thank you for the advice . Could you please do something about the height issue and the modes for the collider? In my specific case i guess (still have to try) that i could achieve what i'm trying to build by setting the collider at minimum offset, copy the collider and then change the offset to its maximum value by code, but of course i would really appreciate having an option for that . But still, i can't to that with the height issue that i mentioned before...

EDIT: i've tried using the bevel cutoff as you suggested and i have got even more problems with the collider unluckly. I still need to activate the tangents to get the collider follow my curve. With the straight line point to point mode, the collider actually follows the straight lines without following the rounded bevels. I guess that the issue is that the collider, as it is now, will always be based on the setted curve and not on the actual shape that the sprite has, which works nicely in a lot of situations but it is a big limitation in a lot of other scenarios.