Sign in to follow this  
Manny

EZDOK - Vexing issue

Recommended Posts

EZDOK is so vexing sometimes... 

 

It was all working fine..and suddenly the GO TO  VC is not working.

 

I set up a camera of my own called VC (This is my default view) ITt' in VC with proper ht and so on. and I assigned a button on my yoke to this view..so no matter where I am, I can click on this button and have my PIC VC view.

 

now when I am in spot view and I click on this button , it doesn't take me to the VC view any more.

 

when I did shift-D and click on the camera "VC", it doesn't take me to the view either (so its not a button assignment issue)

 

But If I do the keyboard button  ""S" 3 times, it takes me to the VC view.

 

It has messed up this thing in all my aircrafts. 

 

Normally when you click on the empty line in "Virtual cockpit" it should take you to the VC...that too has the same issue.

 

But once I do "S" 3 times and I am in VC then when I click on an empty line, it remaisn in VC. 

 

The issue is, once I get  out VC, I cannot get back in unless I do "S" 3 times.

Share this post


Link to post
Help AVSIM continue to serve you!
Please donate today!

I am having another issue maybe they are both related.

 

when I load P3D ( EZDOK along with it), my mouse and keyboard goes out of whack.

 

The mouse wheel behaves differently and the keyboard keys don't function./.if I hit the F key it behaves like Ctrl-F

 

The only way I can get out of it is, if I reboot. Quitting EZDOK or P3D does not restore my keyboard or mouse functions to what it ought to be..

 

I am typing this fine cause I just rebooted. and I have not started P3D.

 

Edited to ADD:


I googled and found there have been similar issues for so many folks in the earlier version..

http://www.avsim.com/topic/473980-ezdok-keyboard-not-working-in-p3d-firstworldproblems/page-3

 

I simply re ran the config.exe.

 

Not sure if that was what fixed it, Now everything seems ok.

 

Hmmm

 

 

Dang! I hate it when I do not know whats going on.  :fool:

Share this post


Link to post

If you look into your processes, you may find that you have ezdoc listed there, and it's possible that it never closed. Consequently, when you have this condition, ezdoc fails to work and it does not give you a clue as to what is wrong.

So, close fsx normally and then check to see if ezdoc is still in the list of active processes( Control- delete). If you see it, close it.

Restart fsx and things should go to normal

tony

Share this post


Link to post

 

 


If you look into your processes, you may find that you have ezdoc listed there, and it's possible that it never closed. Consequently, when you have this condition, ezdoc fails to work and it does not give you a clue as to what is wrong.
So, close fsx normally and then check to see if ezdoc is still in the list of active processes( Control- delete). If you see it, close it.
Restart fsx and things should go to normal
tony

 

Ah ok

 

The problem is back and I had to reboot...

 

OK.. I have a kill process at the end (a batch file..let me add EZDOK to that as well..

 

Thanks

Share this post


Link to post

The problem is back.. Sigh!

 

Tony,

 

That's not the issue.I am having.. I booted up started P3D and everything looked normal.. then I noticed the spot view hat was not working properly so went to settings and assgined the hat switch and then this problem came back like the poltergeist! Sheesh!

Share this post


Link to post

It's like my "Ctrl" key is pressed down permanently. Somewhere the Ctrl key is activated


This may not be an EZDOK issue at all..I am running into this even wehn I do not run the EZCA.exe Hmm..

 

I think I need to remove the FUIPC.ini file and the control.xml and start all over

Share this post


Link to post

I removed the FSUIPC.ini and restarted including EZDOK and it looks ok..so it something in my FSUIPC  is messing up stuff..

 

Redoing the FSUIPC Settings all over again.

 

Not an EZDOK issue.

Share this post


Link to post

After you removed it from FSUIPC, did it still start automatically. Maybe you also had the start command in your XML file and it was trying to start twice. 

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this