Releases: rintrint/mmdbridge
Releases · rintrint/mmdbridge
v1.3.0
v1.2.4
v1.2.3
v1.2.2
v1.2.1
- alembic: Fix UE5 crash when using export mode 1
- alembic: Fix export mode 1 & 2 not setting material slots correctly
- alembic: Show error message if failed to write abc file
- alembic: Add description for export mode 3
- alembic: Use .data() instead of .front() to avoid undefined behavior on empty vectors
v1.2.0
v1.1.2
v1.1.1
v1.1.0
- MMDBridge can now correctly export at high FPS such as 60 or 120. The AVI export FPS does not need to match MMDBridge’s FPS setting, allowing you to bake high-FPS exports into lower-FPS data.
- MMDBridge can now fix more garbled text in MMD on non-Japanese Windows systems.
- Improved VMD export performance.
- The VMD export summary message now shows the elapsed time.
- Message boxes now appear in the foreground.
- Fixed Alembic re-exports accumulating meshes from previous exports.
- Tweaked the plugin settings panel.
- Improved hook stability.
- Other bug fixes and robustness improvements.
v1.0.1
v1.0.1 - VMD Export Bone Name Validation
This is a patch release that focuses on improving the stability of VMD exports and enhancing the overall code quality.
🔧 Fixes & Improvements
- Added Bone Name Validation for VMD Export: The exporter now checks for invalid bone names (e.g., non-CP932 compliant, or exceeding 15 bytes) before exporting. If an issue is found, a user-friendly error message is displayed to guide the user in fixing the model data. This prevents the creation of corrupted or unusable
.vmdfiles.
⚙️ Other Changes
- Code Refactoring: Implemented significant code refactoring across the application to improve maintainability, stability, and structure. This includes simplifying internal hooks and enforcing UTF-16LE for configuration files.
- Documentation: The project documentation has been improved and restructured for better clarity.