QUALITYHIGH Flag not working (Ambient Occlusion)

Version: 1.3.23.0

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: When trying to prevent artifacts in my ambient occlusion texture I have no success using the QUALITYHIGH flag in the xml of my COMP texture, there is no difference.
The SDK documentation describes this for my exact scenario and shows screenshots of the improved AO texture with the flag in use.
To be sure I have deleted the old package to do a clean rebuild and restarted the sim, no difference. The pictures below show the entry in the texture xml, the AO inside the sim WITH flag in use and finally the AO in substance.
If I havent missed anything this leads me to the conclusion that the flag might currently be broken and is not working with AO maps.

Repro steps:

Attachments:

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

1 Like

Also seeing this - tried various things and it seems entirely non functional.

1 Like

Thank you for confirming.

Can also confirm that this does not work

1 Like

To everyone with the same problem, I was just made aware of the reason. Basically you should not edit the texture xmls by hand and instead use the image editor in blender. Please have a look at the following link. Latest Blender exporter removes flags from texture xmls (Blender 4.2) - #6 by b1e1n7e

1 Like

Thank you for the feedback :slight_smile:

@HughesMDflyer4 , can you check if this is also fixed for you please ?

Regards,
Boris

1 Like

Thanks, Boris! It is indeed working for me in the SU2 beta.

2 Likes

Thank you for the feedback :wink:

Regards,
Boris

1 Like

After having done a few exports now I would like to report the following.
I had one project build after which the flag was visually not applied, I have checked if it was still set in blender and yes it was. So something must have went wrong elsewhere, maybe in the build or the rendering. Is that a known issue? I will keep watching it.
Edit (one day later):
The same thing has happened again last evening. This time I was able to narrow it down. No matter how many times I tried to build, the flag was not visually applied. A sim restart did not change it either. Only solution was a fresh blender export.
So it seems that every few blender exports the flags are not exported properly. This should be investigated.

1 Like

@Boris did you see my last message? I am runnig into the blender export issue every two to three exports, so it should not be considered as fixed
just wanted to make sure youve seen that

Hello,

Can you test with the exported included in the SU2 sdk core and let me know if it’s better please ?

If not, we will need a sample .blend that reproduce the issue.

See 3) Provide Private Content

Regards,
Boris

Hey Boris,

I´ve had some trouble with the latest blender exporter. My export settings had been lost. Luckily my presets, export path etc. were still there. I had the box ticked which is supposed to save the export settings but with this new version it has not worked. The earlier versions of the 24 exporter did not have this issue if I remember correctly. Maybe you can pass that information on so it can hopefully be avoided in the future. Doing the settings again in all my blend files is quite a task.

I have now done a few exports without issues, however I would like to test it a few days before giving you a final answer.

Hey Boris,

I just noticed that due to loosing my export settings with the latest exporter, my textures had not been exporting. The setting keep original was activated. This lead me to believe that the problem is solved.
However, now that the textures are being exported again, the problem is back as it used to be. No difference with the latest exporter.

Hello @b1e1n7e,

We will need a sample .blend that reproduce the issue.
See 3) Provide Private Content

Regards,
Boris

Hey Boris,

the issue seems to be fixed with the last sdk update.

1 Like