nadimaj

Perfect. Works a treat. Thank you very much Paul. FYI though, works just fine even without the Thread.Sleep (tried 0 then completely removed the line). As I said above, seems to be a generic problem with any externally (app) generated key events not being sent to P3D. Though the above is a great workaround for FSUIPC.

Slight eureka moment. Works outside of my Timer but not when called from within the Timer.Tick event. However, SendControlToFS() is not so picky about timers?

Problem is there regardless of Fullscreen for me. Interestingly, P3D seems unresponsive to any externally originating key sends. I've managed to write something using the SendKeys method available within .NET and that too cannot send keys to P3D, but works fine with Notepad. A bit of research on the web suggests this is related to Microsoft's UAC which thinks it's being clever by blocking external key events. I've tried launching everything as Administrator and disabling UAC, still doesn't work though. Paul, is there any thing about your sample app which might be getting around UAC or something similar? The focus behaviour is exactly as you describe.

Hi all, Prepar3D 4.5.13 FSUIPC 5.1.5.7 C# .NET (Framework vs 4.7) First time I'm dabbing with this. Using the latest Nuget reference (v3.1.24.339). I'm successfully able to manipulate the sim using SendControlToFS but SendKeyToFS does nothing. The sample application is able to send keys fine though (I can pause using the button) //FSUIPCConnection.SendControlToFS(FsControl.PAUSE_TOGGLE,0); //Works FSUIPCConnection.SendKeyToFS(Keys.P); //Doesn't work Thanks!

Wow, thanks for understanding my questions John, and for the pointers. I'll get to it after my next company sim 🙂

I have an issue with FSLabs A320 where some macro calls result in the button or switch assuming a latched condition. The most annoying one that I've been battling with for months is the Rudder Trim switch. In the VC, a simple left click pulls the button momentarily to the Left, and a right click momentarily to the Right. I record this as a Macro, but then the subsequent execution (in my case a CTRL-Key combo) results in a latched condition. The Rotorbrake codes do the same thing so it's not just my macros. I have (after 15 years of being a FSUIPC user!) finally rolled up my sleeves to see what advanced stuff is lurking in the guides and I'm learning new stuff. If there's any examples, of how to code various click type combos, please can someone/Pete point me to the relevant section? I've played around with various 'on release condition' things too but no change. Any suggestion as to what else I can try? A couple of other questions whilst I'm here: 1.) If I make a change inside the MACRO file, can I get away with restarting the flight? or must the sim be restarted? 2.) I read somewhere about a method by which FSUIPC logs details about panels/gauges that were clicked with a list of variables available to play with(?). I hope I got that right. Has this concept been depreciated due to the latest version of FSUIPC using 'Rectangles?' What debug methods are available in the latest version? Again a pointer to the relevant section in the guide would be very helpful! Thanks FSUIPC v5.152

Thanks Pete, I'll try with LUA. I'm helping a colelge student with a project (he needs to see how accurately people can fly in FS using VFR!)

A request for Pete, Would you be able to redevelop GPSOut so that a chosen GPS sentence is output to a raw text file instead of a comms port. If it's too much bother to output all, how about just $GPRMC. I'd gladly do it if you could spare me the code ;) Thanks