Let the legacy plugins co-exist with the 9.0.0 #31
Labels
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
kkbp-dev/KKBP_Importer#31
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Just wondering, could we have ability to install both versions KKBP_Exporter_4.35 and KKBP_Exporter_5.0 at the same time to export? I have some customized import features that will work with old-texture processing that happened in blender, so I somehow what to keep the legacy exporter there. But I think the export panel will overlay in game, is there a way to let them co-exist so that I can run both exporting method?
The new exporter still exports all texture-related files that were produced by the legacy exporter.
@Sonogami_Rinne wrote in #31 (comment):
I appreciate your response, but this isn’t only about the textures. There are several pain points, such as Blender 5.0 stopping backport support for older versions. In addition, I have some customized shaders that assemble textures from different masks inside Blender for another purpose, a modified armature based on the old KKBP armature to fix knees, shoulders, and other parts, as well as compatibility with the Goo Engine.
Before Importer 9.0.0, I installed two older versions of the exporter and they worked perfectly because the panels were displayed in different areas. Although this that might be related, I’m wondering whether it would be possible to add a checkbox that allows users to choose between different exporting methods.
After PR kkbp-dev/KKBP_Exporter#2, the files exported by the exporter are largely the same as those from version 4.35.
Aside from a few additional new files, the blendshape (shape key) offset fixes, and exportWithPushup being enabled by default, there are no major changes, including the armature. That PR removed the armature modifications, so the exported armature should now match what the older exporter produced.
In theory, the legacy importer should work well with files exported after that PR.
Note: That PR has just been merged and is not part of an official release yet.