[2024] SDK 1.2.4 - Blender exporter 3.3.0 - MSFS2024_PT_ImageProperties for USERFLAGS - not shown or used in exporter code

[DA40CGDFQ]

Version: *1.3.23 - 8 GB update

Frequency: Consistently*

Severity: High
(Low - quality of life, workflow optimization, rare enough to not impact production, etc…
High - critical but workarounds are available, important feature not working as expected, frequent enough to impact production
Blocker - prevents from working on the project, prevents from releasing the product)

Marketplace package name: if applicable

Context: What package? When editing or mounted from Community? In main menu or in flight? etc…

Similar MSFS 2020 issue: insert url here if applicable

Bug description:

The MSFS2024_PT_ImageProperties code in the ASOBO exporter is not being shown or used in the exporter - This allows the developer to set texture.xml properties needed.

        row = box.row()
        row.prop(flags, MSFS2024ImageFlagsEnum.QUALITYHIGH.attribute_name())
        row = box.row()
        row.prop(flags, MSFS2024ImageFlagsEnum.ALPHAPRESERVATION.attribute_name())
        row = box.row()
        row.prop(flags, MSFS2024ImageFlagsEnum.NOREDUCTION.attribute_name())
        row = box.row()
        row.prop(flags, MSFS2024ImageFlagsEnum.NOMIPMAP.attribute_name())
        row = box.row()
        row.prop(flags, MSFS2024ImageFlagsEnum.PRECOMPUTEDINVAVG.attribute_name())
        row = box.row()
        row.prop(flags, MSFS2024ImageFlagsEnum.ANISOTROPIC.attribute_name())

in the DA62 sample the xml files contain more data that the Blender exporter allows - so Blender people need to look at every xml and manually modify it, plus accidental over writing is possible afterwards.

DA62 sample has for example:

<BitmapConfiguration>
	<BitmapSlot>MTL_BITMAP_DECAL0</BitmapSlot>
	<UserFlags Type="_DEFAULT">+QUALITYHIGH</UserFlags>
</BitmapConfiguration>

and

<BitmapConfiguration>
	<BitmapSlot>MTL_BITMAP_DECAL0</BitmapSlot>
	<UserFlags Type="_DEFAULT">+QUALITYHIGH+ALPHAPRESERVATION+NOREDUCTION+NOMIPMAPS</UserFlags></BitmapConfiguration>

Repro steps:

Attachments:

Private attachments: Send a PM to @PrivateContent with the link to this topic and the link to download your content

[Cygnifick]

No idea if this is an issue because I can’t check that atm but,

+NOMIPMAPS in
<UserFlags Type="_DEFAULT">+QUALITYHIGH+ALPHAPRESERVATION+NOREDUCTION+NOMIPMAPS</UserFlags>

and here

NOMIPMAP
MSFS2024ImageFlagsEnum.NOMIPMAP.attribute_name()```

[Yasmine]

Hello,

The flags are accessible from the image editor view in Blender here:

You will need to set them to get them exported in the xml pf the textures.

Thank you

[DA40CGDFQ]

Wow this is fantastic thank you. Now to test LOL

[DA40CGDFQ]

The image flags are not taken into account and are not exporter in the XML for the texture LIB.

this is not functioning in 1.3.1 Blender 3.3.0.

Also the ForceNoAlpha is not in any of the code for the exporter.

Please add more info on forcenoalpha to SDK docs. Is this a setting for the user or is this a default setting for certain materials/images in those materials.

by design makes no sense to me, if the settings are not exported.

[Boris]

Hello,

We were able to reproduce an issue where the flags were exporting inconsistently, with about a 50% chance of being applied correctly.
I’ve logged the issue.

As for the “ForceNoAlpha”, it’s handled internally in the code and set automatically depending on the texture slot.
It’s not intended to be modified manually, so there’s no need to document it.

Regards,
Boris

[DA40CGDFQ]

So you are saying that we do not need to manually set ForceNoAlpha to true? It will be applied internally in the sim as required.

If so I would think that the docs should reflect this information.