• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

MSFS20 Warnings when compiling models, anyone know what this is?

Messages
288
Country
unitedstates
I have no doubt I'm having a texture issue, but I don't know how to resolve it other than eliminating that texture altogether. The warnings I get do not appear to be causing any issues in my models when displaying them in MSFS. But I would still like to get a handle on them and eliminate all warnings if possible.
I believe the texture that the compiler doesn't appreciate is a PBR that I created from the base color. (I do not remember the name of the program I used to create the PBR but can find it on request.)

And yes, I do have all 3 "P" "B" and "R" included in the texture

occlusionTexture and metallicRoughnessTexture must both exist (or both not exist) and be packed together
and sometimes associated with the above error:
Image does not have Asobo extras 'ASOBO_image_converted_meta': 6 / 8

Is there anything unique I need to do to make sure the PBR is "packed together" as mentioned in the error message?

Thanks All!

TB2
 
Last edited:
I have no doubt I'm having a texture issue, but I don't know how to resolve it other than eliminating that texture altogether. The warnings I get do not appear to be causing any issues in my models when displaying them in MSFS. But I would still like to get a handle on them and eliminate all warnings if possible.
I believe the texture that the compiler doesn't appreciate is a PBR that I created from the base color. (I do not remember the name of the program I used to create the PBR but can find it on request.)

And yes, I do have all 3 "P" "B" and "R" included in the texture

occlusionTexture and metallicRoughnessTexture must both exist (or both not exist) and be packed together
and sometimes associated with the above error:
Image does not have Asobo extras 'ASOBO_image_converted_meta': 6 / 8

Is there anything unique I need to do to make sure the PBR is "packed together" as mentioned in the error message?

Thanks All!

TB2

in the shading tab in Blender, look for the gltF Settings node
it must be on "glTF Settings", if is on any of the glTF Settings.00x the warning is thrown
simply use the dropdown menu to move it to "glFT Settings"
 

Attachments

  • gltf.jpg
    gltf.jpg
    27.8 KB · Views: 177
Thank you mamu!!!

I totally forgot about that one! To the best of your knowledge, are there any adverse effects from getting the errors? (such as the PBR wasn't rendered...) Just curious.

One more thing, some of my models don't have just "glTF Settings" without a number behind them. What do you do in that case?

THANKS AGAIN!

TB2
 
Last edited:
I have the same warnings, followed Mamu's advice, and still get them. Unfortunately, Mamu does not indicate where this gITF node connects to.

Oddly, if I compile it a second time, I do not get the error. So I'm just not sure if these warnings are to be concerned with.

Attached are a couple of images showing the error and that I have the same gIFT node, just not connected to anything, because I don't know where/how.
 

Attachments

  • gITFnode.png
    gITFnode.png
    44.6 KB · Views: 89
  • Warnings.png
    Warnings.png
    284.7 KB · Views: 83
Last edited:
Back
Top