How poly-hammer/blendertools works
• “Send to Unreal” – a one‐click solution for sending assets from Blender to Unreal Engine.
• “UE to Rigify” – a node‑based retargeting system that facilitates working with Blender’s Rigify addon to adapt and animate assets from Unreal Engine.
Main Components
• Blender Addon Modules: There are two distinct modules (send2ue and ue2rigify) nested under the “src/addons/” directory. Each module contains several subcomponents:
– Core Functionality: Found in directories like “core” (export, ingest, nodes, scene, templates, utilities, etc.).
– Dependencies & RPC Communication: Both addons include “dependencies” directories that manage remote execution between Blender and Unreal. For example, they implement RPC clients, servers, and exception handling.
– UI Components: Modules have “ui” subdirectories for Blender integration (dialogs, panels, file browsers, header menus, etc.).
– Settings & Properties: Manage addon configuration and user preferences.
– Resources & Templates: Located in “resources” and “setting_templates” folders, which store default configurations, rig templates, and extension code.
• Documentation & Tests:
– The “docs” directory holds extensive user and technical documentation for development, testing, and integration.
– The “tests” folder contains unit tests and sample files to ensure correct behavior across Blender and Unreal integrations.
• Supporting Infrastructure:
– Scripts in the “scripts” folder for addon watching, packaging, and release automation.
– Configuration files like .env.example, mkdocs.yml, and CI/CD workflows under “.github/workflows” that emphasize automated testing and documentation building.
Relationships and Interactions
• Within Blender: The addons integrate directly with Blender’s API (operators, properties, UI panels) to provide one-click asset export/import and node-based retargeting of animations.
• RPC Communication: The “dependencies/rpc” modules in both addons encapsulate client–server relationships for remote execution, handling operations such as sending FBX data and communicating with Unreal Engine.
Architectural Patterns and Design Principles
• Modularity: Clear separation between the two addons and between components within each addon (core, UI, dependencies, settings, and resources).
• Separation of Concerns: For example, UI concerns are handled in the “ui” directories, while processing and export logic is encapsulated in “core” and “io” modules.
• Extensibility: The “extensions” and “resources/extensions” directories are designed to allow additional functionality without altering the core code.
• Testing & Continuous Integration: Presence of CI workflows and comprehensive tests indicates an architecture that values reliability and maintainability.
Final Advice for the Principal Software Engineer
• Be precise in indicating external communication points (e.g., RPC servers/clients) and emphasize the modular separation that allows for extensibility.
• Annotations if necessary to explain key interactions—for example, the remote execution pattern used between Blender and Unreal.