controlling NGX functions through FSUIPC

[ilanj]

Hi Pete & All - I've been reading for days but I miss something... Is it possible to control NGX functions through FSUIPC set key commands? more specifically, can I use, for example, Shift+CTRL+Z to set EFIS range to 20nm?

What do I need for this?

 

 

Thanks in advance,

Ilan

[Pete Dowson]

Hi Pete & All - I've been reading for days but I miss something... Is it possible to control NGX functions through FSUIPC set key commands? more specifically, can I use, for example, Shift+CTRL+Z to set EFIS range to 20nm?

What do I need for this?

 

I don't have a list of all the special controls PMDG added for the NGX. If you look in the SDK folder, in the PMDG 737NGX folder in your FSX, you will find a file ending in filetype ".h". That is the definition of all the data which FSUIPC or other programs can extract, and also, nearer the end, a list of all the "custom controls" which can be sent to it to do things. You need to find the control you want, and work out the number it needs -- it will be a base number plus another. The base number is also defined, near the top of that list.

 

Once you have the number you just assign it, in FSUIPC, to a keypress or button as "<custom control>" with that number, and any parameter it may need.

 

Regards

Pete

[ilanj]

Thanks Pete - then I got it ok in the first place, but it isn't working for some reason. I suspect it's an NGX issue, not FSUIPC (because I can't get any NGX command to work through FSUIPC). I'll experiment further, but if you have any clue I'd be grateful ;-)

 

Thanks,

Ilan

[Pete Dowson]

Thanks Pete - then I got it ok in the first place, but it isn't working for some reason. I suspect it's an NGX issue, not FSUIPC (because I can't get any NGX command to work through FSUIPC). I'll experiment further, but if you have any clue I'd be grateful ;-)

 

Assuming you have the numbers right, then they should do something, but it might well depend upon the parameter. Unfortunately the PMDG SDK does leave a lot to guesswork and experimentation. One idea is to try using the mouse emulating controls values -- see the thread near here entitled "Offset3110 and ngx problem" where the OP ended with "Then I go back to read the pmdgsdk PDF again,find out there is another way to control.Not write 1 or 0 to the parameter offset3114,but write 0x20000000 or 0x40000000 (etc) to 3114,these numbers mean some mouse operations ,like left click and so on.". Maybe that's the way to go? (Offset 3114 holds the same as the parameter in your assignment).

 

Regards

Pete

[ilanj]

Oh, great chance it is - I'm trying to set the EFIS range & mode, and it is left/right clickable. Trying it out...

[ilanj]

Reporting back: everything works fine now! I followed your ideas to some interesting places, but in the end it was a strange little issue, maybe intentional, but new for me: for each key press I programmed, I had to define a blank action for the release, then press confirm. Only then this control would work. Anyway - we're good now!

 

Cheers,

Ilan

[Pete Dowson]

Reporting back: everything works fine now! I followed your ideas to some interesting places, but in the end it was a strange little issue, maybe intentional, but new for me: for each key press I programmed, I had to define a blank action for the release, then press confirm. Only then this control would work. Anyway - we're good now!

 

Could you clarify, please? What's a "blank action"? Normally you wouldn't program anything on the release. What is it you actually found you needed to do?

 

Regards

Pete

[ilanj]

Yep: since I don't need anything on the release, I chose the blank line above <custom controls>. That is all I did for it to work (I have programmed 11 buttons, I had to do it every time or it wouldn't work...

 

BTW, this all goes for the Aerosoft Australia EFIS+EICAS. Wish I could make the MCP work as well, but it won't send keystrokes like the Efis/Eicas...

[Pete Dowson]

Yep: since I don't need anything on the release, I chose the blank line above <custom controls>. That is all I did for it to work (I have programmed 11 buttons, I had to do it every time or it wouldn't work...

 

Hmm. Odd, since it should be blank by default in any case.

 

Pete