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

P3D v4 MCX - DSF TO BGL Coordinate discrepency

Hi All,

I'm hoping someone has a quick fix for this one,

I am converting an X-Plane scenery to P3D V4,

When I import a DSF just with cars to MCX and export a BGL from this - the cars are offset in P3D for some reason?

If you see the below screenshots, WED shows all of the cars correctly placed in the DSF // but P3D sim this position has been modified and is not correct,

appreciate any support!
Last edited:
@arno is there a limit on how many objects MCX can handle correctly? - I just can't seem to understand how it is managing to incorrectly place each car, the difference is quite significant?


Staff member
FSDevConf team
Resource contributor

No, there should be no limit. It's probably a bug. Would you have an object to debug with?