Im bumping this up to make this question

P3D also moved to xml-only preferably

I think have seen some developers claim their planes were completely rebuilt to P3D native, (meaning the latest tech xml gauges, abandoning the old gau dll)

If their planes are not portable automatically to MSFS means...they were not telling the truth?

guess so, the gau format is as old as FS98, the dll probably since fs2002...

Im glad this version doesnt allow dll or gau. No cheating "all-native-original" claims that are untrue anymore

I believe developpers liked gau and dll because they can hide security features to avoid piracy. MS on the other hand by opting all-xml only places security in online connectivity.

Developpers must be worried how they are going to protect their addons with xml files. That must be the issue thats delaying most projects

But back to the question, sure there are many planes with "nearly" all gauges in xml. They should be easy portable with minor changes, even freewares.

I wonder if anyone have tried freewares that you can delete the odd dll or gau to avoid crashes and still make it flyable 

The rest is easy making the manifest.json etc thats all done as text in +notepad, just copy the formats of default planes and change the wording

 

Edited September 12, 20205 yr by kapitan

On 7/17/2020 at 5:54 PM, LHookins said:

If it works, and I have no idea myself, a legacy aircraft will not have all the data necessary to use the modern flight model, so it would have to be using the legacy flight model.  We can't even be sure the legacy flight model will make it to the release version.

Hook

This is not correct. I have aircraft flying perfectly well, using both "modern" and "legacy" f/ms. Except there is not the same ground friction, but then you don't get the crazy nose steering excesses, although this can be ironed out with a lot of work.

1 hour ago, kapitan said:

I wonder if anyone have tried freewares that you can delete the odd dll or gau to avoid crashes and still make it flyable 

I haven't tried any freeware, but I'm currently flying the Golden Age Simulations Super Stearman with my custom Cannibal Queen paint job.  It works... mostly.  I had to delete a sound .dll and haven't tried making a Wwise sound system so I'm missing things like touch down sound but the engine sound from MSFS is fine.

The gauges are all XML and all work except the kohlsman window.  I haven't researched to see what the problem is, but it doesn't matter.

The cockpit textures are fairly high resolution and look very good.  The exterior is missing reflectivity and bump maps.  The yellow-orange color looks better than I expected.

I've been doing edits to the aircraft.cfg and air file to make the Stearman fly the same way I had it flying in P3D.  Some of the numbers aren't being calculated the same way, but I've got it pretty close to exactly what I had in P3D.  I had previously edited the P3D version extensively to make the performance match data given in the book.

Click spots are wonky.  I can't click on anything in the throttle quadrant and some others so I have to use hardware controls, but if I move the mouse around I can get tool tips (useful for the exact mixture setting) but they're somewhere above the airspeed indicator.  Basically I have to use auto start to get the engine running, but after that it flies the way I want.

One very interesting thing is that the slip-skid ball now indicates properly where in the P3D version it would slip rather badly in a turn.  I don't know if this is the ball logic or something in the flight model.  While I have exaggerated adverse yaw set in the .air file, I get none banking into a turn, a small amount leveling the plane.

I've got plenty of custom XML code to implement my own version of "accu-engine" and it all works.  I had to change some numbers in the .air file to get the engine gauges reading correctly, but I'm happy with the result and it matches what I had in P3D.  I'm not going to try to enable spark plug fouling because even at idle the aircraft will creep forward, but the code is there and should work.

The Stearman flies well but is not in any condition for distribution in its current state even if GAS wanted to do it.  I don't have any of the 2D panels so I have to set things in XML code that would normally be done in a panel.

I've currently got 45 hours in this Stearman and I have to say that flying the Cannibal Queen route in MSFS is a lot better than it was in FSX, P3Dv2 and even P3Dv4. 

I doubt any freeware aircraft would convert any better, and even if they did they'd require edits to the aircraft.cfg file and the .air file to make them perform properly.
 

"This is not correct." -- Robert Young

We've figured that out since mid July. 🙂 

Hook

 

Edited September 12, 20205 yr by LHookins

Hi All

Not sure is it suitable ask here.

I got some problem when I convert P3D aircraft to MSFS 2020, I checked in msfsLegacyImporter it show my model is not compatible with MSFS.

However I create the model by my own , have no idea how to fix it.

Could anyone give me some direction?

Many thanks for your help.

Best,

Kay