Search the Community

Is the uiautomation bug still an issue in P3Dv4? I am asking because I seem to fairly reliably get a strange problem when I have been doing a lot of fiddling with the menus. I have not investigated this methodically but I thought I would ask first. When this happens P3D stays running but the reliable symptom is that Windows no longer responds to mouse clicks. The mouse pointer is visible but clicks are ineffective in any application. The mouse pointer soon also slows down to a crawl. The situation appears unrecoverable and if I try to shut down Windows it hangs at the 'shutting down' screen and I have to do a hard reboot. BTW I also notice that my LINDA events stop working, so it could actually be a LINDA problem.

First of all, with MouseClicks you can solve many common problems. Just try with a Lua-Script to Start or Close Engines for the PMDG NGX 737 or try to open the Terrain MAP + Terrain Height on the ND Instrument in automatic. With MouseClicks you can do it. MouseClicks will be available very soon. When MouseClicks Hook-System is activ (intercepting Keyboard) you can still use the Keyboard for other Functions that are not assigned to a Click-File. MouseClicks in NOT connected to any Game or else. You can use it for any Game or else. MouseClicks is including a "Key.txt" File with 47 special Keys/Char you can change for different Keyboards. MouseClicks is executing like the Pilots Hand is moving. Create MouseClicks Files This example is a ClickFile for PMDG NGX 737 The Pilot movements for selecting the Terrain-Data on the ND-Instrument. It seems complicated but it isn't. 1. We create the MouseClickFile or only a Keyboard File Show Terrain_On_Off on the ND Instrument. --- From any actual View switch to the 2D-Panel {F10} --- execute Keyboard Keys --- MouseClicks are executed on the EFIS Control Panel like a Pilot would do. Selecting the MAP ND-View, Selecting Terrain Height(click on center-knob) then click on [Terrain]. --- The ND Instrument is now showing the Terrain Display with the Terrain-Map and the Terrain-Height if both are selected/included. 2. a) We add (View 1) a Joystick-Nr or any Joystick Button Combination. B) We add (View 1) 1 or several Keyboard Keys or Key-Combinations; normally we use a) or B). Joystick number-values are assigned in automatic using 1 or more Joy-Buttons together. 3. With View (2) we can execute any File using the Mouse > click on a Filename. If a File is connected to the Joystick or Keyboard we can execute the File with View(2) or Joystick or KBD. Joystick connection 262144 - Terrain_On_Off is executed. DOORS Using a pure Keyboard File without Mouseclicks included. In this example we open the 2. Door. 1. Door opened (Shift + e) 2. Door is using (Shift + e) then, the delayed Key {2} FSX in Full Screen Just select the Keyboard Keys and save with View (1) Execute as separate File or within another File. Execute via Joystick or 1 Keyboard-Key only or just click on the FileName - View (2) Engine + Lights on Overhead Panel (shift + 6) - From any actual View you switch to any other Panel or Overhead in automatic. - ENGINE Start - ENGINE Stop - Overhead Panel is Fixed. - Execute each Mouseclick x Start or Close engines. Mouseclicks open Switch Covers, click on Switch, close Switch cover. Keyboard Keys a included within the ClickFile. Mouseclicks are executed in sequence like the Pilot Hand is doing. Intrasystem .

Hi Guys, I have just moved into MSFS2020 thanks to the recently released Fenix A320 but I am having problems with clicking switches etc. in the cockpit. I am finding that unless I am viewing the item pretty much square on and fairly close up, the click spots on stitches, knobs and so on are often displaced from where they should be. For example, if I'm in my normal pilot seat view, clicking buttons on the MCDU is almost impossible as the click spots are not over the visual key positions. This means I have to switch to a custom close up view if I want to operate it accurately. Even in a close up view of the MCDU via the 'Instruments' preselected view, the position of the mouse pointer often ends up clicking a key next to the intended one. It's a real nuisance and it's rapidly putting me off the whole thing. I haven't tried this in any other aircraft yet, so I can only comment on my experience with the FA320. Any advice would be gratefully received! Cheers.