EZCA 3.1 for P3D v5 here!!! (beta)

Thanks, worked faultless.

Thanks a lot Nick and Marniftarr, you guys rock!
Be safe :)

timma wrote: Hi Nick thanx for the update .can u pls help me with 1 problem i have when panning around using my hatswitch i get flickering in vc and external view. thanx

no other addons clean install

Not for me either. No menu in add-ons, no functionality.

yakatan/leftseat

RRVyper wrote: Marniftarr/Nick Awesome job! Works great. Installed it, ran the configure tool, added EZCA3.1 folder to antivirus exception, set EZCA.exe and resh.exe to run as administrator, launched P3Dv5 and I'm back using the best camera tool out there. Thanks for the update. There is still the issue with the zoom slider in the Camera Control Panel - clicking the arrows at the top/bottom of the slider doesn't register until you then click on the slider control itself (for making fine adjustments), and the zoom value doesn't show in the box. But the slider itself works.   Cheers. Randy

Many thanks ! works fine for the moment!

Hi Frank. It sounds like your exe.xml file isn't correct. It's located in C:\Users\<username>\AppData\Roaming\Lockheed Martin\Prepar3D v5\. Here's what mine currently looks like:

When I have a chance I will try the exe after p3d is started.

ok thx randy

That doesn't look right. Are you sure that you edited the exe.xml file and not a dll.xml file? I have a clean install of P3Dv5 and do not have a dll.xml file in my appdata/roaming folder. It probably gets created by certain add-ons that require P3D to load a dll file. But I don't see any other entries in yours so something is strange there. Perhaps you installed a different add-on then removed it?

this is what my exe.xml in p3dv5
.
<?xml version="1.0" encoding="Windows-1252"?>
<SimBase.Document Type="Launch" version="1,0">
     <Descr>Launch</Descr>
     <Filename>dll.xml</Filename>
     <Disabled>False</Disabled>
     <Launch.ManualLoad>False</Launch.ManualLoad>
     <Launch.Addon>
          <Name>EZdok camera addon v3</Name>
          <Disabled>false</Disabled>
          <Path>C:\Program Files\EZCA3.1\EZCA.exe</Path>
     </Launch.Addon>
</SimBase.Document>

RRVyper wrote: leftseat wrote: I have ezca vc camera view, but I don’t show it in my addons menu to open up and configure. That means your cameras.cfg file appears to be correctly edited but it sounds like your exe.xml file wasn't (same as Frank). You'll know when you run EZCA.exe after starting the sim. If it still doesn't load, it's either the AV program blocking it or something else that might require a support ticket. Randy

I had the same problem starting EZCA. Starting Prepar3D with admin rights solved it. Now EZCA starts right from exe.xml file. Thanks for the fix.

leftseat wrote: this is what my exe.xml in p3dv5 . <?xml version="1.0" encoding="Windows-1252"?> <SimBase.Document Type="Launch" version="1,0">      <Descr>Launch</Descr>      <Filename>dll.xml</Filename>      <Disabled>False</Disabled>      <Launch.ManualLoad>False</Launch.ManualLoad>      <Launch.Addon>           <Name>EZdok camera addon v3</Name>           <Disabled>false</Disabled>           <Path>C:\Program Files\EZCA3.1\EZCA.exe</Path>      </Launch.Addon> </SimBase.Document>

yakatan wrote: Problem is not the dll.xml, but actually the admin rights for the P3d. Now it works!  Regards Frank

leftseat wrote: Works for me too with P3d admin thanks. I'm trying to slow down the camera when changing views inside the cockpit. having a look through the manual now.

I had a further look at the exe.xml file content issue - if it already exists, the config tool just adds the appropriate EZCA entries. However, if the exe.xml file doesn't exist, the config tool creates it but erroneously uses the <Filename>dll.xml</Filename> entry. You can see this by looking at the config.exe file in an editor.

RRVyper wrote: I had a further look at the exe.xml file content issue - if it already exists, the config tool just adds the appropriate EZCA entries. However, if the exe.xml file doesn't exist, the config tool creates it but erroneously uses the <Filename>dll.xml</Filename> entry. You can see this by looking at the config.exe file in an editor. Nick/Marniftarr, this should be a simple fix. Not sure if it might cause issues in the future. Randy Edit: the correct format can be seen in the ProgramData/Lockheed Martin/Prepar3D v5 folder.