Another Ezdok post...

[groentesoep 22]

Hey guys,

 

I hope someone can help me with getting Ezdok to work. 

One my old pc it used to work under Windows 7 and P3D v2.2. Recently I upgraded to a new pc and installed P3D v2.3, but I can not get Ezdok to work.

 

I already read a lot of topics on this on several forums, but to no avail.

 

I installed Ezdok 1.5, the 1.7 update and installed the P3D version of EZCA.exe.

 

When starting P3D the EZCA will start and the icon will show in my taskbar. But when I click on it, the window will not open. The EZCA menu is also missing from the P3D addon menu.

 

My exe.xml looks like this

<?xml version="1.0" encoding="windows-1252"?>
<SimBase.Document Type="Launch" version="1,0">
  <Descr>Launch</Descr>
  <Filename>exe.xml</Filename>
  <Disabled>False</Disabled>
  <Launch.ManualLoad>False</Launch.ManualLoad>
  <Launch.Addon>
    <Name>EZdok camera addon</Name>
    <Disabled>False</Disabled>
    <ManualLoad>False</ManualLoad>
    <Path>C:\Program Files (x86)\EZCA\EZCA.exe</Path>  
  </Launch.Addon>
  <Launch.Addon>
    <Name>Couatl</Name>
    <Disabled>False</Disabled>
    <ManualLoad>False</ManualLoad>
    <Path>fsdreamteam\couatl\couatl.exe</Path>
    <CommandLine>--mode=prepar3dv2</CommandLine>
  </Launch.Addon>
</SimBase.Document>

My dll.xml looks like this:

<?xml version="1.0"?>
<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>Addon Manager</Name>
    <Disabled>False</Disabled>
    <ManualLoad>False</ManualLoad>
    <Path>bglmanx.dll</Path>
  </Launch.Addon>
  <Launch.Addon>
    <Name>ObjectFlow</Name>
    <Disabled>False</Disabled>
    <ManualLoad>False</ManualLoad>
    <Path>D:\Prepar3D\ORBX\FTX_AU\FTXAA_ORBXLIBS\Scenery\ObjectFlow.dll</Path>
  </Launch.Addon>
  <Launch.Addon>
    <Name>VistaMare Core</Name>
    <Disabled>True</Disabled>
    <ManualLoad>False</ManualLoad>
    <Path>VistaMare\ViMaCoreX.dll</Path>
  </Launch.Addon>
  <Launch.Addon>
    <Name>Migration Tool Plugin</Name>
    <Path>MigTool.dll</Path>
    <DllStartName>module_init</DllStartName>
    <DllStopName>module_deinit</DllStopName>
  </Launch.Addon>
  <Launch.Addon>
    <Name>as_connect</Name>
    <Disabled>False</Disabled>
    <Path>as_srv\as_btstrp.dll</Path>
  </Launch.Addon>
  <Launch.Addon>
    <Name>PMDG HUD interface</Name>
    <Disabled>False</Disabled>
    <Path>PMDG\DLLs\PMDG_HUD_interface.dll</Path>
    <DllStartName>module_init</DllStartName>
    <DllStopName>module_deinit</DllStopName>
  </Launch.Addon>
  <Launch.Addon>
    <Name>FSUIPC 4</Name>
    <Disabled>False</Disabled>
    <Path>Modules\FSUIPC4.dll</Path>
  </Launch.Addon>
  <Launch.Addon>
    <Name>IvAp</Name>
    <Disabled>False</Disabled>
    <Path>D:\IVAO\IvAp v2\ivap_fsx_bootstrap.dll</Path>
    <Commandline />
  </Launch.Addon>
  <Launch.Addon>
    <Name>PMDG Interface</Name>
    <Disabled>False</Disabled>
    <Path>PMDG\DLLs\PMDG_Interface.dll</Path>
    <DllStartName>module_init</DllStartName>
    <DllStopName>module_deinit</DllStopName>
  </Launch.Addon>
  <Launch.Addon>
    <Name>RAASPRO</Name>
    <Disabled>False</Disabled>
    <ManualLoad>False</ManualLoad>
    <Path>.\RAASPRO\RAASPRO.dll</Path>
    <DllStartName>module_init</DllStartName>
    <DllStopName>module_deinit</DllStopName>
  </Launch.Addon>
  <Launch.Addon>
    <Name>Flight Recorder</Name>
    <Disabled>False</Disabled>
    <ManualLoad>False</ManualLoad>
    <Path>Aerosoft\Flight Recorder\AS-FlightRecorder.dll</Path>
  </Launch.Addon>
</SimBase.Document>

The following is added to my aircraft.cfg's:

[CameraDefinition.201]
Title=EZdok Aircraft Universal camera
Guid={D8D67955-2E9B-4e75-9D8B-8EFFBBFAC65B}
Description=Universal camera for EZdok cam utility
Origin=Center
SnapPbhAdjust=Swivel
SnapPbhReturn=FALSE
PanPbhAdjust=Swivel
PanPbhReturn=FALSE
Track=None
ShowAxis=FALSE
AllowZoom=TRUE
InitialZoom=0.40
ShowWeather=Yes
InitialXyz=0,0,0
InitialPbh=10, 0, 0
XyzAdjust=TRUE
Category=Aircraft
MomentumEffect=FALSE
ClipMode=Minimum
HotKeySelect=4

I used Opus recently, but just don't like it as much as Ezca and it refuses to work with the Airbux X 318/319. That's why I really would like Ezdok to work.

 

Anybody got any tips or ideas?

 

Thanks in advance

[vonmar 121]

Bastiaan,

 

"One my old pc it used to work under Windows 7 and P3D v2.2. Recently I upgraded to a new pc and installed P3D v2.3, but I can not get Ezdok to work."

 

What is OS on new PC?

Is FSX on new PC?

Did you use Migration Tool on new PC?

[groentesoep 22]

Sorry, forgot to mention:

My new pc has Windows 8.1

I do not have FSX installed. Just P3D.

 

The migration tool was only used while running the Config Tool.

 

But I tried removing the camera profiles that were added tot the aircraft.cfg and adding the one manually. This did not help. Or is there something else that the Config Tool is adding? If so, does this mean that I have to manually edit all my aircraft.cfg files back to their original state (whatever that may be)?

 

Thank you for your reaction

[vonmar 121]

Bastiaan,

 

"Sorry, forgot to mention:

My new pc has Windows 8.1

I do not have FSX installed. Just P3D.

The migration tool was only used while running the Config Tool."

 

 

Those are the reasons you are having problems., IMO.

 

I forgot to ask if you downloaded a fresh copy of EZdok from Flight One?

[groentesoep 22]

Thank you for your help.

 

I was afraid it was going to come down to this. Well, seems I have to do a full re-install of P3D then. :-s

[Fi5kuS 57]

No, you don't. The only EZdok versions that are working with v2.3 is 1.15. Neither the 1.16 update or 1.17 beta for P3D doesn't work. 

[Artem Crum 5]

 

 

Neither the 1.16 update or 1.17 beta for P3D doesn't work.

The 1.17 version works fine, but you have to install FSX and start EZCA inside it to allow it to build it's database. After that init process EZCA 1.17 will work in P3Dv2 with no problems.

[Fi5kuS 57]

The 1.17 version works fine, but you have to install FSX and start EZCA inside it to allow it to build it's database. After that init process EZCA 1.17 will work in P3Dv2 with no problems.

 

Huh, did not know. Thanks!

[groentesoep 22]

Well, anyway it all still requires me to re-install P3D to reset all the aircraft.cfg's to default. At the moment I'm not prepared to do that. This whole Ezdok thing has already cost me more time and frustration as I want. Re-installing my whole P3D setup with all it's add-ons is going to cost me another week.

 

I unistalled version 1.17 and tried installing v 1.15 (as administrator of course), but without any succes. After that I uninstalled everything again and installed v.15 and v1.17 and the P3d update, and did not run the EMT, but it still will not work.

 

There is just no way I can get the Addon-menu to work.

 

I'm still wondering though what running the Config Tool using EMT changes besides the usual additions to the aircraft.cfg files and the exe.dll, so that it messes everything up beyond repair....

[Ss944 1]

I had an issue with installing ezdok on to p3dnot long ago and have managed to resolve it. Do u have fsx installed?

http://forum.avsim.net/topic/448780-ezdok-was-working-butaccess-violation-error/?fromsearch=1

[gfd 15]

HI groen,

 

If you have the Estonia Migration Tool, you can fix this up. I would uninstall EZDOK and get rid of all traces, including the aircraft.cfg entries. Then you can start clean.

 

What I did was this:

-went to this link: 

 

http://www.simforums.com/forums/ezdok-and-prepar3d_topic40274_post236510.html#236510

 

and downloaded the 1.17 beta for p3d.

-installed EZDOK 1.15 using the Estonia Migration Tool, after activating Virtual FSX

-updated to 1.17. Probably unnecessary, but I'm paranoid

-dropped in the 1.17 beta mentioned above into the EZCA installation folder, overwriting the existing file

-with Virtual FSX still activated in EMT, ran the EZCA config tool and clicked on Configure FSX. That added the camera into the aircraft.cfg files

-added the ezdok entry into exe.xml

 

<Launch.Addon>
    <Name>EZdok camera addon</Name>
    <Disabled>False</Disabled>
    <Path>C:\Program Files (x86)\EZCA\EZCA.exe</Path>
 </Launch.Addon>

 

-deactivated Virtual FSX in EMT

 

EZDOK is running fine on my machine. I can't think of anything else that may be creating an issue. One thing you might check is this: are you running P3D as administrator? If so, I think you also should setup EZDOK to run as administrator.

 

Here is another link with a tutorial on installing EZDOK. If the above doesn't work, give it a try:

 

http://forum.avsim.net/topic/429386-p3dv2-ezca-setup-tutorial/

 

The poster (cvearl) had FSX installed as well. I only have P3D on my machine. Hope this helps.

 

FYI. The EMT fools installers and configuration tools into thinking they are installing/configuring for FSX. It creates dummy files, registry entries and redirects programs to the correct P3D folders, etc. It doesn't change anything other than the installation/configuration paths for programs.

 

Best of luck,

Graham

[adi518 73]

Ok.. some rumors de-mystified:

 

1.17 works perfectly fine under p3d 2.3 and win 8.1.

 

However, this is the situation.. a lot of people are installing p3d on a fresh win 8.1, meaning without installing fsx first.

 

What does it do? it creates a problem, where simconnect isn't installed nor gets installed by the p3d installer. Therefore, LM has included a few simconnect setup files in a folder called 'redist' in p3d root folder.

 

Inside of it, there are few versions of simconnect. You have to install the latest one (sp2) in order to regain functionality for Ezdok, but wait that's not all. You also need to create a simconnect.xml file and put it where your dll.xml and exe.xml are. Then, your Ezdok will work. Look for my thread with detailed explanation.

[jtwhite 36]

Have you ever worked for days to get something to work, give it up, come back to it later and BAM, fix it? Well, that's the way it was with EZCA, thanks to this thread. Im not sure exactly what I did, it being a "try this, try that" thing, not very scientific, but ill try to run through it

Im running p3d V2.3.

I ran the migration tool, then installed EZDOK.

I copied the EZCA folder over to my P3D folder (I dont think this matters; it just made it easier to get to).

I opened the exe.hml file and changed the target of the program to my P3D folder (which for me was "E:\Prepar3D V2."

I then ran the config, and although it gave me some mumbo-jumbo warnings, the list of aircraft appeared, and I closed it.

I ran p3D and then manually started the EZCA program.

VOILA, there it was in the addon menu, and it works perfectly. It even had the camera settings I used back when the program worked.

I did figure out that the migration tool has to be running to use EZCA, or else P3D crashes.

So, there you have it.

Finally, I can sleep tonight (ha ha). It's just a nice little program and I hated to see it fall by the wayside.

 

John

Now that I think about it, most of the steps above are not needed.

With migration tool, the program can build the database, and the error I got about the exe.hml merely said it wouldnt start automatically, which means just start it yourself once you get P3D running.

 

Sorry if I seem to be babbling, but it's kinda like talking to yourself.

Im just glad to get it running again.

[gfd 15]

 

 

Im just glad to get it running again.

 

Cool!!

[groentesoep 22]

Ok.. some rumors de-mystified:

 

1.17 works perfectly fine under p3d 2.3 and win 8.1.

 

However, this is the situation.. a lot of people are installing p3d on a fresh win 8.1, meaning without installing fsx first.

 

What does it do? it creates a problem, where simconnect isn't installed nor gets installed by the p3d installer. Therefore, LM has included a few simconnect setup files in a folder called 'redist' in p3d root folder.

 

Inside of it, there are few versions of simconnect. You have to install the latest one (sp2) in order to regain functionality for Ezdok, but wait that's not all. You also need to create a simconnect.xml file and put it where your dll.xml and exe.xml are. Then, your Ezdok will work. Look for my thread with detailed explanation.

 

I haven't tried this yet. I'm going to give it a go this evening.

 

And BTW thanks everybody for your suggestions and help.