- Modifié
设置defaultMix后动画异常好晃动
压缩包里是动画加载视频，可以看到视频中有一条白色的斜线在晃动,但是设置defaultMix = 0的时候是没有这种问题的。
设置的地方在 SkeletonAnimation.m中
- (void) initialize {
_ownsAnimationStateData = true;
timeScale = 1;
spAnimationStateData datas = spAnimationStateData_create(skeleton->data);
datas->defaultMix = 0.3;
_state = spAnimationState_create(datas);
_state->rendererObject = self;
_state->listener = animationCallback;
spAnimationState stateInternal = (spAnimationState*)_state;
}
资源包和demo已经通过QQ邮箱907689522，发送到你们的邮箱
这样的问题如何处理，期待您的回复谢谢。
There is an animation loading video in the compressed package. You can see that a white diagonal line is shaking in the video, but there is no such problem when defaultMix=0 is set.
The place set is in SkeletonAnimation. m
- (void) initialize {
_ ownsAnimationStateData = true;
_ timeScale = 1;
spAnimationStateData datas = spAnimationStateData_ create(skeleton->data);
datas->defaultMix = 0.3;
_ state = spAnimationState create(datas);
_ state->rendererObject = self;
_ state->listener = animationCallback;
_ spAnimationState stateInternal = (spAnimationState*) state;
}
The resource package and demo have been sent to your mailbox through QQ mailbox 907,689,522
How to deal with such problems? We look forward to your reply. Thank you
我可以重现这个问题。 您不需要修改 SkeletonAnimation.m，您可以在 IkExample.m 中进行此操作：
self.skeletonNode.state->data->defaultMix = 0.3f;
您所看到的称为“浸渍”。 仅使用导出的 .json/.atlas 文件很难诊断。 请通过电子邮件将 Spine 项目发送给我。
I can reproduce the issue. You don't need to modify SkeletonAnimation.m, you can do this in IkExample.m:
self.skeletonNode.state->data->defaultMix = 0.3f;
What you see is called "dipping". It's hard to diagnose with just the exported .json/.atlas files. Please send me the Spine project via email.
The resource package and demo have been sent to your mailbox through QQ mailbox 907,689,522
We look forward to your reply. Thank you
I'm sorry, the files you send to not include the .spine file and images. Please send me these files, not the exported .json and .atlas files.
The resource package and demo have been sent to your mailbox through QQ mailbox 907,689,522
We look forward to your reply. Thank you
Thank you, I was able to reproduce the issue. Sadly, it is not something we can fix in the very old 4.0 branch. Is there a way for you to upgrade the Spine Runtimes to 4.1? I have confirmed that your skeleton is working as intended there. You'll have to also re-export your assets for 4.1.
Can we fix this problem on 4.0? Because we have web, applet and Android in use and hundreds of resource packages. In this way, all ends need to be upgraded. It takes time, effort and error prone. After upgrading, multiple ends need to be retested. I strongly hope that this problem can be fixed on 4.0. Thank you very much
Or you can tell me how to avoid this problem and achieve the same animation effect during the production or export of spine. Because there is a problem with this animation loading at present.
I have backported fixes from the 4.1 branch to 4.0 for spine-c. I have also fixed an issue in spine-cocos2d-objc which is responsible for the flashes. I have used your reproduction project to confirm the fixes work. Please update your spine-cocos2d-objc copy from the 4.0 branch (including spine-c!) and confirm the fixes on your end.
Hello, after I downloaded the latest test, I found that the problem of flicker raised previously has been solved, but the problem of flicker raised in this forum has not been solved, and I look forward to your reply Thank you
The test also found that the problem was not found in 4.1, but only in 4.0. However, due to our version compatibility problems and too many resources, and the high cost of upgrading 4.1, it is easy to make mistakes. I hope that we can update the secondary repair to 4.0. Thank you very much
I'm sorry, it's hard to keep track of the issues you posted. Can you please link me to the flicker issue that is still not resolved in 4.0?
The flickering problem has been solved, but my post says that another problem is not flickering. You can see your reply three days ago. thank you
You replied to the other problem handling results I submitted below this post