Update blender_3dmigoto_gimi.py to allow multiple objects per classification

[Arsinia]

commit 3690cc9 (HEAD -> blender-plugin-merge-meshes, origin/blender-plugin-merge-meshes)
Author: Arsinia arsiniamods@gmail.com
Date: Fri Jan 3 02:52:48 2025 -0800

Update blender_3dmigoto_gimi.py to put new files behind options

*  Add options to gate writing the export indices file and copying ib files behind an option that's defaulted to false

commit 8159e47
Author: Arsinia arsiniamods@gmail.com
Date: Fri Jan 3 02:14:16 2025 -0800

Update blender_3dmigoto_gimi.py to allow multiple objects per classification

Feature details:
*  Now allows for multiple objects per classification that will be merged on export
   *  For example, you can have a NoelleDress_Waist and NoelleDress_Shirt that will be merged automatically instead of needing to merge meshes before export
*  Modifiers and shape keys are applied during export, and non-numeric vertex groups are removed
*  Exports a new file with the face and vertex indices of each part within a classification.
   *  This allows mods to know which indices correspond to which part and edit the ib to show/hide parts of the mesh
*  Exports the ib files to a new folder "BaseFiles" so mods that modify ib have the original ib to reference and revert to
*  Fixed a minor bug where the classification would be incorrect if any classification has an empty relevant object
   *  Before the code "relevant_objects = [x for x in relevant_objects if x]" would remove empty relevant objects, but this would change the indices which are used to get the classifications
   *  Now it early outs without error if the relevant objects is empty instead of removing the empty objects first

Implementation details:
*  Instead of reading directly from the mesh of the objects exported, we make a copy of each mesh
   *  This may be more expensive, but it allows us to modify the mesh in export without messing with the original object
   *  This is what allows us to apply modifiers, remove shape keys, and merge meshes in export instead of requiring the user to do that manually per export
*  Triangulation now occurs on the object after being duplicated instead of ojn the mesh directly.
   *  This is required for the export indices to be correct, but otherwise it should work the same as before

[leotorrez]

We currently use a plugin called XXMI plugin that nucleates GIMI, SRMI and ZZMI modding tools in a single one. This already includes several of the functions this commit offers with some minor differences

Implementation details:

• Instead of reading directly from the mesh of the objects exported, we make a copy of each mesh
  • This may be more expensive, but it allows us to modify the mesh in export without messing with the original object
  • This is what allows us to apply modifiers, remove shape keys, and merge meshes in export instead of requiring the user to do that manually per export

Blender has a fast implementation of this that we also use. Allows you to have data only copies of the mesh to operate on and read from. It also already has all modifiers and shapekeys applied to it saving a lot of export time on that "desgraph copy" I believe is the name of these.

[Arsinia]

Currently working on adapting relevant features from this to XXMI

[leotorrez]

Before diving into extensive coding feel free to DM me in discord at leotorrez or tag me in the discord.gg/agmg. We can discuss on your ideas and what might or might not be ideal for the plugin. We have been working on some features that might overlap or achieve the same end