Version: 1.7.27.0
Frequency: Consistently
Severity: High
Marketplace package name:
Context: Export via new Blender export plugin version 6.4.9 from Blender 4.2.2 LTS
Bug description:
If for a material the “Normal Texture” slot is left empty, but “Detail Normal Texture” is being used, the same Normal texture is being a used as “Normal Texture” too, but without the Detail Scale operator.
This can be circumvented by adding a dummy normal texture to the “Normal Texture” slot, but ofc for big projects this can’t be the solution.
Without a normal texture in the material, but one in Detail Normal:
With the dummy texture:
Repro steps: See screenshots
Attachments:
Private attachments: Send a PM to @PrivateContent with the link to this topic and the link to download your content
Hello @ACCAkut87
We were not able to replicate the issue.
Could you please share the .blend file that shows this issue with us?
For instructions on how to send content to the support team privately, please read section 3 in these guidelines:
How to report a bug or crash - [MSFS 2024] Bug Reports - MSFS DevSupport
Regards,
Sylvain
files send to PrivateContent
1 Like
Hello @ACCAkut87
You seem to have unchecked the Export In Background option from the Multi Exporter general settings:
This can cause side effects and should always remain checked.
Please check it and let us know if this solves your problem.
Regards,
Sylvain
Clicking that did, apparently, actually fix the bug, my question would be why this checkbox has such a big influence on the export process 
I conversed with a couple other hobby devs, and they said “Export in background makes a temp copy of your blend file and then runs the export code in a separate process. So you can continue to modify your model, if you choose.” - which is probably sensible for huge projects, but for small scenes with a handful assets like my lighthouse there, exporting without it is much faster and less stressing for the system.
I did test the same material setup on a test asset made in a fresh .blend file, and the bug did not occur, so I assume it must be something about materials created under older versions of the plugin.
“Export In Background” works on a full copy of the scene and any preps for export done on that scene have no consequences as it’s discarded once the export is done.
When disabled, the process works on the real scene, duplicating assets and doing operations that might affect the scene. This is a bit less reliable.
We will likely lock or remove this option altogether to avoid any confusion.
Regards,
Sylvain
1 Like
