Aircraft Profile associates with Flight Plan

[JoHubb]

On a single occasion only, I used the F33A Beechcraft profile for a flight plan.

Ever since that every plan has associated itself with this aircraft. 
I do not want to delete this profile, but I do not want to use the same one for every flight! 

Having used a profile once,  I cannot find a way to go back to 'no profile'. 

I'd be grateful for advice.

John

[spokes2112]

I too wish there was a "clear" button for that. It's no real big deal though. The only way I know of is to go to the user.config ( C:\Users\USER_NAME\AppData\Local\TA_Software\Plan-G3.exe_Url_SOME HASH CODE\VERSION#\user.config ) and open it up with a plain text or xml editor then go to ~line 500 and modify as such ex.



<setting name="AircraftProfile" serializeAs="String">
   <value>D:\My Documents\Plan-G Files\Profiles\Spartan.profile</value>
</setting>


So it looks like this -



<setting name="AircraftProfile" serializeAs="String">
   <value />
</setting>


If uncomfortable with xml it maybe a good idea to back the file up before doing mods.


Roman

[JoHubb]

So it looks like this -

<setting name="AircraftProfile" serializeAs="String">
   <value />
</setting>
Roman

Thanks, Roman. This put me on the right track but your xml syntax is incorrect.

For others following the thread, the corrected lines must read:

<setting name="AircraftProfile" serializeAs="String">
   <value>False</value>
</setting>

This stops new plans being tagged with a previous profile. Saved plans are still tagged though.

John

[spokes2112]

It may work but it is not a correct setting. The setting should be a path or empty. There is no such path as "False".


If you start up Plan-G with the following -

<setting name="AircraftProfile" serializeAs="String">
   <value></value> <--- NOTICE EMPTY TAG, NOT FOLLOWING SCHEMA
</setting>


Shut down and take a look at user.config again. It will look like this after Plan-G self corrects the setting following schema -

<setting name="AircraftProfile" serializeAs="String">
   <value /> <-- A SELF CLOSING TAG GIVING A NULL VALUE FOLLOWING THE XML SCHEMA FOR SETTINGS.
</setting>


XML as settings is pretty lenient but the program itself is most likely throwing a handled error because it cannot find the path "false" upon loading. 

[JoHubb]

Roman,

Your </value> setting prevented PlanG from running.

The attribute F33A becomes inactive when <value>False</value> is inserted.

Now the program runs and the aircraft profile tag has disappeared. That's all I wanted.

Thanks again.

[spokes2112]

It's not "</value>" but rather "<value />".


The first example is invalid XML while the second is valid.


Just FYI - It's good that it's working for you though.


Roman

[JoHubb]

My wrong, Roman.  :-[

Thanks for your help.