• 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 Model Converter X Not Exporting

Uninstalled; reinstalled; deleted duplicates which obviously were installed by other programs. When I deleted the Visual C++ 2013 64bit, and tried to compile for V4.4, the ONLY error was that it was needed...that was the only error. So I double clicked the error line as it said to and installed it. Then all the errors were back again. I don't know what else I can do and it's very frustrating. Here is the latest error log after the Visual C++ 2013 64 bit was installed again.
 

Attachments

  • Error Log Aug 8 2024 1134AM.txt
    4.3 KB · Views: 37
Every single 64 bit installer was uninstalled and every brand new one from Microsoft reinstalled from a complete package I downloaded. This error shows you that Model Converter X does not recognize the Visual C++ 2013 64 bit is installed because it wants a double click to install it. Since it is installed in the apps, What is going on???
 

Attachments

  • After every 64 bit reinstalled.txt
    2.7 KB · Views: 42
Did you install the x86 versions as well? FSX XtoMdl is x86 for sure, for P3D it differs per version and I don't remember what V4 is.
 
I did not uninstall and reinstall all the x86 versions but I will do that right now. Incidentally, just to see what would happen I had a MDCx V1.50 saved and installed that instead of the current version which I removed and all the same errors occur. I will uninstall and reinstall all the x86 versions right now too and get right back to you after I try it again.
 
The error is not coming from MCX, it's XtoMdl that gives the error. So it does not matter which MCX version you run. So need to make sure all XtoMdl dependencies are on your computer.
 
All of this happened because of that corrupted Flytampa Amsterdam for FSX and it went into P3D V4 by mistake and then all fell apart. Just tried to update every one of the xtomdl options and no matter what I do this refuses not to pop up all the same stinking error codes I have sent and have sent and not create a bgl for Prepar3D V4.4 Every single program I have works again except for MDCx so frustrating and I really do appreciate you trying to help me. FSX still compiles bgl's perfectly in Model Converter X. I have redone every one of the XtoMdl options. In the Prepar3 SDK there are many options from 2012 to 2019 all containing XtoMdl.exe. Do you know which one should be used for each P3D version or doesn't it matter. I am using the 2019. Why do the error codes say Microsoft Flight Simulator when my simulator is Lockheed Martin Prepar3D V4.5? Take a close look at the error log I sent before with all the errors in it today. And like you said it doesn't matter what version of MDCx. AND I specified that the preferred simulator IS Prepar3D V4 where that is requested.
 
Last edited:
When I don't install the MS Visual C++ 2013 that Model Converter X wants, it only gives me those two error lines. Even though the program is already in the apps, if I double click the line in the errors, it goes somewhere and downloads another 64 bit Visual C++ 2013 and there are two of them in my apps.
 

Attachments

  • this is without.txt
    854 bytes · Views: 45
Don't bother wasting any more time on this. I installed the Prepar3D V4.5 SDK onto my Windows 7 laptop and made sure that all the options were correctly filled in. When I try and compile it, I get the same stupid list of XML errors which I think is impossible on a different computer with a different, new SDK in a different location as well, the default one LM puts it in, program files. I am almost starting to think that the problem is the collada file that was created by Sketchup and not the SDK or the Visual C++ but then why does Model Converter X tell me that the 2013 64 bit isn't there when it is. I even went on Google with the error code and Microsoft gave me an updated download for the Visual C++ 2013 64 bit because of some error in the past. Phooey on the whole thing and I don't need to waste anymore of your time on this.
 
I know I told you to quit but I continued working tonight. After attaching effects to the 10 fountains I go to compile it AS AN FXS bgl and those stupid xml errors are there in FSX now. I can't compile anything. If I send you the collada file and the textures will you see if YOU can compile it either for Prepar3D V4.5 or FSX bgl. Either one is ok and I can use it. I gotta know if someone else can compile it. If you can then something happened to this computer and I can never use Model Converter X again until I see if the computer I just got from my friend in the mail which won't power up, WILL power up at Office Depot Tech Dept. Or my days as a scenery designer are over. It's been a lousy day. Please give it one more try to see what's going on by trying it on your computer. Thank you.
 

Attachments

  • Airside Garden.zip
    3.9 MB · Views: 47
Here is an update that I had an inspiration this morning. Back when I first started using Sketchup to create buildings for airport scenery, I would download Sketchup 3D Warehouse components like doors and windows which were beautiful to look at. Many of them were so high in "poly counts" that they would max out MDCx back in the V1.4 days. Anyway, then I learned "cleanup" an addon to Sketchup that removes anything that is a duplicate etc and clean them up to a lot less kb's. Good deal! Well, I found out that even doing that, sometimes Model Converter X just didn't like a particular door, window, lampost etc and would error code and not produce the bgl. Well, this morning when I removed the 6 patio tables, it compiled the bgl for FSX perfectly. So since I have some patio tables that I have used before in my KASH airport, I am going to see if they can be added and still compile. Otherwise there just won't be patio tables. Not a big loss. Thank you for all your help. I still don't believe that it will compile for P3DV4 for some unknown reason. If I can get power fixed on the new computer, when I upload everything to IT, I will try again. In the meantime, thank you for all your help and I am just going to use FSX bgl's.
 
I just decided to give it one more try...I uninstalled both the V3 SDK and the V4 SDK. Don't know why I had the V3 because I have never had V3. I downloaded the latest V4 SDK from Prepar3D Developer and installed it. Reset to default everything in the Options. They all looked correct with the SDK in C:\Lockheed Martin where it belongs not in Program Files like it tries to install by default. I read that somewhere but it didn't make any difference at all. I am through trying until I install everything into my "newer" computer a friend gave me onto an SSD along with other programs like Model Converter X and go from there. It had better work because I think that Amsterdam fiasco screwed up something I cannot find even cleaning everything with my AShampoo paid software. Ya All continue to have a good weekend I hope.
 
You must log in or register to reply here.
Back
Top