Wow, I'm not alone. What we have made wrong?

 

I don't have the foggiest idea, but as long as it works I'm Happy

Just now installed Prepar3D SDK 2.4 but nothing change. Uninstall and reinstall EMT.

 

Do you confirm that ECZA works in normal mode?

 

In my case it works only in legacy.

 

If I start in normal mode, EZCA crash (FSX handle error) and I have to restart it manually.

I've tried ezca.exe suggested by steve, the beta file. It works. But I'm sure that with 2.3 I used the ezca.exe original FSX file.

 

Do you use the beta file or is there someone is using the FSX file ezca.exe?

Always have used the P3D beta file with Prepar3D, from when it was released back in V2.0 of P3D.

 

Since I also still use FSX (only for PMDG planes now), here is a trick I use;

 

In the Program Files (x86)\EZCA directory, I renamed the FSX vesrion EZCA.exe to EZCAFSX.exe, and the P3D Beta EZCA.exe to EZCAP3D.exe.

 

In the FSX EXE.xml file I then have (manually edited)

 

<Launch.Addon>

 <Name> EZdok camera addon</Name>

 <Disabled>False</Disabled>

 <Path>C: Program Files (x86)\EZCA\EZCAFSX.exe</Path>

</Launch.Addon>

 

In the P3D EXE.xml file I have

 

<Launch.Addon>

 <Name> EZdok camera addon</Name>

 <Disabled>False</Disabled>

 <Path>C: Program Files (x86)\EZCA\EZCAP3D.exe</Path>

</Launch.Addon>

 

Then each of FSX/P3D can use the correct EZCA version on demand at startup, and no confusion exists as to which exe is which/in use if both are named EZCA.exe in the Program Files directory.

 

Rob

Great solution Rob, I have FSX installed like you.

 

But mine is a pure curiosity, why now it doesn't work with 2.4 when with 2.3 works fine using NOT beta file?

 

If I launch manually EZCA.exe (FSX) after p3d is loaded EZCA works fine! Why? This is an initialization problem, seems like ezca.exe couldn't the fake FSX.exe created by EMT when launched via entries in exe.xml. If you run it manually after p3d is loaded, instead it works fine!

 

Mistery?!?

Guys, you won't believe your eyes, I solved the matter:

 

the problem was due to text format in the exe.xml, infact originally it was:

 

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

 

and I got the FSX handle error.

 

So, casually I open exe.xml and format perfectly the text in this way:

 

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

 

what is change? apparently nothing than the tailback of the entries.

 

But this solved the matter!

 

Now it works perfectly and ezca.exe is 1.17 from FSX, not the beta for P3D file, as I said at the beginning of this post.

 

Incredible but it works! :rolleyes:

I was wrong, not solved. It's a mistery! I was running ezca.exe beta erroneusly. I see it on EZCA studio 1.17/beta.

 

If I run EZCA (fsx original, not beta) after P3D is started it works ok. So I thought to run it via FSUIPC autostart option and works fine.

 

But someone can tell me the difference to start a program via exe.xml vs fsuipc.ini, is it not the same way? so, why in a way works and in another not?

Well I to had a problem getting this to work properly this time - seems with new versions of P3D you have to figure out the correct lines in your exe.xml file - found a post by Jean-Paul here and used his text and it works perfectly - thanks for that

 

So here is the line text - take note that this is a virgin exe.xml file you paste all of this exactly if you have loaded fsdreamteam coutl stuff - UT2 or anything else that writes to this file you CAN NOT paste this exactly - you have been warned - you would have to sort thru this if you have done so

 

 

<?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>
<NewConsole>True</NewConsole>
</Launch.Addon>
</SimBase.Document>

Richard thanks for reply.

 

1) are you using ezca.exe beta file from forum or stable fsx version provided with 1.17 update?

 

2) I tried your exe.xml without luck, get always the same error "FSX process not foud. FSX_hanlde:0"

 

3) if I run ezca.exe (fsx version, not beta) via FSUIPC with autorun procedure EZCA works perfectly

 

4) I thought it was a spacing and formatting text problem in exe.xml but evidently is not true.

 

There is something blocking properly initialization of EZCA when launched via exe.xml, via FSUIPC works perfectly. Which is the difference?

Ok, seems that P3D reads exe.xml before fsx.exe*32 process runs up, so you get "FSX process not found. FSX_hanlde:0" error.

 

P3D instead reads FSUIPC.INI maybe a few seconds after fsx.exe*32 process is started, so EZCA.EXE (not beta, see my screen, look at v 1.17, in yours there is v1.17/beta) works fine.

 

Ok, seems that P3D reads exe.xml before fsx.exe*32 process runs up, so you get "FSX process not found. FSX_hanlde:0" error.

 

P3D instead reads FSUIPC.INI maybe a few seconds after fsx.exe*32 process is started, so EZCA.EXE (not beta, see my screen, look at v 1.17, in yours there is v1.17/beta) works fine.

 

 

Hi Riccardo - nice job -I am using the beta exe - never thought to try without it - so cool when it works  

 

Also thinking this xml text lines may not be one fits all - as last time I had something different than this now - weird

Hi all,

 

When I upgraded to 2.4, my results were unpredictable as well. Starting manually after P3D worked most of the time.

 

I use the registered version of FSUIPC and here is what finally got it working for me:

 

-delete the EZCA.exe entry in exe.xml

-Added RunIf<next number>=CLOSE,"C:\Program Files (x86)\EZCA\EZCA.exe" in the [Programs] section of the FSUIPC.ini file

 

EZDOK now runs fine in 2.4. Sometimes it takes a few seconds to get its wits together, but it works. I wonder if running EZDOK through FSUIPC opens it a bit later than if it's loaded by P3D; and that it may be a timing issue.

 

Graham

Guys I tried to disable FSX virtualization from EMT and noted that FSX.exe*32 process is running anyway whenevr I start up Prepar3D 2.4, is it normal?

No idea sorry

I tried to get this to work with p3d 2.3 and 2.4 to no avail.. basically the control panel would come up, sometimes it would show the different views correctly, sometimes it wouldnt (ignoring the fsx process error).. but if you tried to customize a view then do edit mode (num lock 0) and then save it, it would not save the view and crash on an error about writing to an appdata folder (with or without running both as administrator).