Jump to content

Home Fries

Members
  • Posts

    3515
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by Home Fries

  1. I compared the controller mod with the latest default.lua, and while there are differences in the keyboard file there wasn't anything different about hiding the stick or kneeling the aircraft. I'll try to test it tomorrow or the next day. In the meantime, I updated the default.lua to account for the new toggle functions; this will be out in 2.44.
  2. I should be able to do the comparison when I get home from work.
  3. Nice catch on the Walkman. Fixed internally and will be in the next release. I couldn't find an issue with the Joy_BTN5. Joy_BTN30+Joy_BTN5 shows in the Thrustmaster Combined column for both Cougar and Warthog, and the control map in the Options menu is responsive when the stick is pressed. I have not had an opportunity to test it in the sim itself.
  4. That's exactly it. Even though the F-14 speedbrake isn't on an analog axis, by "analog" I mean that it can be stopped midway through its travel as opposed to being either all out or all in like the Mirage 2000C. When you can stop the brake like this, you need two separate buttons to allow for this flexibility, as opposed to just having the brake open until the switch is released (i.e. the "binary-momentary" routine I have in the script), which is what the Mirage defaults to. The Tomcat is set to the "analog-momentary" brake type.
  5. Since the F-14 uses an analog airbrake, I can't do that.
  6. Along the same lines, bindings for the searchlight and landing light appear to be mixed up. They show up properly in the Options menu (e.g. the keystrokes actuate the proper commands in the Options menu), but in-game they appear to be mixed up. For example, Landing Light Extend works, as does Retract, but Landing Light Stop actually stops the Searchlight. Similarly, the Extend Searchlight command appears to work, but the Searchlight Stop and Retract commands appear to work on the landing light instead. Note that I tested this using keystrokes from my HOTAS profile without changing any Huey bindings since probably before DCS 1.5.
  7. The Warthog profile doesn't use the Rudder axis, so anytime you see RZ on the Warthog diff.lua it's for VR. Since VR has no use for the analog zoom I normally map to the friction lever, I remap RZ for VR users then apply it to a custom command as required. In this case, VR RIOs can use the friction lever to adjust the HCU thumbwheel. Throttle axes are not used for RIO, though the HOTAS controls are.
  8. I would love to add the external lighting switches (e.g. nav/form lights, anticollision lights) to my Warthog base, and I'm wondering if these bindings are on the radar and if so, what is the ETA to get them into the game.
  9. Request: Bindings for external lighting controls on right panel I would love to add the external lighting switches (e.g. nav/form lights, anticollision lights) to my Warthog base, and I'm wondering if these bindings are on the radar and if so, what is the ETA to get them into the game.
  10. Hotfix is up. Includes diff.lua fixes for the Su-25A/T, Su-27, and A-10A.
  11. Fixed. I'll check the other FC3 modules and release a hotfix. Thanks for the report. :thumbup:
  12. I haven't updated it for 2.5.6 yet. It's on my list of things to do, but it probably won't be for another few weeks.
  13. If you deactivated your SF in the release version, it will apply to all SF versions on your system (e.g. legacy 1.5 as well as pre-2.5.6 beta). Activations are for the module (not the DCS version) at the registry level. So you haven't lost an activation.
  14. Was able to implement it last night. Looks like as long as the guard is up, the emergency throttle is unused and returns to neutral after the guard is replaced. I just wish there was a set of keystrokes to cycle the guard, but at least the axis will be mapped.
  15. I like the idea, but I haven’t had time to look into it further. Hopefully I can look at it next week.
  16. Fixed the MiG-21 bug, and I've isolated the A-10C LGAIN issue. 2.43b (Hotfix 2) is out.
  17. I’m not sure when I’ll get to this, but it will be hopefully in two weeks (literally, not figuratively). In the meantime, for anybody who posts a bug, please indicate whether use the cougar or warthog, whether you use TrackIR, VR, or POV, and anything else such as SRS and VAICOM.
  18. Thanks for the heads-up. I'll take a look at these hopefully sometime next week.
  19. Here’s the big thing with VAICOM: it doesn’t just listen to your voice and then press the proper function keys in sequence. It integrates with he import/export functionality of DCS to skip the comms menu entirely and even allows use of in-mission callsigns, airfields, etc. If easy comms are used, saying “sukhumi inbound for landing” will also change your radio frequency to Sukhumi. For single player it really is a paradigm change.
  20. You can disable TERNAV using the CK37. I know it’s an extra step and not ideal (and I don’t remember the code off the top of my head), but the option is there.
  21. It is possible to have your cake and eat it too. I don't use TUSBA, but I do have both Cougar and Warthog HOTAS controllers hooked up. If I set Warthog Throttle = 2 in CTS, the profile will incorporate both the Cougar and Warthog controllers into TARGET. This way you could use the TQS for the F-16 or JF-17 and the Warthog Throttle for the twin-engine jets. In this configuration, you would use the Warthog stick for your controller either way, and you would keep your Cougar stick connected, but out of the way. The only thing you really can't do is use both throttles at the same time (though you can use the switches on the Warthog base) because Windows limits a single controller (e.g. Thrustmaster Combined) to eight axes. EDIT: if you want the same functionality as TUSBA, you can still plug in your HOTAS Cougar and set Warthog Stick = 1 and Warthog Throttle = 1 in CTS. Then the profile will exclude the Cougar from TARGET, allowing you to use the axes as a separate controller. Again, you could remove the JoyX and JoyY axes from your controller profile and stick to the TQS as a separate controller. Then just keep your Cougar stick connected, but out of the way.
  22. Once you're in TWS Manual, the antenna elevation is usually the thing that trips most people up. There are two possible TWS scan settings: 40 degree/2 bar and 20 degree/4 bar, set with the azimuth switch (the bars are automatic). If I have a working datalink I usually use 20/4, center the cone on the datalink contacts, then work the antenna elevation to keep the contacts in the middle of the altitude band. If you can see datalink contacts but don't have them on radar, the antenna elevation should be the first thing you should check.
  23. I won't be able to look at this until February, but I'll get back to you as soon as I can.
×
×
  • Create New...