FS-Interrogate2std & List of FSX controls

[bwillcott]

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?

[Pete Dowson]

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'm not surprised, as those are NOT offsets, but controls. They are assignable as controls in FS itself or in any of the Buttons and Keys drop downs in FSUIPC. What on Earth made you think they were offsets? That looks like a section from the list of CONTROLS not the Offsets documentation!

I set the Segment in the Interrogate view to 0001

Why? FSUIPC offsets have never actually been extended beyond FFFF. Where are you thinking there are extra offsets beyond?

Please do use the documentation provided. The offsets lists are provided in the Offsets document. The list of control isa list of controls! Exactly as it says!

Pete

[bwillcott]

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.

[Pete Dowson]

I was hoping to have a way of selecting the ATC options without the ATC being selected.

Well you can send any of the FS (or FSUIPC-added) controls via offset 3110, as documented. however, I am not sure what you mean by "without the ATC being selected". I don't use FS ATC (being a Radar Contact user), but I think the controls you listed are those used to select from an ATC menu. Doesn't the presence of the Menu necessitate ATC being "selected"?

As I am building a multi-screen simulator where the ATC window may not have the focus at the time.

Hmmm. I didn't think it needs specific focus, unless perhaps you have undocked it, as when it is present it is stealing the keystrokes or controls it needs in any case. At least, it seems to.

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.

So the GF ATC panel uses keystrokes, not FS controls? That's rather surprising. Is there anything on the GF support forums dealing with this?

Obviously, I was hoping these would give me the needed access.

But access to most all actions in FS is actually via controls (also known as "events" or "key events" -- I have always called them "controls" because they are tabulated in FS's "CONTROLS.DLL". That's what they are for. Keystrokes are assigned to controls. Gauges use controls. You can log controls in FSUIPC's logging facilities. Even when you have an application program writing to FSUIPC offsets in order to get something to happen, more often than not all FSUIPC is then doing is sending the requisite control to FS.

I'm not sure how you got onto "offsets", which are more typically for application programs and programmers. Doesn't GF's config program deal with control assignments? If not can you not assign stuff via FSUIPC's button assignments?

Regards

Pete

[bwillcott]

Thank you Pete.

I will look into 3110.

however, I am not sure what you mean by "without the ATC being selected".

Doesn't the presence of the Menu necessitate ATC being "selected"?

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:

I don't use FS ATC (being a Radar Contact user)

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'm not sure how you got onto "offsets", which are more typically for application programs and programmers.

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.

[Pete Dowson]

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. :)

Why are yuo looking for it as an axis in any case? FSUIPC doesn't handle any Go-Flight axes anyway, or at least not as such -- only DirectInput or joystick axes.

I've never seen one, but the GF-ATC device should have most if not all of its switches and things come up as Buttons in the Buttons and Switches tab. At least it certainly should do if an adequate version of GFdev.dll is installed (i.e. from the GoFlight install package). According to my code there's one dial and 4 buttons or switches catered for. I can't swear that it all works as it should since I've never seen one and I don't remember having feedback on it. The code's been in there a good while though.

Regards

Pete