Let the legacy plugins co-exist with the 9.0.0 #31

Open
opened 2026-02-06 06:24:06 +00:00 by C1011 · 3 comments

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?

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?
Contributor

The new exporter still exports all texture-related files that were produced by the legacy exporter.

The new exporter still exports all texture-related files that were produced by the legacy exporter.
Author

@Sonogami_Rinne wrote in #31 (comment):

The new exporter still exports all texture-related files that were produced by the legacy exporter.

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.

@Sonogami_Rinne wrote in https://gitgoon.dev/kkbp-dev/KKBP_Importer/issues/31#issuecomment-4847: > The new exporter still exports all texture-related files that were produced by the legacy exporter. 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.
Contributor

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.

After PR https://gitgoon.dev/kkbp-dev/KKBP_Exporter/pulls/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.
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
kkbp-dev/KKBP_Importer#31
No description provided.