Jump to content

Home Fries

Members
  • Posts

    3515
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by Home Fries

  1. Shift is S3 (or pinky button) on the stick. It's also the NWS/Reference button. S3 as shift is universal across all profiles. LANTIRN from RIO does not require the mod. You only need a mod to run LANTIRN from the pilot seat. You can either download the mod from the link below, or use the included controller mod (which also adds some functionality to the MFDs). https://www.digitalcombatsimulator.com/en/files/3303929/ The URL is also in the HTML documentation. I recommend reading at least the sections of the aircraft you intend to fly, as they explain many of the setups and combinations.
  2. Glad to hear it's working. Go ahead and run the CTS updater again to get the latest PDF.
  3. That's a good thing. It means that your axes are working in TARGET. Now somehow there's a disconnect in DCS. Dumb question, but you did load the F-16C diff.lua for both the Keyboard and HC, right?
  4. OK, I need you to open the device analyzer and check to see if you get the microstick on the Ry and Throttle axes (TARGET has a bug that remaps Rx to Slider1). BTW, most buttons are DirectX so they'll only be seen on the Device Analyzer (not the event tester). The F-16 profile uses an analog microstick, so in retrospect the message of unmapping the microstick was actually unmapping the digital commands in favor of analog axes. I was unable to reproduce this error on my end. My microstick showed Ry and Throttle in the Device Analyzer, and JOY_RY and JOY_SLIDER1 in DCS.
  5. Ok, Rum Runner, so to clarify the following: The Microstick X axis works oustide of TARGET You have CCP set up to match the axes in TARGET When you load CTS, it loads a digital microstick axis. So now the questions from me: What profile are you loading by default (i.e. which module)? When you load the Event Tester (the TARGET app that reports keystrokes), do you get ,./; (or something similar) reported from the microstick?
  6. Everyone, It appears the new versions of the PDF and some of the graphics didn't make it into the build. To get the latest files, run the CTS updater (normal update) and you should get the new PDF.
  7. Definitely start with the 24 pages in the PDF guide, and you don't need to read the appendices unless they relate to you. Of course, #2 of your questions may rate reading Appendix E. Check the Setup Guide for how to configure the Cougar Control Panel (CCP) and make sure it matches what you have. Does the microstick X axis still work outside of TARGET? If not, it could well be a hardware issue. I'm assuming you're using Windows 10. It sounds like it could be the Windows Store conflict addressed in Appendix E and this thread.
  8. That's a good question. A visual fix would be difficult because you would need to use the wheel at the exact time you're overflying the object (likely at low level). A TACAN fix would be easy enough to select the TACAN (pilot or RIO channel), but Jester would need to know which waypoint was for that TACAN. I suppose the pilot could choose the fix waypoints in both cases, and a TACAN fix would be easier to perform.
  9. Confirmed. Would like a logic check to see if the cover is open before actuating the "Admiral's Doorbell."
  10. Version 2.43 is released. It adds the JF-17 and MB339. Change Log: Added JF-17 and MB-339 (both WIP). Added ability to cycle Hat1 (POV/TrackIR/VR) functionality while in Profile Selection Mode. Added delay when switching stations for VR1 (Trim) users to prevent "trim roll" after station change. Added option to disable station switch with Hat1, as well as option to default to crew station other than "1." Added option to enable both Warthog Throttle and Cougar TQS in profile. Added option to remove DirectEntry from AV-8B and F/A-18C SnapViews. Removed SnapViews for VR users, and in some cases replaced with substitute functionality. M-2000C: Corrected HOTAS direction for keying UHF and V/UHF radios (now matches SRS). Improved radar controls on LMFD (Cougar). F-14: Added command to swap Jester/AIRIO with SRS ICS in RIO cockpit (similar to pilot function). Fixed Instrument and Console lighting dials at RIO station. Added TID Mode commands to HOTAS (RIO). F-16C: Added option for users with both Warthog Throttle and Cougar TQS to use the TQS (with WH base switches). Updated Comm Switch orientation to match SRS and the actual Jet (Comm1 aft, Comm2 fwd). AV-8B: Moved Dual MFCD Export macro from S1 Long to S3+H4P Long to free up Waypoint Increment for JDAM IL2GB: Added Dive Mode and Contact Altimeter Setting Updated Warthog Stick H4P to fire rockets (per the control diagram) Warthog: added Prop Feather to Left Idle when Combined Engine with RPM selected. Updated bindings since 2.42: UI Layer, M-2000C, MB-339, F-14 (RIO), F-16C, JF-17 Updated SnapViews since 2.42: Classic and Boresight (MB-339, M-2000C, JF-17) Updated Custom Luas since 2.42: none Known Issue: JF-17 Rudder Trim isn't currently working for VR users. This will be fixed globally in the next version. Note: The UI Layer is not just for VR anymore; it affects anyone who uses DCS in-game voice comms.
  11. All, I have put a 2.43 release candidate up for internal testing. I was hoping for a public release today, but there were so many changes to the JF-17 that I want to make sure I caught all of them before putting this out. Since there's also expected to be another hotfix tomorrow, I also want to make sure that 2.43 is fully compatible with the upcoming hotfix. I figured out a way to drop this in. You should have this, along with a couple of ways to select your desired station in profile selection, in 2.43.
  12. +1 Would also like to see bindings for external lighting switches and the HUD day/night and declutter switches.
  13. This might be worth reporting on the RAZBAM forum. You'll notice the other time we saw this was on another RAZBAM module (the AV-8B).
  14. Excellent point. I'll give it another round of testing.
  15. This is a possibility, and I have some thoughts on how to make it work. I'll add this to the bug tracker as a feature request. However, it will require a global change and I most likely won't be able to get to it until April or May. In the meantime, there are a couple of workarounds you can try: Be careful not to quickly tap the roll trim, being sure to use longer intervals between quick adjustments. Reduce the "Double Tap" value in CTS (under Global in the category Timing Values-TEMPO) so that your trim adjustments won't change the profile to RIO. Then you'll also want to be careful when going between switch extremes with the Boat Switch or Pinky Switch, as Double Tap also delays actuation of the center position for that very reason. Hope this helps,
  16. I'm not saying this is what's going on, but this is the only thing that makes sense right now: Make sure you load the CTS profile before you load DCS. If you ever load DCS without loading TARGET/CTS, don't enter the control options menu in DCS, and be sure to cancel out if you do. If it is red, it could be that the modifiers (JoyBtn30-JoyBtn32) need to be added again. The other possible issues are addressed in Appendix E of the Setup Guide PDF. Please let me know if one of these issues is the culprit. EDIT: Re-reading, the first issue in Appendix E could very well be the culprit. I'm still not sure exactly how to fix that.
  17. TARGET middleware (aka Thrustmaster FAST) isn't the most stable service in Windows. High CPU saturation can also cause a profile to crash, as can programming 2 LEDs at the same time. Still, I put up with it because of what I can do.
  18. @VC, I was about to post regarding plugging/unplugging the stick. I get this more than i should, despite having only 5 TM devices plugged into a 10 port powered hub. I think it's due to power draw, and it's just one of those things.
  19. Update on this issue: for dual seat aircraft with VR set to Trim (1), a short delay was introduced between when the trim is commanded and when the seat is swapped. Doing a "double-tap" of the hat switch and releasing the hat switch within the same interval between taps should be enough time to release the trim command before commanding the seat swap. I tested this on the F-14 and now it performs only a slight roll in the direction of trim, followed by "Iceman" autoleveling the aircraft. I think this is just how the F-14 module does things. This fix is currently in beta testing and barring any unwanted discoveries will be in the 2.43 release.
  20. +1. Elegant solution. The flip side would be having a "negative" checkbox with the switch being active if one or two buttons are not pressed. For example, if "Master Arm On" has the held checkbox, then "Master Arm Off" should enable the "negative" checkbox with the master arm on button selected.
  21. It's a brilliant marketing move. Those of us who are OCD and can't stand looking at a black and white Icon will purchase the modules so everything is in color. :D
  22. All those USN and USMC patches you see if you select a USA pilot were done by me and incorporated by ED a few years ago. So the answer is yes.
  23. Following up with your report, both MFDs are technically correct (though I'll italicise the high def N/STS). Depending on whether you have RMFD: Context Sensitive Bottom Row Buttons enabled in CTS, and whether the logical gear state is up or down, and the state of the parking brake determines the functionality of the bottom row of the RMFD (and especially the BRT rocker). There just isn't enough room on the MFD inserts to put all the combinations. What I did do is amplified the information in the HTML control guides and verified that the hyperlinked table is correct, so people can just click on the hyperlink to see the bottom row functionality.
  24. Just an update on the JF-17: In adding the Cougar TQS option for Warthog users, I uncovered some bugs that, while not showstoppers, have no business being in a release. Since the OB patch has been pushed to Dec 18, my plan is to squash these bugs, then when the OB is released with additional JF-17 keymappings, I will add the UFC to the LMFD and many of the switches to the WH throttle base. Those switches should be simple (for the time being at least), so I'm hoping to have 2.43 out on Dec 19. Unless there are changes in keymapping for other modules, 2.43 should also be backward compatible with the DCS Stable release.
  25. Concur with OP. While it is a realism abstraction, setting the laser code via kneeboard is now an established precedent that is consistent through other modules. I find the kneeboard method to be convenient, and the feature can still be disabled in the air.
×
×
  • Create New...