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

can ModelConverterX convert MFS .bgl file to P3D .bgl or .MDL file?

A

AthenaYan

Messages
2
Country
china
I try to convert MFS Scenery .bgl file to P3D .bgl file,beacuse I want to place these models in to my Airport Scenery，I can open the MFS .bgl file with ModelConverterX.
But when i export it as a P3D BGL file. It always return a error

19:17 XtoMDL Error error : Vertex list has mix of single UV mapped and double UV mapped vertices!

I want to know how to solve this problem , or is there any other way to export these files?
thx!
 
Hi,

As the error message indicates the object has parts that have a secondary UV channel and also parts without. It seems XtoMDL does not allow that. I have not seen this error before. You could try to add a secondary UV channel to the parts without it in the hierarchy editor. That might solve the error.

I'll also add this issue to my todo list to check, maybe I should write the X file differently.
 
arno said:
Hi,

As the error message indicates the object has parts that have a secondary UV channel and also parts without. It seems XtoMDL does not allow that. I have not seen this error before. You could try to add a secondary UV channel to the parts without it in the hierarchy editor. That might solve the error.

I'll also add this issue to my todo list to check, maybe I should write the X file differently.
Click to expand...
THX!
I found i can export these file as. dae files first, and then I can use these .dae file export it as . bgl or. mdl files
 
Hi @arno,
I'm also experiencing this error message.
I can get past it by exporting to an intermediate format like .OBJ and then to .MDL, but it would be really nice if MCX could strip UV1 and keep UV0 whenever it detects both, before exporting to .MDL.
 
I have it on the bug list to check this issue. So I hope to check it soon.
 
Would any of you have a model I can use to reproduce this issue? I tried to make a model with mixed single and double UV, but I have not yet been able to reproduce the XtoMDL error.
 
Thanks, I can reproduce the error now. But I am not sure whay causes it, as all parts have both uv1 and uv2 coordinates in this model. I'll try to figure out what the error means.
 
I had another look at the issue, but I can't really find out what is wrong with the model. It more looks like an internal XtoMDL bug to me. The test model has two parts, both have UV1 and UV2. When I try to export each of them separately the one with less vertices exports and the other one not. But the rest of the X file code is the same. So that's why I think it is a XtoMDL bug.

I will add a menu option the hierarchy editor to remove the UV2, that will allow it to be exported again.
 
I have implemented it now, so it will be in the next development release as well. I have also added a batch operator step to remove the vertex colors.
 
You must log in or register to reply here.
Back
Top