2024 Blender tool exporting grey scale ORM

kcgb · October 26, 2024, 11:26am

Version:

Dev Alpha

Frequency:

Consistently

Severity:

High

Context:

When using Blender to export textures, with blender 3.6LTS

Bug description:
When exporting a model from Blender using the 2024 SDK tool, the ORM map gets exported as a greyscale texture instead of the original. This obviously causes it to not work. Can be worked around by replacing with the original texture after export

Repro steps:

Export a material with ORM map from current version of blender tools from blender 3.6LTS
Attachments:

SLH · October 26, 2024, 4:30pm

Can confirm. Huge Issue

DA40CGDFQ · October 26, 2024, 6:07pm

For my own understanding are you saying the Blender exporter modifies the texture? It should only copy it to the packagesources folder (or where ever you specify)

EDIT:

WOW!!!

will you look at that

DA40CGDFQ · October 27, 2024, 1:55pm

Could someone else test my theory that this is a Blender 3.6 (possible 3.3) issue and not an issue in 4.2

github.com/KhronosGroup/glTF-Blender-IO

Exporting textures - 3.6 changes the texture while 4.2 does not

opened 01:53PM - 27 Oct 24 UTC

ronh991

**Describe the bug** Having a texture node going to a separate RGB node and the…n to roughness and metallic in BSDF. Exporting this as a gltf and having the texture also exported. In Blender 3.6.5 3.6.10 and 3.6.16 and 3.6.17 (Also in 3.3 I think but 3.3 no longer LTS) the texture gets changed to all white, while I do the same in 4.2 and works as expected. **To Reproduce** Steps to reproduce the behavior: 1. set up texture node to separate node to BSDF with channels going to roughness and metallic - set the texture node to non-color 2. export as glTF - with texture folder ../texture ( do not overwrite same folder) 3. compare the source texture to the texture saved in the ../texture folder 4. See difference **Expected behavior** The texture should NOT be modified. **Screenshots** If applicable, add screenshots to help explain your problem. texture from source in both scenarios **.blend file/ .glTF (mandatory)** [test_omr_compissue_2.zip](https://github.com/user-attachments/files/17534139/test_omr_compissue_2.zip) ![DA40CGDFQ_2024 10 27_9h45m59s](https://github.com/user-attachments/assets/6e89a004-bbaa-4d23-9075-907fd559b38b) 3.6 export texture is test_comp.png ![DA40CGDFQ_2024 10 27_9h46m39s](https://github.com/user-attachments/assets/311309d5-2c3e-465c-a86b-bb7161af6e65) 4.2 export ![DA40CGDFQ_2024 10 27_9h47m5s](https://github.com/user-attachments/assets/918603a1-3109-4367-b254-e221b75db1e8) 3.6 shader nodes ![DA40CGDFQ_2024 10 27_9h52m5s](https://github.com/user-attachments/assets/f8e9de3e-4fd9-4eab-a20f-79877cb3d263) 4.2 shader nodes ![DA40CGDFQ_2024 10 27_9h51m18s](https://github.com/user-attachments/assets/193a4d46-f899-484f-84d1-10fdc45230a8) **Version** - OS: windows 10 - Blender Version 3.6.5, 3.6.10, 3.6.16, 3.6.17 not working 4.2.3 working **Additional context** Add any other context about the problem here.

I have reported this to Khronos - when I export without MSFS exporter enabled. This still happens.

SLH · October 28, 2024, 4:07am

I’m not exactly what you’re asking us to test, what i do know is the old Fs20 plug-in didn’t do it, but this one does doesn’t matter whether blender 3.6 or 3.3, so i thinks it’s an asobo plug-in issue. I don’t use blender 4.x.

DA40CGDFQ · October 28, 2024, 1:43pm

I tested this by disabling the msfs 2024 plugin and 2020 plugin. This seems to be a Khronos issue or blender issue. So I am asking some one else to disable the ASOBO plugin and just export a cube with a comp texture in a group node.

Skylizard8760 · October 28, 2024, 2:26pm

I also see this issue, for now, it’s fine to just manually copy the texture png afterwards. Though you must disable live reloading for this to work correctly if exporting with the sim running.

Yasmine · November 6, 2024, 4:11pm

Hello,

This has been fixed in SDK SDK Core 2024 0.9.2. We now copy/paste the texture used in the gltf in the given relative folder.

Thank you