I've searched thru the SDK and manuals but was not able to see a list of "Reserved" key sequences used by the 737NGX, anyone have such a list?

 

Example:

Ctrl + Shift + 0 = .... does XYZ

 

Thanks, Rob.

Since they're able to be changed by the users, none of them are "reserved," so I doubt you'll be able to find a definitive answer.  If you'd like to see what they are, you can look into the the KEY ASSIGNMENTS in the FMC to see what is currently being used.

You could inspect and parse the following file, which contains all of the NGX-specific keybinds:

 

<FSX>\PMDG\PMDG 737 NGX\737NGX_Shortcuts.ini

 

Its contents look like this:

 

[shortcuts]
FD L=70, 0, 1, 0
FD R=0, 0, 0, 0
A/T ARM=82, 1, 0, 0
TO/GA SWITCH=71, 1, 1, 0
CMD A=90, 0, 0, 0
CMD B=0, 0, 0, 0
CWS A=0, 0, 0, 0
CWS B=0, 0, 0, 0
N1 SWITCH=0, 0, 0, 0
SPEED SWITCH=82, 0, 1, 0

...

 

You'll have to figure out for yourself what those parameters and values mean, but with a bit of trial and error that should prove to be all that difficult.

There is a default list of all keyboard commands in the FSX Learning Center.

 

Index Tab > K > Key Commands

 

Regards,

Chris

 

Edit:

 

Sorry, I just realised you were specific to the 737NGX.

Since they're able to be changed by the users, none of them are "reserved," so I doubt you'll be able to find a definitive answer.  If you'd like to see what they are, you can look into the the KEY ASSIGNMENTS in the FMC to see what is currently being used.

 

Yes, correct ... I should have said "default" for NGX 737.  The reason I'm asking is because something in PMDG 737 NGX appears to conflict with my FRAPS key sequence I'm using ... Ctrl + Shift + 0 (screenshot) and Ctrl + Shift + ~ (start recording).

 

 

The reason I'm asking is because something in PMDG 737 NGX appears to conflict with my FRAPS key sequence I'm using ... Ctrl + Shift + 0 (screenshot) and Ctrl + Shift + ~ (start recording).

 

My suggestion would be to go into the KEY ASSIGNMENTS function and try to assign Ctrl + Shift + 0 to some random function in the NGX, and it will pop up and tell you what it is currently assigned to, if it is.  At that point, tell it "yeah, I'd like to assign that stroke to this function instead."  After confirming, you can delete it and it shouldn't be in conflict anymore.