• 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 v3 Unable to import PMDG/A2A .mdl files

Messages
8
Country
brazil
Hello,

First of all, thanks for accepting me in the forum.

I have been using the ModelConverterX to help with my repaints for around 4 years, have been an amazing tool for me. I'm the owner of BravoZuluStudio - http://bravozulustudio.blogspot.com.br/

30 days ago, I decide to upgrade to Windows 10 (64 bits), so I did, installed the P3D V3.4, and the PMDG and A2A aircrafts I own.

Now with Air Canada new livery, I decide to make a repaint for the PMDG 777-300ER.

After painting the first section of fuselage on the Photoshop, I downloaded the MCX to check it out how it's going (alignment and etc.). I opened MCX, and import the PMDG_777_300ER.mdl file, after selecting the file and click on open, nothing happens.

So I close and run the MCX again, same issue, tried with PMDG 747 V3, A2A C172 and A2A C182 .mdl files, same problem! (Also tested with compatibility mode and run as admin, same issue)

But the VC .mdl files for those aircraft opens normally, but the files for the exterior model don't! (The little lamp with "importing" in the left down corner don't even show it, and the event log is clear)

The default aircraft + TFDi 717 .mdl are working fine, but the PMDG and A2A exterior models, not.

Any clue on this? I really need the MCX to see how my repaint is going. (FS Repainter and MDL Reader are not working on W10 x64).
 
Hello...

and Welcome to the Forum! Which version of MCX did you load? to start off...
 
No works! But very buggy! The below image showing the 777 (with default paint and PMDG repaint it's the same grating) in the link for the log:

Text with the log: http://textuploader.com/d1ue4

Image:
WNxnQ
 

Attachments

  • 777.txt
    19.1 KB · Views: 600
  • 777.jpg
    777.jpg
    402.4 KB · Views: 1,030
Hello...

It appears that textures are not loading - failing to load for 1 reason or another.... are the textures in the proper location?

Arno... May need to look at this...
 
Yes, in the pic is my repaint but happens the same thing with the default and officials repaints from PMDG (747V3 all variants and the another variants of the 777).

In the other hand, the A2A it's working fine now.
 
Hmmm,... is the folder structure the same for the PMDG as well as the A2A,... that could be a possibility,...

Try is: load up the aircraft.cfg file for the PMDG,... MCX should give you the option to do so as well.
 
I load up the aircraft .cfg file, same problem (read the aircraft.cfg fine, but back to the bug part when automatically start to load the .mdl)

This is affecting "just" the rear part of the front fuselage section, engines, wings, flaps, gears and tail section.
 

Attachments

  • 777cfg.txt
    167.5 KB · Views: 600
Hi,

MCX appears to be loading all of the "livery specific" bitmaps, and not loading all of the "generic" bitmaps. This is probably because they are in a different folder and the livery contains a texture.cfg file in the texture folder that is not being read for some reason, or those bitmaps are missing in your installation. Perhaps you could post the contents of the texture.cfg file and the livery section of the aircraft.cfg file you are trying to load?

That said, this is one of the most complex models out there, and may not be compatible with MCX.
 
Hi,

MCX appears to be loading all of the "livery specific" bitmaps, and not loading all of the "generic" bitmaps. This is probably because they are in a different folder and the livery contains a texture.cfg file in the texture folder that is not being read for some reason, or those bitmaps are missing in your installation. Perhaps you could post the contents of the texture.cfg file and the livery section of the aircraft.cfg file you are trying to load?

That said, this is one of the most complex models out there, and may not be compatible with MCX.

It's compatible, if you look up in my blog, you will see Star Wars ANA Repaint and LATAM 77W. But I made those repaints on the Win7, now I'm with the W10.

I just uploaded the aircraft.cfg and texture.cfg!
 

Attachments

  • aircraftcfg.txt
    24.3 KB · Views: 757
  • texturecfg.txt
    223 bytes · Views: 551
Hi,

I guess the problem is that MCX doesn't read the texture.cfg file. So it will look in the livery texture folder and else in the texture folder. It seems in this case there is also a common texture folder, but MCX will not search that by default.

Better support for the texture.cfg file is on the wishlist, but time is limited. So as a work around you could add that extra texture folder to the texture search path.

This behavior is not different in Windows 7 or Windows 10 btw.
 
Hi,

I guess the problem is that MCX doesn't read the texture.cfg file. So it will look in the livery texture folder and else in the texture folder. It seems in this case there is also a common texture folder, but MCX will not search that by default.

Better support for the texture.cfg file is on the wishlist, but time is limited. So as a work around you could add that extra texture folder to the texture search path.

This behavior is not different in Windows 7 or Windows 10 btw.

I was thinking in something like this. In the meantime, have anything I can do to "solve" this? maybe change folders/.mdl/.cfg location?

Thanks for the support!
 
You could add the extra folders to the texture search path in the options like I wrote above.
 
Back
Top