213: Avoid Messing up C172 EZDok Profile

The newly released A2A C172 Trainer is quite troublesome.   Despite the various Saitek accessory incompatibility issues waiting to be solved, the aircraft can mess up the EZDok Camera settings of the default C172 as well.   Because the aircraft is using an atc_model name of C172, which is exactly the same as what the default C172 is having.

EZDok-01

If you are unaware of this and you quickly change the EZDok Camera for it after installation, you are actually messing up the previous profile you tuned for the default C172.  The EZDok Camera can’t differentiate which is which when both aircrafts are using the same atc_model name.   Hope that you have previously saved Camera backups for your C172.

In order to differentiate the two aircrafts from each other, open the aircarft.cfg file of the A2A C172 Trainer under \Microsoft Flight Simulator X\SimObjects\Airplanes\A2A_C172 folder.   Then, look for the [General] section and rename the aircraft’s atc_model name from C172 to C172R (or whatever you think good).

EZDok-02

After reloading the aircraft, you’ll find its name has been changed accordingly.  Now you can freely adjust the camera without the fear of altering the original profile of the default C172.

EZDok-03

Of course, you can modify the atc_model name of the default C172 to C172SP instead, for example.  The principle applies to all aircrafts.

 

 

 

 

 

 

 

 

Advertisements

6 thoughts on “213: Avoid Messing up C172 EZDok Profile

  1. “The newly released A2A C172 Trainer is quite troublesome. Despite the various Saitek accessory incompatibility issues waiting to be solved, the aircraft can mess up the EZDok Camera settings of the default C172 as well.”

    Your problem is that you have a an issue with the A2A C172 Trainer and now like to blame every issue on A2A; an emotional reaction.

    The problem doesn’t lie with A2A, the problem lies with EZDok, who made the mistake to treat the field “ATC_Model” as a unique key. It was never by design meant to be a unique key. FSX allows every third party developer to use any name he wants.

    A2A is not the first one that suffers from poor EZDok design which causes this particular issue and won’t be the last one either.

    Like

    1. Be more reasonable, guy. If you have a stable setup, then something new added to it and causes various issues, shouldn’t it be blamed naturally?
      And if you have read my post carefully and you should find that I am not saying that the A2A C172 is bad. I just report that it doesn’t fully compatible to FSX standard which causes trouble to my gears and messes up my EZDok Camera setting.
      No matter how you guys think about it, if it doesn’t meet my need, it is useless to me.
      Like it or not is a personal thing. Big deal.

      Like

  2. Tom,
    Thanks much.. I have been trying to figure out a good work around for this issues for months know… One other work around I got was to save the profile as a different name and then reload it. (somewhat of a pain in the rear) it works but ya got to remember to do it. This is a much better solution.
    Thanks again.

    Tom

    Like

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s