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

Two suggestions

roger-wilco-66

roger-wilco-66

Messages
227
Country
germany
Hi Arno,

I have two suggestions for ModelconverterX to propose:

1. Is it possible to handle the xtomdl-limit of texture-vertices inside modelconverterx? I have several objects (ships, aircraft carriers) that have around 50 drawcalls and 60k texture-vertices. When I optimze them with the "minimize drawcall" function, the xtomdl compilation exits with an error and produces a 0 byte file. Apparently, the drawcall minimization almost doubles the texture vertices and is way over the 65k limit for xtomdl.

2. I saw your nice video tutorial on LOD generation and the idea sprang to my mind that this function could be used to make simpler versions (for static objects) of complex models. Ie, take an aircraft or ship and make a static object with reduced complexitivity out of it. Would it be possible to save a down-LODed version of a model seperatly?


Cheers,
Mark
 
Hi Mark,

roger-wilco-66 said:
1. Is it possible to handle the xtomdl-limit of texture-vertices inside modelconverterx? I have several objects (ships, aircraft carriers) that have around 50 drawcalls and 60k texture-vertices. When I optimze them with the "minimize drawcall" function, the xtomdl compilation exits with an error and produces a 0 byte file. Apparently, the drawcall minimization almost doubles the texture vertices and is way over the 65k limit for xtomdl.
Click to expand...

Let me see if I can look into that. I would not expect that the total amount of texture vertices is increased. But you can end up with more texture vertices in one material, that could give trouble as well.

I'll see if I can find a good test object for this.

roger-wilco-66 said:
2. I saw your nice video tutorial on LOD generation and the idea sprang to my mind that this function could be used to make simpler versions (for static objects) of complex models. Ie, take an aircraft or ship and make a static object with reduced complexitivity out of it. Would it be possible to save a down-LODed version of a model seperatly?
Click to expand...

Yes, that is possible already. You might have to manually change the GUID to prevent trouble. In the LOD Creator you can remove any LOD that you do not want anymore, leaving only the simpler versions. Then you can just save the object with another name.
 
arno said:
Hi Mark,

Let me see if I can look into that. I would not expect that the total amount of texture vertices is increased. But you can end up with more texture vertices in one material, that could give trouble as well.

I'll see if I can find a good test object for this.
Click to expand...

Thanks four your answer. If you want, I can send you one of these complex models for testing.

As for the LOD idea, that's great! I was working with the 1.2 version, and did not know this was already implemented in the beta.

Thanks,
Mark
 
You must log in or register to reply here.
Back
Top