Chaseplane now gives me an error

[Panman 4]

Hi all,

 

A couple of days ago I installed P3Dv4 (alongside P3Dv3.4) and yesterday I deleted FSX.  Now when I start up chaseplane I get the following message:

 

There was an error while processing the following aircraft.

 

FSLabs A320 CFM (P3Dv3) - Unable to Access cfg file,

FSLabs A320 IAE (P3Dv3) - Unable to Access cfg file,

mjc8q400 (P3Dv3) - Unable to Access cfg file,

 

Make sure you have sufficient permissions to write to this file.

 

Seeing that the only changes were the above mentioned install/uninstall and that my P3Dv3 install was not changed in any way, why am  I getting this error?

Panman

 

[Keven Menard 658]

Hi,

Try again with the latest version

Regards,
Keven

[Panman 4]

I seem to have fixed it by switching to the latest stable version.  I am now back on the latest experimental version and all is well.

 

Panman

[specialist 51]

I too am having issues, and I did try the latest version, and here is what mine says;

 

There was an error while processing the following aircraft.

A2A_C182 (FSX) - Unable to Access cfg file,
A2A_Piper_PA28_180_Cherokee (FSX) - Unable to Access cfg file,
Aerosoft Airbus A318 CFM (FSX) - Unable to Access cfg file,
Aerosoft Airbus A319 CFM (FSX) - Unable to Access cfg file,
Aerosoft Airbus A319 IAE (FSX) - Unable to Access cfg file,
Aerosoft Airbus A320 CFM (FSX) - Unable to Access cfg file,
Aerosoft Airbus A320 IAE (FSX) - Unable to Access cfg file,
Aerosoft Airbus A321 CFM (FSX) - Unable to Access cfg file,
Aerosoft Airbus A321 IAE (FSX) - Unable to Access cfg file,
mjc8q400 (FSX) - Unable to Access cfg file,
PMDG_JS4100 (FSX) - Unable to Access cfg file,
PMDG_MD11 (FSX) - Unable to Access cfg file,
PMDG_MD11F (FSX) - Unable to Access cfg file,
RealAir Duke Turbine V2 (FSX) - Unable to Access cfg file,
Aerosoft Airbus A318 CFM (P3Dv3) - Unable to Access cfg file,
Aerosoft Airbus A319 CFM (P3Dv3) - Unable to Access cfg file,
Aerosoft Airbus A319 IAE (P3Dv3) - Unable to Access cfg file,
Aerosoft Airbus A320 CFM (P3Dv3) - Unable to Access cfg file,
Aerosoft Airbus A320 IAE (P3Dv3) - Unable to Access cfg file,
Aerosoft Airbus A321 CFM (P3Dv3) - Unable to Access cfg file,
Aerosoft Airbus A321 IAE (P3Dv3) - Unable to Access cfg file,
mjc8q400 (P3Dv3) - Unable to Access cfg file,
RealAir Duke Turbine V2 (P3Dv3) - Unable to Access cfg file

Make sure you have sufficent permissions to write to this file.

[mburkhard 23]

I've got the same issue with the same error message, but only for the A2A C172. Using P3D v4 with the latest experimental version.

[Dondy 0]

Same here with the A2A C172. Latest experimental version of CP installed.

Maybe the problem is the "write-protection" of the "documents" folder? I'm still on Win7 and tried for an hour to get rid of the protection but everytime I uncheched the "write protection" box it will check itself when I re-open the settings page of the folder. And yes, I checked that I (the win7 user) do have full access security clearance within Win7.

[Egbert Drenth 250]

Same here, P3D V4, including A2A C172.
New user, installed yesterday and included experimental versions.
A2A C172 (incl all folders, like simobjects) is installed in a folder outside P3D-V4.
I changed user permission for the whole drive and besides that, CP is running as admin

[anden145 2,285]

Same here for me... version v0.8.2 alpha exp.

[Cruachan 705]

On 11/06/2017 at 1:46 AM, mburkhard said:

I've got the same issue with the same error message, but only for the A2A C172. Using P3D v4 with the latest experimental version.

Hi,

I found a workaround which seems to have resolved this issue. The A2A C172 installs to the Libraries\Documents\Prepar3D v4 Add-ons folder on the C: drive.

1) I copied the A2A folder in its entirety over to the same drive where P3D4 is installed.

2) The add-on.xml in this copied A2A folder was then deleted.

3) I opened the original add-on.xml in the Prepar3D V4 Add-ons\A2A folder in Notepad++. The Paths were modified to point to the different drive and the file saved.

Chaseplane now loads without errors. It looks like ChasePlane expects a different installation method and currently can't find the aircraft configuration file if aircraft are installed in the 'Prepar3D v4 Add-ons' folder.

Note: I have left the original A2A installation intact meantime in case it is needed for any updates (in which case you would need to copy across the updated installation) or A2A decide to change their installation method which seems unlikely. In fact, all that is really needed in the 'Prepar3D v4 Add-ons' folder is the add-on.xml file which allows flexibility of choice of drive destination for each aircraft installation.

Regards,

Mike

[specialist 51]

Huh, interesting find, Mike, thanks for letting us know. I wonder if CP intent was to avoid P3Dv4 from removing or deleting any entries when you may sometime have to set your sim back to its default state, without having to reinstall all the addons again. I know that that is to be true when FSDT decided to make their installer place their scenery files outside P3D main root folder. Not sure if addon aircraft will do that in the future or not, but I'm just guessing what the idea behind CP was.

[paradisca1 23]

Now that 18 months have passed since this discussion has this issue been corrected in the latest version of Chaseplane? I have most add-ons installed outside the P3Dv4 root folder and would like to hear that the program will work without workarounds.

Thank you.

Steve P.

 

[Keven Menard 658]

It was fixed