Slipstick

I have both the Channel and Normandy maps on my Steam DCS installation and wanted to get the appropriate Normandy 2.0 upgrade, but the DLC for this combination has no price and there doesn't seem to be any way to "purchase" it. I contacted Steam support and they replied that it appears that this content is not available in my region (U.S.), which is odd. They suggested that I contact the publisher. Can someone help?

I have both the Channel and Normandy maps on my Steam DCS installation and wanted to get the appropriate Normandy 2.0 upgrade, but this pack has no price and there doesn't seem to be any way to "purchase" it. Anybody know how to do this? TIA (thanks in advance), Slipstick

Which is why I suggested that to map or go with default premapped buttons be an option.

As I mentioned in another thread, if you load the TM Windows drivers, the MFD properties pages in the Game Controllers control panel will allow you to renumber the MFDs to something other than 1 or 2, in which case they will appear as F-16 MFD "new number" in the DCS controls setup, are not locked in by the default MFD 1 and 2 .lua files, and can be freely mapped. I try to avoid messing with the program files, if I can; I've been burnt by updates too many times in the past.

BIGNEWY locked the original thread, shown below, but I wanted to throw in my zwei Pfennige, as well as offer a possible workaround. The fact that the TM MFD's 1 and 2 are preassigned to the OSB in the DCS controls setup is a genuinely nice plug'n'play time-saving feature for those that add them and should, IMHO, definitely not be changed, unless a "remap TM MFD buttons" option switch, the default being option off, is also added somewhere in the setup screens. The workaround: I have 3 TM MFD's setup and use the third for the CMSP in the A-10C, the plethora of switches on the MFD allowing all the CMSP controls to be mapped with switches to spare. To do this, I had to load the TM drivers in Windows and change the MFD number assignment through the Windows Game Controller dialog -> F16 MFD x -> [Properties]. There is a drop-down to select the "F16 MFD" number, as well as ID LED checkboxes and button test map. Setting my third MFD as '3', it listed as "F16 MFD 3" in the DCS Controls setup and the buttons are freely mapped. Although I haven't tried this, if you change MFD's 1 and 2 to 3 and 4, I suspect you will be able map the buttons normally. Mi dos centavos, Slipstick

Update: The report below can be disregarded. I finally had some time to delve into this, and discovered that the hooked script interrogating the lamps signals was reading the NMSP HARS signal, 606, and then reading the caution lamp HARS signal, 511, using the same 'HARS' identifier, thus overwriting the NMSP value. Changing the latter identifier to 'HARS_CAUTION' corrected the issue. Original post: While trying to implement the A-10C II NMSP panel lights on an external panel, I found that the HARS signal (606) is always 0. In a cursory search through the mod code I found the following in ...\Mods\aircraft\A-10C_2\Cockpit\Scripts: -- Navigation Mode Select panel count = 0 NMSP_buttons = { flag_HARS = 0, flag_EGI = counter(), flag_TISL = counter(), flag_STRPT = counter(), flag_ANCHR = counter(), flag_TCN = counter(), flag_ILS = counter(), flag_UHF = counter(), flag_FM = counter() } function NMSP_button_light(arg,flag) local light_ = CreateGauge() light_.arg_number = arg light_.input = {0.0, 1.0} light_.output = {0.0, 1.0} light_.params = {flag} light_.controller = controllers.NMSP_button_light_controller end NMSP_button_light(606, NMSP_buttons.flag_HARS) -- HARS I suspect this has probably been noticed by others and there is a good reason elsewhere in the scripts, but I can't help but wonder if this is simply an error and, if so, whether we could get this fixed. Thanks.

I recently entered the DCS World and have started with Warthog II. As I have the HOTAS Warthog and rudder pedals and MFD frames, I was looking for a good keyboard layout for use with those and was disappointed with what I could find, so I decided create one myself. Most reading this likely have a layout with which they are happy, but I am quite pleased with how this turned out and offer it for any other newbies looking for some ideas. After clearing the HOTAS and Flight Controls key binds, I was pleasantly surprised by how many keys became available and focused on mapping the UFC and CDU (I started in computing with teletypes and punch cards, so I have a keyboard bias and hate clicking to type), as well as cockpit switches I find particularly annoying to get to with the mouse, like the NMSP and SAS switches. Also, since I have a bit of hand tremor, three-position switches can be problematic with the mouse, so those got thrown in. And, as long as we're adding stuff, how about a bunch of cold-start convenience keys, emergency controls, and some odds and ends. Key binds were chosen, with some unavoidable exceptions, to be somewhat memorable, for example, W for EW, L for landing lights, and T for test and TO TRIM, as well as being influenced by the cockpit layout; there's also a pun in amongst the assignments. The view and camera F- and numpad key binds are untouched. The UFC and CDU are completely operable from the keyboard. The UFC LTR key and CDU numbers are not modeled, as they would be redundant with the key mapping as it is. With the AAP PAGE switch set to OTHER, the UFC FUNC combinations and mirror keys are used to operate the CDU. The attached keyboard map is for an ancient (bought circa Falcon 4.0, if anyone remembers that) Datalux Spacesaver keyboard (so old it doesn't have a Windows key) I use for flight sims. The map shows only the new keybinds after HOTAS and Flight Controls binds have been cleared; unchanged default binds are not shown. The map works fine with a conventional keyboard layout with just a couple of changes. By the by, IO means ON-OFF. Also, the Ctrl modifier for the screen shot is a quirk of the Datalux and not necessary on a conventional keyboard. "If you hear me shout EJECT-EJECT-EJECT, the last two will be echoes, 'cuz I'll be gone."