Studio Library for Blender 5.2 LTS has been updated to v03 with several improvements to the export workflow. In this update: Improved the export path system for better file organization. Exported animation files are now properly integrated with their thumbnails. The UI selection automatically updates to the newly exported file, making it easier to continue working with your latest animation. This update focuses on improving the workflow and making animation library management more seamless and intuitive.

We’re happy to announce that Studio Library Animation for Blender 5.2 LTS has officially been released! Starting with Blender 5.x, the Individual Blender 4 and Blender 5 versions are now sold as separate variants. This is because Blender 5 introduced major API changes that require specific development and adjustments, and we are also following the sales guidelines recommended by SuperHive. For existing users: Individual Blender 4 → You will need to purchase the Blender 5 variant to use Studio Library with Blender 5.2 LTS. Individual Blender 5 → Includes the Blender 5 version. Studio Seat → Automatically includes both variants, Blender 4 and Blender 5. Thank you for your continued support and trust in Raha Tools / Studio Library. ❤️

Update Note – April 22, 2025 This update addresses a critical bug related to the reading and saving of custom properties. In certain rigs, this issue caused animation data to be unreadable or corrupted, which could severely impact usability. However, I’ve decided to keep both versions available: Studio-Library-Blender-4++ (v01) Studio-Library-Blender-4_V02 You're free to use whichever version works best for you. If you find that v01 still feels more stable or familiar in your workflow, feel free to continue using it.

About the "Fix Your Keyframe" Feature When exporting animation, the system can only read the keyframe data correctly if all three transform axes (X, Y, Z) have keyframes. If only X and Z are keyed while Y is missing, the exporter will assume the Y value is zero, which can cause the animation to break or behave incorrectly. The "Fix Your Keyframe" option works by: Scanning all frames in your animation. Detecting any missing keyframes on individual axes. Automatically adding keyframes for the missing axes using the current values at those frames, ensuring X, Y, and Z are always fully keyed where necessary. Important Note: This is not a baking process. It does not bake your animation or add keyframes on every frame. Instead, it cleans up existing keyframes by filling in only the missing axes at frames that are already keyed. This keeps your animation data clean and lightweight, unlike baked animations which can be heavy and dense with keyframes. Why It Matters: While Blender usually inserts keyframes on all axes by default, during animation editing it's common for some axes to be unintentionally removed (e.g., only X and Z remain). This incomplete data can lead to errors or incorrect motion during export. Other Considerations: The cleanup process may slow down the export, especially on complex animations. If you're confident that your animation is already clean and all axes are keyed properly, you can leave this option unchecked for faster export. But if you're unsure, it's safer to enable this option to avoid broken exports. Extra Tip: One of the biggest factors affecting export speed is the number of bones being exported. Only selected bones will be included in the export, so: Exporting just 2 bones is much faster than exporting 50 bones. The more bones selected, the longer it will take to scan and export—especially when "Fix Your Keyframe" is enabled. Try it yourself: Export your animation with and without "Fix Your Keyframe" checked, and test with different bone counts to see how it impacts both export speed and results.

If you receive an "invalid path" message, try navigating to a path that contains images in D:/ or E:/ (or another path that has images). Once you can read that path, you can return to the correct path you want to go to. This issue should not occur anymore as the bug has been fixed