bwillcott

Thank you Pete. I will look into 3110. Not really. The reason being, I am going to have 6 screens attached to one powerful PC (3x GTX-280 nVidia cards) running FSX, with each screen displaying a different View Window. One screen will be used for various minor windows, some requiring mouse access at times. This will take the focus away from the main View Window (#1) where I'll have the ATC window docked. When this happens, all keyboard commands will go to the window with the current focus. Also, the problem with the standard Panels showing up, is because, on occasion, one of my keyboard's Shift keys sticks.:evil: Once I get my sim built, I will be going online also, and this will no-longer be an issue. However, I have other fish to fry before doing that. I am looking into developing a tool to make my GoFlight hardware more flexible, as I intend on getting the Project Magenta software (incl. pmSystems). I want to have the ability to use all the PM offsets as well, with the appropriate updating of the GF displays and LEDs. I am currently still reading the various documentation, including the GFdisplay doco, which looks interesting, along with the doc for FSUIPC. One thing I noticed about the GF-ATC knob, is that, as it isn't an axis, FSUIPC doesn't seem to be able to handle it. I am still reading. :) Again thank you for your patience and help. Brad.

Sorry Pete, Pls forgive my ignorance. I was hoping to have a way of selecting the ATC options without the ATC being selected. As I am building a multi-screen simulator where the ATC window may not have the focus at the time. I have the Goflight GF-ATC set-up using the GFConfig program. What I have found is that at times I get a Panel appearing and disappearing with each press of the selector knob, instead of it selecting the required ATC option. Obviously, I was hoping these would give me the needed access. Perhaps you might know of a solution? Thanks, Brad.

Hi there, I am trying to test some of the offsets in FSX: 66172 ATC_MENU_1 (0x1027C) 66173 ATC_MENU_2 (0x1027D) 66174 ATC_MENU_3 (0x1027E) 66175 ATC_MENU_4 (0x1027F) 66176 ATC_MENU_5 (0x10280) 66177 ATC_MENU_6 (0x10281) 66178 ATC_MENU_7 (0x10282) 66179 ATC_MENU_8 (0x10283) 66180 ATC_MENU_9 (0x10284) 66181 ATC_MENU_0 (0x10285) However, I have had not such luck. I set the Segment in the Interrogate view to 0001, then the address range to 027C - 0285, and nothing was displayed. I then went to the Hwx-Viewer and set the Segment to 0001, Selected All and Read, and got all 0s. Am I doing something wrong, or can't FS-Interrogate access these extra segments?