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

SkeletonAnimation flashing and disappear when SetResolution

zeuxgame

As the title says

We have met a problem
that some Spine SkeletonDataAsset assign to skeletonAnimation
keep flashing(it's like 1 frame alpha 0, next frame alpha 1, and repeat)
after the program been build(in editor does not happend)

another problem is when we call SetResolution to full screen or to window
the skeletonAnimation object just been invisible

the objects tested above are using Spine runtime's skeletonAnimation by GameObject > Create
and they do not adding any other script to it

two of those problems can call Initialize(true) in skeletonAnimation to fix it
but this is expensive and not right

we need a better and correct solution for fix it
so please help

we have tested lot of files
most of them have this problem
and they all are expored by same version of Spine Editor(3.2)

Our Unity is 5.4
Spine runtime is 3.2

if you are curious why we don't upgrade to 3.5
that's because to do that we have to reexport all 2xx spine project
so we are keep using 3.2

thanks

Pharan

I tried doing this with Spine-Unity 3.2 and Unity 5.4.
I used this script:

using UnityEngine;

public class SetResolutionScript : MonoBehaviour {

   public KeyCode changeResolutionKey = KeyCode.Space;

   void Update () {
      if (Input.GetKeyDown(changeResolutionKey)) {
         bool nextIsFull = !Screen.fullScreen;
         Vector2 res = nextIsFull ? new Vector2(1920, 1080) : new Vector2(1280, 720);
         Screen.SetResolution((int)res.x, (int)res.y, nextIsFull);
      }
   }
}

Built for Windows standalone. Ran it. Pressed spacebar a few times. It changed resolution and switched between full screen and windowed.
Nothing wrong happened. Nothing became invisible.

I don't think there's anything in the Spine runtime code that would prevent it from rendering. It's just a MeshRenderer with a dynamic mesh.

zeuxgame

I found it
We change support graphic API
from dxd3d9 to dxd3d11
then this problem doesn't happend anymore
because most PC has 11
so checking auto Graphic API will using 11
and this problem will not easy to see