Sign in to follow this  
Followers 0
Brenchen

EZCA Not Working Properly

4 posts in this topic

I'm sorry if this problem has been asked and solved before, but I don't know how to ask, let alone search for existing replies. I will try to explain what's happening.

 

I installed very very limited amount of addon on my current computer, with a freshly installed FSX (with SP1 and 2, but not Acceleration). After that, did some tweaking using Kostas tweak (worked really well), and setup my NVidia Inspector.

 

Installed NGX base pack and UK2000 EGLL, with REX-Ess+OD, FSGlobals and ENB and that's it.

 

I then went to install EZCA, all installed, configured and updated to 1.17, but somehow when I load up a flight, the view can default to EZCA view, but whenever I use the hatswitch to look around, it won't budge (I guess this is what EZCA does). The weird thing is, when I use middle mouse button to move the camera around the flightdeck, it won't move, and when I tried to switch some default views, it also doesn't want to work.

 

Does anyone understand what I'm trying to explain? Anyone experienced this or could point me to look in some directions?

 

Thanks in advanced.

0

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

Hi Brendon,

You need to go to the fsx menu options....controls, select your yoke, and scroll down the views section and remove any default views that ezdok uses like A, S, Shift A, Shift S and any pan views that is used by FSX as well. What is happening is the default views are in conflict with ezdok.

0

Share this post


Link to post
Share on other sites

It doesn't sound like you have conflicting controls in FSX, as you'd still see some jumping and wonky views. I think you need to redownload the flight1 wrapper and reinstall. Sometimes you can't reuse the extracted exe. EZCA security won't be verified and nothing will work. Happened to me when I reinstalled FSX

0

Share this post


Link to post
Share on other sites

Thanks guys for the reply. Indeed reinstalling from F1 was what was needed. Now that's done its all working fine! Thanks for the advices.

0

Share this post


Link to post
Share on other sites
Sign in to follow this  
Followers 0