Skip to content

v0.6.5

Pre-release
Pre-release

Choose a tag to compare

View all tags
@3dvm 3dvm released this 07 Aug 22:10
· 58 commits to main since this release
v0.6.5
64901a5

Full Changelog: v0.5.5...v0.6.5

image

Release Notes - OpenStudioHub v0.6.5 (Unstable)

Welcome to version 0.6.5! This update marks a milestone in the development of OpenStudioHub. We have closed the main work cycle ("Golden Path"): from the inception of a project to the rendering of shots, including automatic quality control and local infrastructure management.

Although we are still polishing details and fixing bugs (it's Unstable after all!), the core engine of the application is now ready to boost your studio's productions.

##Main Features (For Artists and Managers)

The Gatekeeper: Your new best friend before Publishing (v0.5.0)
No more stress over sending broken files and endless manual reviews.

  • Auto-repair (Sanity Check): The Gatekeeper now silently audits and corrects dirty geometry, purges orphan data, and fixes unapplied scales.

  • "The Janitor": If you used a downloaded texture in your personal folder, the system detects it (Out-of-Bounds), alerts you, and automatically copies the files to the secure project folders on the studio's network.

  • The Synergy Hook: Upon passing the checks, the Hub automatically triggers Blender Studio Tools addon (Blender Kitsu) to generate and publish your playblast without friction.

Big Kitsu Integration: Batch Creation & Path Resolver (v0.6.3)
The Production Manager now has absolute control directly from the Hub interface.

  • Batch Spawning: The PM can read approved shots and assets in Kitsu and inject all their folders and master .blend files into the SVN repository at once with a single click.

  • Automatic Resolution: Zero human error when creating folders. The Hub translates Kitsu data into structured physical paths (e.g., shots/sq010/sh010) using its PathResolver engine.

New Artist Dashboard & Injected Environment (v0.5.5 - v0.5.7)

  • Visual Redesign: A much cleaner, elastic interface adapted to our corporate colors to list your active tasks.

  • Magic Pre-Flight: Upon hitting "Launch Project", the Hub now silently injects your credentials, project ID, and the studio's physical preferences directly into Blender's memory (RNA). Everything is ready for the Kitsu add-on to work without you configuring anything.

  • Contextual Workspaces: If you open a "Storyboard" or "Editorial" task, the Hub forces Blender to directly open that specific workspace to save you clicks.

Watchtower Integration (v0.6.5)

  • Visualize the entire production progress. Supervisors and PMs can now see a visual report of the rendered videos and playblasts by simply pressing the "Watchtower" button in the Hub, which spins up a temporary server without extra configurations.

Infrastructure and Backend (For the Tech Team / TD)

The magic behind the scenes that keeps the studio secure and standardized:

  • ProjectBuilder and B2B Vault (v0.6.0): The New Project Wizard now dynamically extracts templates and dependencies directly from the NAS. The engine builds the entire base topography of the project, makes the initial commit, and updates the SSoT.

  • Jailing / Sparse Checkout Engine (v0.4.0): Industrial-grade security for freelancers. The Hub reads *-meta.json manifests and executes a recursive algorithm to download exclusively the files and textures the artist needs, isolating the rest of the intellectual property.

  • Process Guardian and Version Control: The system now handles file locking (svn lock) upon opening them for editing and prohibits closing the Hub if it detects Blender is still running, avoiding repository corruption and preventing files from getting locked on the server.

  • ConfigFactory (v0.6.1-patch): A new visual panel for the TD to configure the Nextcloud path, SVN, and Cloud servers directly, saving changes bidirectionally in a secure master file (settings.json).

  • Migration to PySide6: Goodbye to 4K monitor rendering issues. We have migrated the graphical architecture to Qt to ensure full Thread-Safe support and a smooth experience.

Additional Notes and Known Bugs

  • We are aware that Kitsu validation might fail if there are discrepancies between the physical disk and the name in Gazu. An initial SSoT system has been implemented to mitigate this, but we suggest maintaining manual sync if projects are renamed.

Thank you for being part of this milestone! Your feedback is vital as we move towards version 1.0.0.

Assets 5
Loading