codelegend.com

My plane is Flysimware MU2. The Attitude gauge does not work when using IF nor when I load IF flightplan only in p3d v5. I test this last night using all IF simulator startup behavior. ATT not working after each test with IF.
Loaded the same F plan from Little Nav Map in to p3d Att worked. Loaded IF plan into p3d Att not working.
Uninstall Rxp gtn then used IF Att not working.

Loaded p3d mooney it worked fine with IF.

Since p3d v5 was out I thought it was just the plane.There is something in the flight plane from IF that conflicts with the plane or it could be the other way.
I've used this plane with IF since Feb 2019 in p3d v4.

The Dev did update the plane for v5.

What you think Steve?

Thanks for the report. I don't think it would be the Plan file. It could be the flight save file since all Ideal Flight flights are started with an Ideal_Flight.fxml.


So it would be handy to check without IF in the mix:

Can you start a flight with that aircraft, check it's working, then save the flight and close the simulator. Now start the sim and go straight to the menu and load the saved flight. Does it work then?

I did your test the ATT worked. After the test I loaded IF flight plan .PLN into p3d ATT not working. I did not use IF your app to load the flight plan. Its something in the .pln that causing this.

Did you try a plan made in the sim planner?

With the sim plan there's only one difference:

Ideal Flight .PLN

Code: Select all

        <AppVersion>
            <AppVersionMajor>5</AppVersionMajor>
            <AppVersionBuild>31</AppVersionBuild>
        </AppVersion>


P3Dv5 .pln

Code: Select all

            <AppVersionMajor>5</AppVersionMajor>
            <AppVersionMinor>0</AppVersionMinor>
            <AppVersionRevision>31</AppVersionRevision>
            <AppVersionBuild>35253</AppVersionBuild>


This difference makes no odds to any aircraft I have loaded either plan with.

Another possibility is your aircraft does not like Approach waypoints in the IF plan, although should not make a difference. Perhaps try with Notepad to insert the four <appversion> lines into the IF plan over the two and see if that helps. Also try making a plan in IF with no approach waypoints so as to be like the P3Dv5 plan. Also test other aircraft with the IF plans. If the other aircraft work OK it could just be a mistake in the aircraft.

...in any case I'm upgrading the <appversion> block to include all four items. It's possible the aircraft is referencing those and doesn't find what it wants.

The next build Preview 25 incorporates the full <AppVersion> block exactly is it is in the v5 .pln. This taken from the new plans:

Code: Select all

        <AppVersion>
            <AppVersionMajor>5</AppVersionMajor>
            <AppVersionMinor>0</AppVersionMinor>
            <AppVersionRevision>31</AppVersionRevision>
            <AppVersionBuild>35253</AppVersionBuild>
        </AppVersion>

If you need that in the plans now, in the meantime, with Notepad, insert over that block into the plan stored in the Flight\New folder before running the flight:

C:\ProgramData\Ideal Flight Professional\Flight\New\0_Ideal_Flight.PLN

Any luck with testing with the sim generated plan or with the IF plan and the appversion block pasted over in Notepad?

I'll check back with this tomorrow - have a good evening!

Please try Preview 25b this includes the .PLN with corrected <appversion> block:

Ideal Flight Professional P3D v4/5

Havent had a chance to test this Steve. Work,Work,Work no flying.