I have a simple cube character that’s been animated in blender and exported to a glb. I’m unable to preview the animations in the inspector. If I download to a glb viewer I can see the animations play. Is there a trick to getting animations to preview? I’m following the docs but no luck yet.
Hi @noah_mizrahi !
I’m looking at your project, and it seems like the animations are playing in the inspector as expected:
Could you give a bit of information on your system, or clarify if I’ve misunderstood what the issue is?
I was able to produce this by clicking on one of the animation clips in the asset panel:
I hope this is helpful.
2 Likes
Thanks for your reply!
I can see the timeline looping but there is no model showing up in my system like yours does. It’s possible I don’t understand how to load the preview with a model. I am only clicking on the animation inside the glb. do I need to do something to make the model show up?
My chrome version: Version 142.0.7444.176 (Official Build) (64-bit)
can you check the console in your Chrome dev console please, to see if some errors are reported.
thanks for the reply! Yes there is a anim view error in the console.
editor.ts:136 PlayCanvas Editor API v0.0.0 revision unknown
messenger.ts:104 messenger connected
relay-server.ts:112 relay server connected
realtime.ts:16 realtime connected
anim-viewer.ts:602 Animation preview cannot render as input data is not a multiple of 4
render @ anim-viewer.ts:602
It might be related to the size of the preview window, but not sure.
But with the way @will is attacking Editor bugs lately, this might get fixed in the near future!
Here is a similar issue:
Curious if there are any work arounds that people know of. I’ve tried other browsers and it’s the same. It’s a major slow down for production not being able to preview.
Curious what browser you are using that allows you to preview.
I think it has something to do with device. I work on an Apple Mac and it works, but it doesn’t work on the Chromebook I use. May be a screen size issue, but I’m not the expert.
The fix for this was just deployed in Editor v2.11.0:
1 Like