Этот сайт лучше всего просматривать в современном браузере с включённым JavaScript.

Weird texture tearing?

Xelnath

What does this bug indicate? (notice the legs turn a weird shade of orange - like its reusing the face.)

Pharan

Whoa. Looks like UVs doing weird stuff.
In cases like this, it's useful to capture the video in Scene view and select that GameObject so you can see the mesh.

Can you email us that scene? Looks like the renderer might be doing something weird. Have updated to the latest runtime recently?

Xelnath

Yeah, I update the runtime weekly.

This scene is pretty massive - as is the project.

Would it be OK if I sent you a github link privately?

-Alex

11 Jun 2016, 07:58

Here's the scene view, it's almost unreadable though.

Pharan

You should scale down the gizmos slider. Maybe way down.

Can you just send the skeleton data and atlas instead for now? Maybe that's enough to repro.

Xelnath

The gizmo slider appears to have no effect upon those bones.

The slider is all of the way down.

Pharan

Oh, I get it now. I guess this is what happens when you scale down your GameObject's transform. (I assume that because your level is pixel art).

Damnit, @Mitch.

This has nothing to do with the mesh errors though. It's just that those bone overlays are in the way.
You could collapse the SkeletonUtility component's Inspector temporarily and that would get rid of the bone overlay.

As an aside, I recommend changing the skeletonJSON scale rather than the GameObject scale. As the json scale is applied at load time and Transform scale is applied every frame. I guess since its effect on performance is also miniscule, it's a matter of taste.

Xelnath

Adjusting the JSON scale in unity seems to have no effect in-game.

Wait, wait, I forgot to hit "reload"

12 Jun 2016, 18:42

Things get stranger.

The underlying skeleton and game object positioning is different than the rendered final.

Check out this out. The blue "Missile Release Point" is supposed to be at the "tip" of the gun.

However, its positioning the base objects in a different place (the Layer 0 pose)...

12 Jun 2016, 19:56

Just picked up your editor inspector update, thank you, Pharan!

Did you mess up the case for boneMesh and BoneMesh?

Pharan

Nah, those were renamed in a previous PR. Haven't updated the unitypackage yet.

Xelnath

Here's what the skeleton looks like:

It appears to "reset" after the non-looping animation blends into the looping one.

I was able to reduce the frequency of the UV texture mess-up by using Layers in sequential order ( 0, 1, 2) instead of arbitrary ( 0, 2, 5)

Pharan

Are you using any extra stuff to render? The SkeletonRenderSeparator maybe?

Xelnath

Let me look. I might be using SkeletonGhost somewhere.

13 Jun 2016, 11:24

http://imgur.com/VWQcEYZ

The image size limit is brutal on this forum. 2 megs is not much for a gif.

27 Jun 2016, 20:40

This issue was mostly resolved by changing the "Track" IDs to be sequential, rather than semi-random.

Pharan

The issue kinda stumped me. Getting a bit sidetracked with the 3.3 update at the moment.
I don't think tracks should affect the integrity of rendering at all.

Xelnath

3.3.07 update is pretty important!

The issue went away once I changed all of my track IDs to be sequential instead of spread out:

Before ( 0, 3, 5)
After ( 0, 1, 2 )