I have run into some huge issues with how Blender 3.3 and 3.4 now manage Key Frames when working on glTF-2 related projects. Also, when bringing in some of my projects from Blender 3.2 to 3.3 and 3.4, there are new issues with the Key Frames.
This never happened before and make it very difficult on exporting to game platforms. Could there ‘possibly’ be a bug in how glTF-2 files and animations management are now handled in Blender 3.3/3.4?
I used to be able to import an glTF-2 file, animated and mapped, into earlier versions of Blender fine. Key Frames (0-100, or 0-50, etc) always imported properly.
Now, when I import a model scene to Blender 3.3 or 3.4, a 0-100 key frame range is now 0-2400 or so. Radically high. I was told by Blender Development that glTF’s are imported per Frame megaherz or timing, frames per second. Not key frames.
This is a radical change… Is this a good direction? This really messes things up when importing and exporting glTF-2 files and scenes.
If only there were a switch that one could flip that would revert glTF-2 Animations management back to Key Frames instead of Frames per second. This didnt exist before. I had never had issues like this before 3.3 and 3.4. And 3.2 earlier versions never had this.
This is a voice of my opinion and a concern on projects in the field of animations and exporting for game platforms. I know that Blender are trying to create the best product possible, but have we gone into a direction that possibly has some issues? A buggy route? My humble input…