Description:
When exporting a GLB file with the "Apply Modifiers" option checked in the Capsule 1.4.1 plugin for Blender 4.0.2, the "Data Transfer" modifier is not applied to the meshes in the exported file. However, other modifiers like "Decimate" are applied correctly.
I have attempted to resolve this issue by modifying the plugin's dependency collection code in dependencies.pyto include the "DATA_TRANSFER" modifier, but this did not solve the problem. It appears that the issue may be in the actual modifier application step during export, rather than just in dependency collection.
Steps to Reproduce:
Create a mesh object in Blender 4.0.2.
Add a "Data Transfer" modifier to the object, configure it with a source object and any data transfer settings (e.g., vertex groups, normals).
Select the object and export as GLB using the Capsule 1.4.1 plugin, ensuring the "Apply Modifiers" option is enabled in the export settings.
Import the exported GLB file into another application or back into Blender.
Observe that the mesh does not reflect the data transferred by the modifier.
Expected Behavior:
The "Data Transfer" modifier should be applied during export, resulting in a GLB file containing the mesh with the transferred data.
Actual Behavior:
The "Data Transfer" modifier is ignored, and the exported mesh remains unchanged by this modifier.
Environment:
Blender Version: 4.0.2
Plugin Version: Capsule 1.4.1
Operating System: Windows 11
Additional Information:
I noticed that the SearchModifiersfunction in dependencies.pyinitially did not include "DATA_TRANSFER" in the mod_typesset. I added it and implemented a branch to handle the source_objectproperty of the "DATA_TRANSFER" modifier, but this did not resolve the issue. This suggests that the problem may lie elsewhere, likely in the code responsible for actually applying modifiers during the export process.
I have also checked the plugin settings for any options that might skip non-deformative modifiers, but found none. The "Decimate" modifier works fine, indicating that the issue is specific to certain modifier types.
Possible Cause:
There may be a filter in the export code that excludes certain modifier types from being applied. The "Data Transfer" modifier might be inadvertently or intentionally excluded from this process. Could you please check if such a filter exists and if "DATA_TRANSFER" is on the exclusion list?
Request:
Could you investigate and provide a fix or workaround for this issue? Alternatively, if there is a known limitation, please advise on how to properly export meshes with the "Data Transfer" modifier applied.
Thank you for your time and for developing this useful plugin.
Description:
When exporting a GLB file with the "Apply Modifiers" option checked in the Capsule 1.4.1 plugin for Blender 4.0.2, the "Data Transfer" modifier is not applied to the meshes in the exported file. However, other modifiers like "Decimate" are applied correctly.
I have attempted to resolve this issue by modifying the plugin's dependency collection code in dependencies.pyto include the "DATA_TRANSFER" modifier, but this did not solve the problem. It appears that the issue may be in the actual modifier application step during export, rather than just in dependency collection.
Steps to Reproduce:
Create a mesh object in Blender 4.0.2.
Add a "Data Transfer" modifier to the object, configure it with a source object and any data transfer settings (e.g., vertex groups, normals).
Select the object and export as GLB using the Capsule 1.4.1 plugin, ensuring the "Apply Modifiers" option is enabled in the export settings.
Import the exported GLB file into another application or back into Blender.
Observe that the mesh does not reflect the data transferred by the modifier.
Expected Behavior:
The "Data Transfer" modifier should be applied during export, resulting in a GLB file containing the mesh with the transferred data.
Actual Behavior:
The "Data Transfer" modifier is ignored, and the exported mesh remains unchanged by this modifier.
Environment:
Blender Version: 4.0.2
Plugin Version: Capsule 1.4.1
Operating System: Windows 11
Additional Information:
I noticed that the SearchModifiersfunction in dependencies.pyinitially did not include "DATA_TRANSFER" in the mod_typesset. I added it and implemented a branch to handle the source_objectproperty of the "DATA_TRANSFER" modifier, but this did not resolve the issue. This suggests that the problem may lie elsewhere, likely in the code responsible for actually applying modifiers during the export process.
I have also checked the plugin settings for any options that might skip non-deformative modifiers, but found none. The "Decimate" modifier works fine, indicating that the issue is specific to certain modifier types.
Possible Cause:
There may be a filter in the export code that excludes certain modifier types from being applied. The "Data Transfer" modifier might be inadvertently or intentionally excluded from this process. Could you please check if such a filter exists and if "DATA_TRANSFER" is on the exclusion list?
Request:
Could you investigate and provide a fix or workaround for this issue? Alternatively, if there is a known limitation, please advise on how to properly export meshes with the "Data Transfer" modifier applied.
Thank you for your time and for developing this useful plugin.