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

FSX Material Report for Library

hcornea

hcornea

Resource contributor
Messages
2,388
Country
australia
I think I suggested this a long time ago, but perhaps with the evolution of ModelconverterX it may be more feasible.

To correctly batch, materials must be identical ... so across a library bgl, it would be a good idea to identify discrepancies between material settings (and correct them!)

A report function that identified the unique mateials and grouped them would make it possible to identify "rogue" materials that were meant to be the same.

A flagged material would have the same diffuse texture .... but at least one different material setting.

So (for example) ... similar to the "object" report that Modelconverter produces, this would be a report sorted by unique material

An output for part of a library might look something like this

Material: VHHH_Fence_trans.dds

Terminal_withFence.mdl 128 tvert
Peripheral_Hangar.mdl 128 tvert
Fence_4m.mdl 16 tvert
Fence_15m.mdl 16 tvert
Fence_64m.mdl 16 tvert
Fence_128m.mdl 16 tvert
Fence_256m.mdl 16 tvert

Material: VHHH_Fence_trans.dds ** duplicate use of texture

Fence_32m.mdl 16 tvert

In this example, the rogue material is in the Fence_32m model and is producing an additional (unnecessary) drawcall.

A simple ModelconverterX examine + edit (or maybe a "get material from xxx.mdl" function! -- another suggestion, that would be cool!) would fix the issue.

Alternatively, back to Max/gmax/TweakFSDS and fix the source file.

Thus, a library.bgl could be checked for efficiency

(please note the above example is a mock-up, and I am not working on Hong Kong international airport)
 
Hi,

Yes, I have a feature on the wishlist to compare materials with each other. I think at that time it was inside one mdl, but would also be useful within a library.

I'll give the feature request a bump on my list.
 
You must log in or register to reply here.
Back
Top