Animating in Stride

[eemmanu]

Hi I am new in Stride but animation feels hard for me . Does anyone have any idea how animations can be made easier

[mihai-ene-public]

You can start here: https://doc.stride3d.net/latest/en/manual/animation/index.html

[Asatte32]

You can use this Blender extension to separate the animations and export them for Stride: https://github.com/JackPilley/BlenderToStrideAnimationSeparator

[Asatte32]

Here is the version I am using. The original version did not work due to the model I am using lacking some properties I guess? Copy the whole thing, pasting the code triggers code start and end resulting with this:

bl_info = {
"name": "FBX Animation Splitter (Stride)",
"author": "Stride / Blender fixed",
"version": (1, 0, 0),
"blender": (4, 0, 0),
"location": "File > Export",
"description": "Export each action as a separate FBX animation",
"category": "Import-Export",
}

import bpy
import os

def sanitize_filename(name):
invalid_chars = '<>:"/\|?*'
for ch in invalid_chars:
name = name.replace(ch, '_')
return name.strip()

def get_armature():
for obj in bpy.context.scene.objects:
if obj.type == 'ARMATURE':
return obj
return None

def main(context):
armature = get_armature()
if armature is None:
raise RuntimeError("No armature found in scene")

if armature.animation_data is None:
    armature.animation_data_create()

# Save original action
original_action = armature.animation_data.action

blend_path = bpy.data.filepath
if not blend_path:
    raise RuntimeError("Please save the .blend file first")

directory = os.path.dirname(blend_path)
base_name = os.path.splitext(os.path.basename(blend_path))[0]

exported = 0

for action in bpy.data.actions:
    # Skip empty actions
    if not action.fcurves:
        continue

    safe_name = sanitize_filename(action.name)

    print(f"Exporting: {safe_name}")

    armature.animation_data.action = action
    context.scene.frame_start = int(action.frame_range[0])
    context.scene.frame_end = int(action.frame_range[1])

    fbx_path = os.path.join(
        directory,
        f"{base_name}_{safe_name}.fbx"
    )

    bpy.ops.export_scene.fbx(
        filepath=fbx_path,
        use_selection=False,
        object_types={'ARMATURE', 'MESH'},
        bake_anim=True,
        bake_anim_use_all_actions=False,
        bake_anim_use_nla_strips=False,
        bake_anim_force_startend_keying=True,
        add_leaf_bones=False,
        use_armature_deform_only=True,
        path_mode='AUTO'
    )

    exported += 1

# Restore original action
armature.animation_data.action = original_action

print(f"Exported {exported} animations")

class SplitAnimations(bpy.types.Operator):
bl_idname = "export.split_stride_animations"
bl_label = "Export Animations for Stride"
bl_options = {'REGISTER', 'UNDO'}

def execute(self, context):
    main(context)
    self.report({'INFO'}, "Animation export finished")
    return {'FINISHED'}

def menu_func(self, context):
self.layout.operator(SplitAnimations.bl_idname, text="Stride: Export Animations")

def register():
bpy.utils.register_class(SplitAnimations)
bpy.types.TOPBAR_MT_file_export.append(menu_func)

def unregister():
bpy.utils.unregister_class(SplitAnimations)
bpy.types.TOPBAR_MT_file_export.remove(menu_func)

if name == "main":
register()

[MsEpsilon]

Given my own personal experience, this is not necessary anymore. This was actually fixed.

[MsEpsilon]

I use Blender for animation, export as FBX. Depending on the Stride version, if pre 4.2.0 you'll may a single entire animation then split it up inside Stride.