Home Fries

SnapViews are mapped to TMS on the Warthog and TMS Up/Down, CMS Right and T1 on the Cougar. Shifted DX commands on CMS should be normal.

All, A slightly delayed message, but the 2.50 Hotfix 1 is out. This mainly fixes some issues with the A-10C, adds SnapViews for A-10C II, and re-integrates the throttle mapping into the JF-17 diff.luas. Update to hotfix 1 using the CTS Updater. I've also had a couple of people who have experienced the dreaded "stack full" error. I have gone through many of the files and removed redundant code that is now taken care of in a global profile init routine. This should hopefully free up some stack space, but because I can't duplicate the stack error and because it crosses just about every module/profile, I can't test it all myself. Therefore, people who get the stack errors, please update to 2.50a (hotfix 1), backup your CTS\DCS folder, then extract the file below directly into your CTS folder (you should be prompted to overwrite). Even though these changes are low risk, please consider this patch (hotfix 2) an alpha release. Please respond with your feedback on this patch (hotfix 2) either here or on my Trello bugtracker - I would like both positive and negative feedback (i.e. let me know if it works well too). EDIT: 2.50b is now available via the CTS Updater.

I'm not sure how well my script can support your configuration. TUSBA is seen as a separate controller (non-programmable), and when I programmed for the Warthog stick I used the CMS Z axis. I don't have an option in CTS for Warthog with Cougar mapping. The TrackIR recenter command works, so the positioning is likely a TrackIR mapping issue or you may need to reset your default SnapView (or use one of the SnapView configurations included in the script). Not sure about the HARM issue; I assume based on your configuration that you're talking about the F-16. I've had no issues launching HARM in the viper. I'm wondering if it's an issue with the nonstandard configuration because I've seen weird things happen before.

Thanks for the help, uboats. That helped me a lot. Also for people who are comfortable editing lua files, the Thrust iCommand has changed. Just replace ["a2024cdnil"] = { with ["a2004cdnil"] = {

Thanks for the kind words and validation of my instructions! When TARGET starts, it replaces the separate controllers with a single virtual controller (usually "Thrustmaster Combined"), so while I try to match the first 19 buttons with the stick wherever possible, I cannot match the throttle buttons. Regardless, you should be using the "Device Analyzer" instead of the Windows controller app, which can be run directly from the TARGET runtime window (i.e. the window that pops up when you press "play" from within the CTS GUI). Device Analyzer shows you both the buttons on your TM controller as well as what they do on the TM Combined controller. For VAICOM, I have included a profile all set for you to import into VoiceAttack. This will assign buttons 20-23 to the different functions, and all you need to do is bind button 21 (or ScrollLock) to your push to talk in Discord.

Glad you like it. Probably not. I haven't patched yet, but from what I understand it's primarily more functionality on the HOTAS (which is already mapped).

2.50 is released. Change Log: F-14: Added TEMPO and repeat commands to Walkman Volume and interior lights on ROSB17/18 (Pilot). Replaced interior lights on ROSB17/18 with DECM RCV/RPT (RIO). Added optional MFD3 for Pilot and RIO. Added Rudder Trim and reversed Auto/Man wing sweep on CSL/R (Warthog Pilot). Added TCS Trim to S3+Microstick/SC (RIO). Fixed bug where H4 wouldn't map properly (Cougar/RIO). M-2000C: Fixed LOSB4/ROSB2 mappings. Remapped VTB Power/Export to deconflict with VAICOM overlay. P-47D: Added D-40 Rocket controls to RMFD and Rocket/Bomb selector to Warthog Throttle Base. Moved Primer to ROSB11. Changed H2 mapping (switch cover TEMPO long only and jettison S3 with no tempo) for use with early D-30. Added Arm/Safe for all pylons to APENG (Warthog). JF-17: Added VR Zoom to S1. Known Issues: Very close to stack limits. If you receive a full stack error, report it ASAP. P-47 gun safety switch toggle does not work (module side issue) H2U set to Arm discrete command for time being. Some F-14 Pilot bindings incorrect/inop on MFD3 (module side issue). JF-17 throttle doesn't save to diff.lua (module side issue). Manually add the throttle axis.

I just encountered the following with the Jeff: when I fired up my profile the throttle wasn't working. Thinking it was a remapped command, I reassigned the throttle to the Thrust axis, then re-saved the diff.lua. The Z axis as Thrust does not show up either in the diff.lua for the controller, nor the saved diff.lua. I use TARGET, so the main lua would be default.lua. Here are the axis commands in the original diff.lua local diff = { ["axisDiffs"] = { ["a2003cdnil"] = { ["name"] = "Rudder", ["removed"] = { [1] = { ["key"] = "JOY_RZ", }, }, }, ["a2012cdnil"] = { ["added"] = { [1] = { ["key"] = "JOY_SLIDER2", }, }, ["name"] = "Zoom View", }, ["a2024cdnil"] = { ["changed"] = { [1] = { ["filter"] = { ["curvature"] = { [1] = 0, [2] = 0.05, [3] = 0.1, [4] = 0.17, [5] = 0.28, [6] = 0.4, [7] = 0.52, [8] = 0.64, [9] = 0.76, [10] = 0.88, [11] = 1, }, ["deadzone"] = 0, ["invert"] = false, ["saturationX"] = 1, ["saturationY"] = 1, ["slider"] = true, }, ["key"] = "JOY_Z", }, }, ["name"] = "Thrust", }, ["a2028cdnil"] = { ["added"] = { [1] = { ["filter"] = { ["curvature"] = { [1] = 0, }, ["deadzone"] = 0, ["invert"] = true, ["saturationX"] = 1, ["saturationY"] = 1, ["slider"] = false, }, ["key"] = "JOY_RZ", }, [2] = { ["filter"] = { ["curvature"] = { [1] = 0, }, ["deadzone"] = 0, ["invert"] = true, ["saturationX"] = 1, ["saturationY"] = 1, ["slider"] = false, }, ["key"] = "JOY_SLIDER2", ["reformers"] = { [1] = "JOY_BTN30", }, }, }, ["name"] = "T6_Axis: Antenna Elevation", ["removed"] = { [1] = { ["key"] = "JOY_RX", }, }, }, ["a2033cdnil"] = { ["added"] = { [1] = { ["key"] = "JOY_RX", }, }, ["name"] = "TDC Slew Horizontal", }, ["a2034cdnil"] = { ["added"] = { [1] = { ["filter"] = { ["curvature"] = { [1] = 0, }, ["deadzone"] = 0, ["invert"] = true, ["saturationX"] = 1, ["saturationY"] = 1, ["slider"] = false, }, ["key"] = "JOY_RY", }, }, ["name"] = "TDC Slew Vertical", }, }, And the axis section in the latest diff.lua (the gap is the missing thrust axis since I used file compare) local diff = { ["axisDiffs"] = { ["a2003cdnil"] = { ["name"] = "Rudder", ["removed"] = { [1] = { ["key"] = "JOY_RZ", }, }, }, ["a2012cdnil"] = { ["added"] = { [1] = { ["key"] = "JOY_SLIDER2", }, }, ["name"] = "Zoom View", }, ["a2028cdnil"] = { ["added"] = { [1] = { ["filter"] = { ["curvature"] = { [1] = 0, }, ["deadzone"] = 0, ["invert"] = true, ["saturationX"] = 1, ["saturationY"] = 1, ["slider"] = false, }, ["key"] = "JOY_RZ", }, [2] = { ["filter"] = { ["curvature"] = { [1] = 0, }, ["deadzone"] = 0, ["invert"] = true, ["saturationX"] = 1, ["saturationY"] = 1, ["slider"] = false, }, ["key"] = "JOY_SLIDER2", ["reformers"] = { [1] = "JOY_BTN30", }, }, }, ["name"] = "T6_Axis: Antenna Elevation", ["removed"] = { [1] = { ["key"] = "JOY_RX", }, }, }, ["a2033cdnil"] = { ["added"] = { [1] = { ["key"] = "JOY_RX", }, }, ["name"] = "TDC Slew Horizontal", }, ["a2034cdnil"] = { ["added"] = { [1] = { ["filter"] = { ["curvature"] = { [1] = 0, }, ["deadzone"] = 0, ["invert"] = true, ["saturationX"] = 1, ["saturationY"] = 1, ["slider"] = false, }, ["key"] = "JOY_RY", }, }, ["name"] = "TDC Slew Vertical", }, },

I haven't heard of that, but it sounds pretty messed up. Glad you got it squared away! :thumbup:

All, FYI, I just put 2.50 into Release Candidate status. Once it passes internal testing I'll release it. It updates the F-14 and AV-8B Enhanced LUA files to the 2.5.6.55363 Openbeta build, fixes some bugs, and adds rockets to the P-47D-40.

This is just a list of some keymapping bugs I came across in testing the 9/23 build of DCS. All buttons have been tested with DirectX, but not keyboard macros. Pilot: ARC-159 function incr just toggles between Off and Both ARC-159 function decr is inop ARC-159 discrete functions Both and Main are reversed RIO: TACAN Cmd button presses but never releases (requires mouse to release) Datalink Mode up/down inop TCS Trim is a recentering axis rather than a relative movement axis (i.e. slew) Finally, if TCS Trim is ever set as a relative axis, I recommend a TCS Trim center function since you can't see the center position on the cockpit knobs.

Ok, roger that! Good point.

In the picture above, I was using hands for alt-printscreen, so my station keeping was not good. I also use little rudder inputs to maintain position without using roll inputs, so that could explain the off-center ball.

Nicely done. Love the rivalry banter too - classic!

Thanks for the follow-up, Hollywood. I didn't realize that the comms were integrated with the NS430 (I thought it was just non-functional switches), but I can see how that might cause issues. I would definitely love a more robust explanation, but then I'm also a software developer...

Operationally, it was usually the Tomcat that buddy lased for the Hornets. You have a RIO who could focus on keeping the LANTIRN on target while the pilot flew the aircraft, and the single-seat hornets (before the F model) could launch and leave. It also meant that the Hornets wouldn't need to carry ATFLIR, and didn't need to use the double-ugly configuration.

Unfortunately, no. TARGET only recognizes the first two MFDs for programming, so without modding the TARGET headers in Program Files (which is something I wish to avoid) there's no way around this. Anything I have done with extra MFDs has been using MFD3 and MFD4 as separate controllers (using the S3 button as a shift modifier when useful).

Roger all. I'll give it a look. You're welcome. Thanks for the report.

Something I'll do as RIO is go into ground stab, then use the HCU and the button on top to offset the display so the aircraft is at the side of the TID opposite its vector (i.e. on the left part of the TID if heading east). This gives you the same level of SA as aircraft stab, and you get the absolute vectors instead of relative. I'll use this early on when I'm trying to figure out who's who in the zoo.

Any amplification on this? I have the NS430 and would like to know if and when I can re-enable it.

The enjoyment of flying RIO is the best kept secret in DCS. That said, I'm always trying to tell the secret to people who will listen!

I find myself counting how many times I increment the ICLS knob when I need to set the channel, rather than matching the setting. While this may be realistic, it can be frustrating for a game. I recommend another SA option in the DCS Options menu (similar to the selected A/G munition in the TID): having the ICLS channel displayed in the text box when it is changed, or alternately on a corner of the HSI display in ICLS mode).

I really do need the cts.dat file though. That's the only way I can troubleshoot the GUI/database. At this point, though, I won't get to it for another week. So you have some time to upload it.

It is more; you can also find this feature in the F-14 and P-47! Using S1 as a global VR Zoom for VR users is something that I have been retrofitting to the profile, and should be a global feature in CTS 3.0. VR users use S1 for VR zoom, and the normal S1 function is shifted instead. In this case, NWS is S3+S1 and canopy open/close is not mapped. In the controller references for each controller, you will find a section under each aircraft called "VR Substitutions" that shows any changes for VR users. I'll update the HTML though. Thanks for the heads-up on the graphic.

2.49 Hotfix 2 is up. The hotfix suppresses station change WAV when using TCPTM trimmer with helicopters.