With 5.2 on the horizon, do you think the issue will be resolved by the time it is released?
Hello.
Thank you for your reply and for providing a solution.
I would also like to report another issue. Every time I import an FBX using Pipeline, a red error message appears at the bottom of the screen. It does not seem to be a serious problem because the āAll Doneā message appears immediately afterward and the import process completes successfully.
Uploading: Issue Pipeline 02.jpgā¦
I have also encountered a similar issue with a particular character FBX. The same red error message appears first, followed by another message showing additional errors. Despite these warnings, the character appears to function correctly and I can work with it without any noticeable problems.
However, I am concerned that these errors could become more problematic with future Blender releases and potentially affect the addonās functionality. I hope you can identify the cause of these messages and provide a solution.
Best regards.
Given it took the Blender devs over 2 years to push this change through, I am not expecting a quick fix.
However, it may be the case that there is nothing to fix.
Iāve been reading through the history of the commit for this change and one comment stands out:
- Another thing to consider is that this will remain an asymmetrical feature for the foreseeable future,
as Blender has no support for custom normals on shapekeys currently.
In other words, custom normals have never worked when the mesh has shape keys. So maybe removing the custom normals is the right thing to do?
Any traceback errors like this are a serious problem. They mean it crashed unexpectedly and didnāt finish what it was doing.
But that particular error, on itās own it doesnāt make much sense, unless something caused another error before that.
What are the exact steps to reproduce this error:
- How did you export the character.
- What steps did you take to import the character into Blender.
Hi! I found the issue, and it turns out it wasnāt a problem with the add-on after all.
I realized that I had accidentally saved a custom startup file (āSave Startup Fileā) in Blender with one of my characters already loaded in the background. Because of this, every time I opened Blender and tried to import a new character, it caused a conflict with the existing one and triggered the error. In fact, when I tried to import that same character that was already loaded, it would trigger even more errors.
I have now loaded the factory settings to have a clean startup scene, and the importer works perfectly. Sorry for the confusion, and thank you for your time!