codelegend.com

Hi
I am just returning to your product and am using the p3d v2 pro version and get this error message along with an error building AI aircraft list. What do I do?
thx Lee

Hi Lee,

Can you first try deleting

C:\ProgramData\Ideal Flight 10 Professional\Profiles\AIInclude.dat

and restart IF10 Pro.

Let me know if that clears it...

...please also can you try the preview version in Dev & New Builds section Preview discussion.

After that I would need to look at your Aircraft folders specified in C:\ProgramData\Lockheed Martin\Prepar3D v2\simobjects.cfg. Does the error specify the path of the cfg?

Hi Steve,

I am also experiencing this issue with the latest Lionheart Learjet 24b.
I tried your suggestions but none worked. The path is right.

I uninstalled and reinstalled both the aircraft and Ideal Flight without success.

Could you please check it out?

Thanks in advance,
Nikos

So it reports can't read an aircraft.cfg, something in there is unusual?

Can you send the aircraft.cfg or paste it here? It should be obvious the reason for failure to read it as it is a simple text file.

Another possibility is that the file is locked by an app reading the file exclusively maybe? Doesn't seem likely but it's happened before.

The problem Lee had, I have no idea if it worked out, was about failing to build the AI List. We could unset all the AI planes selected and look at any in isolation if it were that.

Basically we can try any plane as AI in IF but we can't just tick a long string of checkboxes and hope they can all work as AI.

These will be true AI aircraft communicating with ATC fully controlled by the sim, so we can check them first perhaps as AI Buddy, that's good when developing AI aircraft, or just add one at a time to the list and see if the AI build fails, then look at the plane cfg, that's all that IF reads.

New things come along in P3D and it's possible IF can be a step behind in some way, but usually IF continues to work at every P3D update as others need changes every time.

But something could creep in especially with a brand new plane. I'm not able to obtain all planes just for testing and so the cost to simply go off and buy it and try it is prohibitive. Generally looking back on the forum, it's rarely just an obvious mistake in the code, mostly problems boil down to something outside of IFs control and they clear up. If I hear nothing more of it then I've not had a chance to put in a work around. Seems odd but IF reads data from those files that is ignored by the sim. Just because an aircraft flys in the sim doen't mean it's all AOK for IF to work on. IF is a machine reader that's blind other than to the data presented. So on rare occasions something can crop up but it's always put right in no time.

Very little happens on these forums and not much to report in private mail either. I'm workng on all the known issues, and the next build moves things along as usual in the aesthetic sense. Normally the nitty gritty is concentrated on, followed by the look and feel of it as it has a lot to do. But the next build is enhanced a lot for the Blind Pilots community which is quite a big ask for any app and proved useful in tidying up IF in several areas.

Hi Steven, I have attached the aircraft.cfg for you to check it

Steve Waite wrote:Another possibility is that the file is locked by an app reading the file exclusively maybe? Doesn't seem likely but it's happened before.

To exclude this specific reason, I rebooted windows and tried again too many times, but no luck.

Steve, I found the problem.
In the aircraft.cfg file there were the following values

cruise_speed = 318.
max_indicated_speed = 358.

When I changed these values to 318.0 and 358.0 respectively, the problem was solved.

Hey Nick,

That was so awesome of you to find that!

I'll check into this condition, it should actually be handled as any normal decimal is, so I can't wait to find out what's causing it. Thanks again.

Steve