Hey everyone,

 

Hope someone has figured this one out. If I have a new plane installed, can I pull all the developers made camera positions into EZCA to have a starting point? External and Internal.

 

 

For example, Carenado or RealAir have some great pre-packed cameras with their planes. Rather than build all new cameras I would like to start with theirs from within EZCA and tweak from there.

 

Possible?

 

Charles.

Yes it is. But you will have to have two sets of keys. One set for the developer's camera positions and another set of keys for the EZCA set of cameras.

 

for instance EZCA asks you to disable S shf S, A and shf A in the FSX menu for key assignments. And then EZCA uses those keystrokes for their own identical functions. 

 

But you can do something different instead. You could keep the original S, SHF S, A, SHF A key assignments in FSX menu, and those will then only move you thru all the developer cameras, just as without having EZCA installeld.

 

Because then in the EZCA menu you assign the same four functions to entirely different keyboard keys. Then you have 8 keys to move thru all the camera views, and camera view categories, both EZCA's and developers'.

 

I find that I have to reset the developers view to the 'virtual cockpit' view (and not to any other developer view) when I want to cycle the EZCA views. If I start at any other developer view except the 'virtual cockpit' then the EZCA keys will cycle thru incorrect views (at nonsense angles that are not useful).

 

I have CH flight stick (4 hats) and CH Pro throttle (4 more hats). And the CH trigger on the flightstick changes the assigments on all keys and hats. So if I hold the trigger and work the hat 4 positions I have S, SHF S, A, SHF A. If I do NOT hold the trigger then working the same 4 hat positions cycles forward and backward the EZCA views and the 3 EZCA view categories (cockpit views, airplane views, fixed views). 

 

I know of no way to put all the views of the developer and all the views of EZCA into one combined set that can be changed with one set of keys. It could be done but only by manually editing the aircraft.cfg file. And if you do that you do not need EZCA which really is mainly a aircraft.cfg editing tool.

 

Of course EZCA also allows eyepoint changes with TrackIR running (EZCA allows these eyepoint changes with TrackIR running to either the EZCA or to the developer views!).

 

I have the 6 eyepoint changes (up, down, left, right, in (forward), out (backward) mapped onto one hat. That hat does nothing except changing the eyepoint and it does it on the fly with TrackIR running!

 

To me this is the biggest advantage of EZCA: allowing changing eyepoint on the fly with trackIR running while holding my head still. For smaller changes of eyepoint I just move my head.