• 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 v2 Compiled Aircraft Models

n4gix

Resource contributor
Messages
11,674
Country
unitedstates
I finally got around to setting up the P3Dv2 SDK this morning. My first attempt to re-export and compile the Milviz F86 model hasn't gone so well so far...

While both exterior and interior mesh models export and compile without error, they will not load in P3Dv2 (error: cannot display model) even though the exterior model displays just fine in the rotating preview window... :confused:

Setting up Max2012 to use the v2 SDK tools is pretty simple. It's just a matter of changing one path in the configuration files.

Getting my new "SendTo" shortcut for the v2 SDK tools was a bit more challenging, since for reasons known only to God and L-M (maybe not even them!) the folders in the SDK have been rearranged drastically... :eek:

Just for fun, I tried the two new .mdl files in FSX. I wasn't surprised that they won't load at all given the changes made to the v2 .mdl format.

Ah well, early days yet! I would have been astonished had everything worked perfectly the first time... :rotfl:
 
I had that error pop up before in FSX about not being able to display a visual model when I could clearly see it in the preview window, but that was due to a model.CFG mistake regarding the interior.

I made he mistake of changing my XtoMDL shortcut path to the V2 one after installing the new SDK (I still use FSX, unfortunately. Haven't gotten my hands on P3D yet.) So obviously it didn't show up in the sim properly. There may be extra things to configure in the V2 XtoMDL, I don't know...but until I buy P3D 2.0, I'm still using the V2 plugins for Max 2014 with the Max 2012 XtoMDL from V1...it works just fine for my needs.
 
Well, I made certain that I used the new v2 xtomdl.exe file to compile the exported .x and .xanim files. I'm going to try in a bit just exporting the fuselage of the F86 exterior, and remove the interior model from the model.cfg file to see what's up.
 
The new V2 SDK is for V2. The models use a new element in their materials that keep them from showing up in V1 for some reason, as well as FSX.

But.... If you use the V2 max exporter, then run the X and Xanim through the V1 SDK XtoMDL compiler, you will get proper FSX/V1.4 models. (That's what I do).



Bill
 
The new V2 SDK is for V2. The models use a new element in their materials that keep them from showing up in V1 for some reason, as well as FSX.

But.... If you use the V2 max exporter, then run the X and Xanim through the V1 SDK XtoMDL compiler, you will get proper FSX/V1.4 models. (That's what I do).

Well certainly, Bill. I'm wanting to (re)export and compile the F86 for P3Dv2...

I have in fact set up three "SendTo" shortcuts: FSX xtomdl.exe, P3Dv1 xtomdl.exe, and P3Dv2 xtomdl.exe...

There's no point to exporting and compiling for FSX/P3Dv1 since that was done well over a year ago. ;)

There is obviously far more than simply changes in the material settings though. I've found that the cause of the crash in P3Dv2 is the "logic node" I've long used to Attach a custom "logic script" in the modeldef.xml file. If the node is present in both the exterior and interior .mdl files, P3Dv2 will barf... every time.

Leaving the "logic node" only in the interior (vc) .mdl, the F86 will load and display properly in P3Dv2, but about half of the animated switches are inoperative. The "Hand" will appear, but clicking on the object produces no response, nor is the sound file played.

I don't really have much time to do any further experiments at present, but eventually I will track down all of the problems.

I've also noted that apparently "animated bones" are no longer supported, or at the very least they aren't working. The 3d landing/taxi lights are not appearing. In addition, the "taxi light" seems to be broken, as the poly assigned to that circuit fails to "light up"... :(
 
Well, at least you can fall back to 1.4 XtoMDL and the models are still fully functioning.


Have you found out anything on the new Material slot? Like what it is, etc?
 
P3D2 Model Compatability

Been following your attempts to convert models and while I'm not a developer of any ability really, I have messed with MS models a bit since FS2000. I use FSX P3D and now v2 and thought my recent and strange experience with P3Dv2 might help in your work to understand v2 discrepancies. My first install v2 went fine and after loading SSW F104 models from P3D1.4. I selected and flew both 1.4 models with a couple of different paint schemes. All appeared and flew normally. Then after a few crashes the SSW models no longer appreared in the livery list even though the folders remained. I unistalled and reinstalled v2 and with help from a display setup guru friend of mine he made several display and GPU adjustments (3 monitor set up) and all worked quite nicely for a couple of days as I flew only stock P3D aircraft with no addons.

Then I reinstalled Sim SkunkWorks F104 models and weapons ( over top of the existing folders from first install) . . strangely all of the 104 aircraft appear in the list and can load but do not show in any view even preview. Virtual Cockpit is missing and not selectable . . look around view works but no zoom . . even more odd is the weapons appear and are selectable . . including the small rotating preview. They all load and are flyable - I could fly-ride an Aim9L or AIM7 missile till its nose hit the ground). The missiles and tip tanks use the token trike virtual cockpit placeholder . . . so I copied model.cfg and panel.cfg files from P3D1.4 104s into P3Dv2 aircraft folders . . . . no effect.

The P3D.cfg file contains: 2 new SimObjectPaths
SimObjectPaths.7=SimObjects\Weapons
SimObjectPaths.8=SimObjects\Countermeasures

If I fly an AIM7 for example it will show the external chase view is fully working with missle textures, exhaust and smoke and ends after a few seconds with either hitting the ground or ERROR 6025 Pure Virtual Function Call exception. . . does any of this help
 
If you are in V2, then this shouldn't be the sim that is doing this, as it can run both V1 and FSX models fine.

What I think you are running into, Cooked is the built in security systems of those planes that prohibit file sharing. If you move them to another location other then your sim folder (like FSX only model packages), then the security system will crash the model. One of mine was doing this.

Are you also running Windows XP?
 
Addon Models in v2

I`m running WIN7 Pro 64bit with i5 650 at 3.2Ghz and GTX770 stock unclocked
The owner of SSW 104 models said there should be no problem just overwriting but I suspect you may be right about some conflicts . . .they will be verifying compatability of all their models soon they said . . thanks for the comments . . will try moving them . . maybe just point to v1
 
Addon Models in v2 - Answer

This probably only applies to SSW installs. It's an install issue . . . when you go to install into P3Dv2 the SSW appends an extra "\P3D" to the end of the path effectively creating an unuseable interior path. Just remove that and it installs fine . . and works fine . . no changes.

I saw P2Dv2 on the path and just did not notice the extra "\P3D"

Whew . . . that was not as complicated as it seemed. Thanks to Mario from Sim SkunkWorks. .SSW . . . once he saw the extra folder in my v2 he knew right away.
 
Back
Top