Most problems arise from broken connections between P3D and EZdok, follow these steps below:

1. Start the Estonia tool
2. Install the simconnect module again, you can find this setup in your main P3D folder >> \SDK\Core Utilities Kit\SimConnect SDK\Lib
3. Disable the Estonia tool and start P3D to check it out.

This will work if you have acces violation issues.

Matthijs - Thank you. Just tried this but this is a no go. 

 

 

I dont have the sdk folder under p3d. I did have the simconnect installation under the redist\ subfolders. 

 

I ran the Estonia tool and ran the installer.. Disabled this and opened P3D - still have the same access violation. 

 

Thanks

Sri

yes me as well...still no resolution

I have resolved this issue - atleast for me and i hope this works for everyone as this program when it works is really god sent. 

 

On my new PC i only had P3D installed initially and i saw some of the folks who had this issue also the same. I tried installing FSX and that resolved it.

 

I didn't want fsx on this new pc but hey! a small price to pay to get ezdok working. 

 

So this is what i tried tonight and i have it working on P3D. 

 

1) install FSX (Sp1 + Sp2) 

2) Install EZDOK ( Update 1.17 but not the P3D beta)

3) Configure EZDOK and run fsx once to make sure everything is working. 

4) Copy the 1.17 beta executable on to the installation folder

5) Run the Estonia Migration tool 

6) Run EZCA config - Run Config 

7) Launch P3D (For me EZCA Didnt start right away) so i just double clicked on the ezca.exe to open it as well

8) It worked ... 

 

Hope this works for you - good luck

 

Sri

Sri,

 

As I mentioned on Ezdok forum post, here on your install problems:

http://www.simforums.com/forums/ezdok-was-working-butaccess-violation-error_topic49884&SID=1125227396acbd37zez56fe5911863121643519.html

 

You mentioned:

Vaughn - Yes thank you. I did make a modification on the exe.xml file as suggested. 

 

 

I have resolved this issue - atleast for me and i hope this works for everyone as this program when it works is really god sent. 

 

Anyways - from the posts here above and at avsim.net -- i realized (only now) that the original poster had ONLY p3d installed just like me. So hopefully the below steps will be useful to you guys as well. 

 

So this is what i tried tonight and i have it working on P3D. 

 

1) install FSX (Sp1 + Sp2) 

2) Install EZDOK ( Update 1.17 but not the P3D beta)

3) Configure EZDOK and run fsx once to make sure everything is working. 

4) Copy the 1.17 beta executable on to the installation folder

5) Run the Estonia Migration tool 

6) Run EZCA config - Run Config 

7) Launch P3D (For me EZCA Didnt start right away) so i just double clicked on the ezca.exe to open it as well

8) It worked ...

 

******** My follow up:

Glad to hear you installed Ezdok software on your PC, plus the updates and EZdok P3D beta file,  without any errors.

** "I did make a modification on the exe.xml file as suggested"
Ok, good. I also noticed you now have your "Add-ons" menu item. That's good too.

** "5) Run the Estonia Migration tool "
I never have used the Estonia migration tool. I have just never needed it.

** "7) Launch P3D (For me EZCA Didnt start right away) so i just double clicked on the ezca.exe to open it as well"
I do not have to do this ..... something is still wrong with your setup.

Post here the contents of your exe.xml file for me to have a look at it.

I will try this tonight when I come home from work.

 

Did you need to keep FSX installed or could you delete it after?

I have not uninstalled fsx yet - good luck. Hope it works for you

I can confirm that after installing FSX my EZDok cam works. However I did not need to install it with the migration tool. I just open the EZCA.exe manually and did not touch my exe.xml. I did however temporarily enable my virtual FSX in EMT to be able to hit the configure button in EZCA's config.exe.

 

I guess it needed some of the Visual Studios that I couldn't find of the Microsoft site and sim connect? I could be wrong, not a pro in that aspect. I will do another test this evening and see if I can do a clean uninstall of FSX and continue to use EZDok with P3D v2.3.

 

Any who, I am happy I can get some good DHM and camera shortcuts again. Hope this thread can help others getting the same error because the passed month has not been fun at all.

I can confirm that after installing FSX my EZDok cam works. However I did not need to install it with the migration tool. I just open the EZCA.exe manually and did not touch my exe.xml. I did however temporarily enable my virtual FSX in EMT to be able to hit the configure button in EZCA's config.exe.

 

I guess it needed some of the Visual Studios that I couldn't find of the Microsoft site and sim connect? I could be wrong, not a pro in that aspect. I will do another test this evening and see if I can do a clean uninstall of FSX and continue to use EZDok with P3D v2.3.

 

Any who, I am happy I can get some good DHM and camera shortcuts again. Hope this thread can help others getting the same error because the passed month has not been fun at all.

 

"I can confirm that after installing FSX my EZDok cam works."

Good to hear a normal install of EZdok into a FSX works on your new PC / hardware setup without errors.

 

 

"However I did not need to install it with the migration tool."

I personally never needed to use this Migration Tool either.

 

" I just open the EZCA.exe manually and did not touch my exe.xml."

I prefer to copy the EZdok entry from the FSX exe.xml to the P3D exe.xml so it mirrors the correct default EZdok FSX installation.

Or copy the entire exe.xml file in case it was never present in P3D (never installed by other addon software).

That way EZdok start when P3D starts and it will appear in the P3D ADD-Ons drop down menu (which I use often).

 

I also copy the [CameraDefinition.201] data from FSX to each Aircraft.cfg I am using in P3D.