P3D v4 LCXML Support for P3Dv4 MDLs?

christopherbritton

Resource contributor
Hi Arno.
We are able to export P3Dv4 native MDLs in Model Converter X, but we are unable to compile models into P3Dv4 native object libraries using Library Creator XML. Are there any plans to bring v4 support to Library Creator XML?

Thanks for all the hard work! Without your programs, development would be a little more of a pain in the rear. :)
 

arno

Administrator
Staff member
FSDevConf team
Resource contributor
Hi,

Let me check, I thought I updated the development release of Library Creator Xml as well already.
 

arno

Administrator
Staff member
FSDevConf team
Resource contributor
I just checked and I didn't update it yet. Does it not work in P3D v2 mode? The MDL header didn't change, so that might work. I need to check that.
 

arno

Administrator
Staff member
FSDevConf team
Resource contributor
Hi,

I have just fixed it and the next development release should support P3D v4 correctly as well. It should be online in about 15 minutes.
 

christopherbritton

Resource contributor
@arno
I have found another bug in Library Creator XML. If you drag and drop P3Dv4 MDLs into a new library, they are recognized as v4 MDLs, however if you open up a saved v4 library XML, it thinks that the MDLs are compiled for FSX.
Also, (although very minor) there is just a small typo in the Options. You duplicated "P3D 2.0 BGLComp path" for the v4 section, but forgot to rename it.

Cheers!
 

christopherbritton

Resource contributor
@arno
I have came across another bug somewhat related to this. It seems that if you physically move your P3Dv2/v4 MDL file to another location, (breaking the path in LCXML) upon loading in your Library XML, it assumes all of the models are for FSX. Currently, in order to bypass this, you must remove the broke model from the list, save, and reload. Only then will it display the correct sim version.
 

arno

Administrator
Staff member
FSDevConf team
Resource contributor
Hi,

I think I have an idea what is going on. If none of the MDL files is found, then only the XML file can be used to determine the FS version. For FS2004 you have the GUID in the XML, for FSX not. So that's why I think it defaults to FSX here. Maybe I should set it to unknown so that you can add FSX or P3D files.
 
Top