• 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.

HTML report doesn't find textures

  • Thread starter Thread starter GHD
  • Start date Start date
Hi George,

Let me check if I can reproduce this. The same logic is used to find the textures in both cases.
 
The first few pics in the report display fine, it is the later ones which are missing. Each run shows a different number (at the beginning) with textures.
 
OK, I'll try with a bigger library as well then.
 
It knows what the textures are, it just doesn't display them.

Report attached.
 
Last edited:
Hi George,

I tried to reproduce the problem, but I can't yet. I used one of the default FSX libraries and the object report is fine.

Do you see warnings or errors in the event log while the object report is being generated?
 
Yes, it doesn't load any of the textures during the report generation:



But during model loading, it only misses the _LM texture, but displays the model correctly:

 
Hi George,

Very weird. The same logic is used in both cases. And the object report just switches to the model like you would do when you browse through the library. Let me think if I can find a way to reproduce this somehow.
 
Back
Top