April 4, 20179 yr P3D V3. Can somebody please tell me why I can't get my mouse to hover over buttons and switch them with left or right clicks on the PMDG747. QOTS2? I thought it might be EZDOC V2 so uninstalled that and purchased and installed Chaseplane and yet I still have the same results! Even if Chaseplane is disabled. NGX and other aircraft work fine but everytime I load the 747 the mouse does not show the hovering hand. I am not within the headrest! When I first installed 747 in February it was fine Thanks Dean UK P3DV5 and Xplane 11 SimmerPilotEdge I11, CAT11, A-Z (ZLA), A-Z (WUS) System details: Gigabyte P57v7 CF2 17.3" laptop. Kaby Lake i7 7700HQ CPU (averaging 3.4mhz). NVIDIA GeForce GTX 1070 8mb (laptop version), 16 GB of DDR4-2400 RAM, SSD - Samsung 970 Evo 500GB M.2 NVMe, 1TB HDD 7200.
April 4, 20179 yr Once this happened to me. It turned out to be the couatl module (part of FSDreamTeams' scenery) had run amuck. Since then, I don't run couatl as part of my DLL.XML. No FSDreamTeam scenery? No problem. Richard Chafey i7-8700K @4.8GHz - 32Gb @3200 - ASUS ROG Maximus X Hero - EVGA RTX3090 - 3840x2160 Res - KBSim Gunfighter - Thrustmaster Warthog dual throttles - Crosswind V3 pedals MSFS 2020, DCS
April 4, 20179 yr Check that your view is not inside the seat. Sometimes this happens and you can see everything but not use the mouse. Mark CYYZ
April 4, 20179 yr 6 minutes ago, RichieFly said: Once this happened to me. It turned out to be the couatl module (part of FSDreamTeams' scenery) had run amuck. Since then, I don't run couatl as part of my DLL.XML. No FSDreamTeam scenery? No problem. I guess this could happen but I (and many others) run all kinds of their scenery and GSX without issue on many payware addons including the Queen. Mark CYYZ
April 4, 20179 yr Just now, MarkW said: I guess this could happen but I (and many others) run all kinds of their scenery and GSX without issue on many payware addons including the Queen. To be sure. I had run with this enabled many times before without a problem. ...just a suggestion as to something to try. Good luck, OP. Richard Chafey i7-8700K @4.8GHz - 32Gb @3200 - ASUS ROG Maximus X Hero - EVGA RTX3090 - 3840x2160 Res - KBSim Gunfighter - Thrustmaster Warthog dual throttles - Crosswind V3 pedals MSFS 2020, DCS
April 4, 20179 yr Author Thanks guys but I don't have anything from FS Dreamteam. And I'm not in the seat! UK P3DV5 and Xplane 11 SimmerPilotEdge I11, CAT11, A-Z (ZLA), A-Z (WUS) System details: Gigabyte P57v7 CF2 17.3" laptop. Kaby Lake i7 7700HQ CPU (averaging 3.4mhz). NVIDIA GeForce GTX 1070 8mb (laptop version), 16 GB of DDR4-2400 RAM, SSD - Samsung 970 Evo 500GB M.2 NVMe, 1TB HDD 7200.
April 8, 20179 yr I had this problem aswell, with B737NGX. My solution was an option inside FSUIPC (don't know if you use it). In the "Misselanious"-tabs shows three radio-buttons for mouse-action. After i disabled one of these option all was fine, don't remember wich one. Hope this helps ;-) Regards, William Vrielynck
April 8, 20179 yr Author Thanks William. I have this evening heard from PMDG who suggested cause might be Malwarebytes or Antivirus. I uninstalled Malwarebytes and reinstalled 747 and now knobs and switches are back working! Cheers Dean UK P3DV5 and Xplane 11 SimmerPilotEdge I11, CAT11, A-Z (ZLA), A-Z (WUS) System details: Gigabyte P57v7 CF2 17.3" laptop. Kaby Lake i7 7700HQ CPU (averaging 3.4mhz). NVIDIA GeForce GTX 1070 8mb (laptop version), 16 GB of DDR4-2400 RAM, SSD - Samsung 970 Evo 500GB M.2 NVMe, 1TB HDD 7200.
April 9, 20179 yr Dean, Try reloading Malwarebytes now that you have your mose working, because it has never caused me this problem. The most frequent cause I have had for being unable to use the mouse to move switches, dials etc in the VC is because the eyepoint is too far away from the instrument panel. All you have to do is move your eyepoint closer (Ctrl + backspace) until the mouse works. Have a look at the six eyepoint commands under SETTINGS - CONTROLS IN FSX and play around with them as necessary. Bertie Goddard Bertie Goddard
Archived
This topic is now archived and is closed to further replies.