Jump to content

Why are some controller options "grayed out"???


Recommended Posts

And locked so no other controller can be assigned or changed. Like a locked default. ie. mouse inputs, Track IR inputs etc. etc. etc.

for example I want to assign Screenshot to a HOTAS button but it is locked and grayed out with a keyboard assignment "SysRQ" (and WTF is SysRQ anyway?<--rhetorical question) 

Why isn't there any indication to this grayed out/ Locked state within the controls options???? Mind telling us what this is, what its for, why is it there, and how to turn it on or off?

Link to comment
Share on other sites

  • 4 weeks later...
On 12/30/2022 at 11:48 AM, FatSlapper said:

for example I want to assign Screenshot to a HOTAS button but it is locked and grayed out with a keyboard assignment "SysRQ" (and WTF is SysRQ anyway?<--rhetorical question) 

Why isn't there any indication to this grayed out/ Locked state within the controls options???? Mind telling us what this is, what its for, why is it there, and how to turn it on or off?

 

You are probably on the module controls sheet ... select the UI Layer control sheet and bind it to "Make Screenshot"

 

For work: iMac mid-2010 of 27" - Core i7 870 - 6 GB DDR3 1333 MHz - ATI HD5670 - SSD 256 GB - HDD 2 TB - macOS High Sierra

For Gaming: 34" Monitor - Ryzen 3600 - 32 GB DDR4 2400 - nVidia RTX2080 - SSD 1.25 TB - HDD 10 TB - Win10 Pro - TM HOTAS Cougar

Mobile: iPad Pro 12.9" of 256 GB

Link to comment
Share on other sites

You are spot on Rudel but my issue is I want to make screenshots of the P-47D-30 specific vs the P47D-40 specific controls (I am just starting the P-47D after a years long affair with the jets).  I find it easier to figure out sensible HOTAS mappings with these printouts.  I did try the UI route but no joy (the newly UI assigned screenshot keypress doesn't show in any of my modules).  Unfortunately DCS wants to detect my keypress and direct me to its assigned command.  I end up in a loop of bringing up the control listing then pressing "print screen" only to be shown the "print screen" control assignment and no screenshot of the module controls section I was attempting to capture.  It's a bit frustrating but certainly no a game killer.  Interestingly enough, in the past I was able to take print screens in this manner while flying the A-10C and FA-18D.  This is a relatively recent development (at least for me).  If you can help, great.  If not, I truly appreciate your response above.  Many thanks!

Radial Madness

Link to comment
Share on other sites

1 hour ago, sgilewicz said:

but my issue is I want to make screenshots of the P-47D-30 specific vs the P47D-40 specific controls

 

OK, I understand .. I'm afraid the only workaround I can think of, is to use the MAKE HTML button of the Controls screen and then import that onto a spreadsheet. It may look like a ton of work, but actually it makes things easier as it will allow you to easily filter the keybinds by Group, like this:

 

lYr9kNy.jpg

 

 

 

For work: iMac mid-2010 of 27" - Core i7 870 - 6 GB DDR3 1333 MHz - ATI HD5670 - SSD 256 GB - HDD 2 TB - macOS High Sierra

For Gaming: 34" Monitor - Ryzen 3600 - 32 GB DDR4 2400 - nVidia RTX2080 - SSD 1.25 TB - HDD 10 TB - Win10 Pro - TM HOTAS Cougar

Mobile: iPad Pro 12.9" of 256 GB

Link to comment
Share on other sites

I was just about to suggest making the HTML for the same reasons Rudel_chw.  Edit it in Excel or Libre Office (free option if you don't have Excel).

To take a screenshot of the the actual binding screens, just use the PRT SC (or similar) button on your keyboard.  Typically top right part of the keyboard (not always the same place).  I don't think the in-game DCS binding does anything unless you're actually in a plane.

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...