Sign in to follow this  
HondaJet

Error Every Time I add a New Aircraft

Recommended Posts

I am running P3Cv3.3.5 and CP is v0.1.622.   

 

This is the 3rd aircraft I have added to CP and each time I get this error --  "Aircraft misconfigured
We have fixed a configuration issue with this aircraft to make it work with ChasePlane. Please reload the aircraft or relaunch the simulator for views to work properly."

 

Why do I keep getting this?  Is it the normal right now at this stage in development? 

What kind of changes did it make to my aircraft.cfg or other sim files?

Thanks,

Jerry

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

Hi Jerry,

 

Some aircraft have cfg entries that conflicts with ChasePlane.

We fix the issue when loading the aircraft.

 

Sometimes, this is caused by a previous EZDok install.

 

Best Regards,

Keven

Share this post


Link to post
Share on other sites

I did just convert over from EZdok so maybe that is what is doing it.  I did uninstall EZdok before Installing CP.

Thanks for the info.

Jerry

Share this post


Link to post
Share on other sites

Keven,

I am not sure I know what you mean about ... Restore the configuration?  I had used EZdok on my last flight but when I bought CP the next day I did the uninstall just as it had been the day before.

If you tell me more about the restore process in your question I will post the answer.

Thanks for your support, I can see from these forums you are a busy guy.

Jerry

Share this post


Link to post
Share on other sites

Some EZDok version will leave traces of itself in cfg files after a traditional uninstall.

You have to Restore the configuration in the Config.exe

 

tNtkN4y.png

 

Regards,

Keven

Share this post


Link to post
Share on other sites

I guess I am out of luck since the Configurator tool is gone after I uninstalled EZdok.  Hopefully it won't mess up going forward with CP.

Share this post


Link to post
Share on other sites

It shouldn't.

 

We will add a configuration check at launch to prevent this kind of error in upcoming versions

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this