All VC switches become inactive--seems to be only after using CHKL

[Noel 4,556]

<p>Unbelievably nice work and I've had 4 really nice flights with the T7, but now, since dabbling in the electronic checklists my mouse no longer interacts w/ ANY switches anywhere in the VC.  I can still click on default ATC window, but everything in the T7 behaves as it it can't interact w/ the mouse pointer.  I search back many pages and didn't really notice anyone else w/ the issue.  The plane performs very well on my rig too.  If I don't hear back here by tomorrow I guess I better submit a ticket.  It's a real bummer--go thru the entire set up ready to pushback and the blithering click spots have all went to sleep!</p>

<p> </p>

<p>Addendum:  I see this was at least one of the reasons for the delayed release and PMDG came up w/ a fix for it.   I'll submit a ticket so they no it's apparently not over for everyone yet.  I have never experienced this issue in decades of simming and I hope we can find a cure quick!</p>

[Boeing or not going 578]

If you can't press any buttons in the vc it sounds like your viewpoint is too far back, literally in the headrest or seat.

[Icon 22 11]

If you can't press any buttons in the vc it sounds like your viewpoint is too far back, literally in the headrest or seat.

I too have this problem. You have one good possibility, but I'm well inside the captains seat view. I too use the ECL, which needs some editing/additions to be effective.

[Noel 4,556]

I too have this problem. You have one good possibility, but I'm well inside the captains seat view. I too use the ECL, which needs some editing/additions to be effective.

Yes I'm afraid I already looked into that possibility as well having done what research into the issue I have.  I'm submitting a ticket now...

[Andydigital 93]

If you have FSUIPC and you are using profiles try making a copy of the FSUIPC4.ini and keep it somewhere safe as a backup, then go into the working file and delete any other profiles you might have, leave your 777 profile intact (unless it was based on another profile when you created it, if it was you should probably clear that too and start again) and that includes deleting the general profile for aircraft you don't have specific profiles for.

 

I had a similar problem when I first installed the 777 and it was a conflict of some kind in one of the other profiles that somehow caused problems. If you get it working then add the other profiles back a few at a time and test again. If the problem comes back you should be able to work out which other profile may be causing an issue.

[Noel 4,556]

 

 

I had a similar problem when I first installed the 777

 

Were you able to tell if using the ECL played any role in what you were seeing?

[SeanBH 9]

I have had this problem as well, and was thinking this was going to be one of those "OMG- will I ever find the answer"-kinda issues. What was strange is that I could mouse around in my other screens where I place displays such as the PFD and HSI, but not my main screen where the VC was. I could even "A" over to the FO view and others, and the mouse was controlling just fine there. Found it was the viewpoint being too far back- by merely resetting it (I have a joystick button dedicated to that), my mouse recovered control. There is a specific distance back that control will disappear, and you don't have to be in back of the headrest to have the issue.

[Icon 22 11]

I have had this problem as well, and was thinking this was going to be one of those "OMG- will I ever find the answer"-kinda issues. What was strange is that I could mouse around in my other screens where I place displays such as the PFD and HSI, but not my main screen where the VC was. I could even "A" over to the FO view and others, and the mouse was controlling just fine there. Found it was the viewpoint being too far back- by merely resetting it (I have a joystick button dedicated to that), my mouse recovered control. There is a specific distance back that control will disappear, and you don't have to be in back of the headrest to have the issue.

 

I found my problem. Though I thought I was close enough, the next time it happened I pulled even closer to the VC with EZDOC and it went away.

[Andydigital 93]

Were you able to tell if using the ECL played any role in what you were seeing?

No not at all, I'd not even bothered looking, I went straight into FSUIPC and cleaned up the profiles I thought might conflict due to similar names and the FSUIPC profile option "substring" (or something like that) and the problem was gone. I also deleted the general assignments for aircraft with no profile set so it may have been a conflict there too.

 

Parts of the VC not working when clicked with a mouse in my experience have one of two causes, EZDok having a camera inside the cockpit geometry (headrest for example), or a conflict somewhere in FSUIPC and one of its profiles as stated above.

[Noel 4,556]

 

 

No not at all, I'd not even bothered looking, I went straight into FSUIPC and cleaned up the profiles I thought might conflict due to similar names and the FSUIPC profile option "substring" (or something like that) and the problem was gone.

 

Well, good thought--I'll check it out, though I don't have a lot of profiles there I don't believe.

[scandinavian13 5,192]

Coincidence.

 

Always check to ensure FSX has not moved your eyepoint/viewpoint into the headrest.

Default view movement keys are:

CTRL + SHIFT + ENTER/BACKSPACE

CTRL + ENTER/BACKSPACE

SHIFT + ENTER/BACKSPACE