Jump to content

Home Fries

Members
 View Profile  See their activity

  • Posts

    3515

  • Joined

  • Last visited

  • Days Won

    1

 Content Type 

Everything posted by Home Fries

  1. Home Fries
    2.47 Hotfix 1 is up. Hotfix 1 addresses compatibility with the AV-8B in the DCS 2.5.6.50979 patch. Updated bindings: AV-8B Updated Custom Lua: AV-8B
  2. Home Fries
    In what can only be described as a serendipitous coincidence, the now released CTS v2.47 includes the P-47 Thunderbolt! Other changes: A-10C: Fixed NVG button assignments. A-4E: Updated for version 1.4 AV-8B: Removed Engine RPM LEDs (Warthog) Known Issues: This script is now very close to stack limits, which is why I've had to remove deprecated routines. If you receive a full stack error, report it ASAP. Please include the text log. P-47 gun safety switch toggle does not work properly (module side issue). H2U is set to the Gun Arm discrete command for the time being. Closing the switch cover will switch off the gun safety switch. Updated bindings since 2.46a: P-47, P-51, A-10C, A-4E Updated SnapViews since 2.46: Boresight (P-47) Updated Custom Luas since 2.46: none Note: due to the stack limits, this is likely going to be the last major release for a while. Stay tuned for a CTS 3.0 development update.
  3. Home Fries
    Excellent catch. I missed those changes. Updated for the next build.
  4. Home Fries
    I got DX+ working, and I know you can call a TMH file (including a modified target.tmh) from a folder other than TARGET/Scripts. In fact, I call DX+.tmh from my CTS/Common folder. I haven't tried calling the DevCfg files though (which I assume is most important in getting the CMFD to work). If I could call these from a different folder I would put this into my CTS profile in a heartbeat. Code for the TMH from a relative folder is easy: include "Common/dx+.tmh" Do you know if it's possible to call the DevCfg files from a different folder (ideally a relative path from the script itself)?
  5. Home Fries
    I am hard at work on a P-47 profile, and I think you guys will really like it. Alamo is on the right track - it is based very heavily on the P-51 profile (with some nice twists though ;) ).
  6. Home Fries
    One of the things on my list is to completely rebuild the comms routine to support VAICOM, SRS, and TS3/Discord from the ground up. I'll have to get back to you all when I can start on this (probably sometime in August).
  7. Home Fries
    This is great stuff, RogueSqdn! Mind if I include it in my public TARGET script? I'll give you credit.
  8. Home Fries
    With the sandbox approach DCS takes, I have no problems with modern airfields, or at least fictional period airfields that can handle modern jets. I wouldn't mind having fake TACAN/ILS/NDB/PMRG at airfields either. The important thing is that any deviations of this sort should be removable in the Mission Editor to allow maximum accuracy with WW2 scenarios.
  9. Home Fries
    Thanks! Looks like ED changed the Mat Names on the numbers as well; I didn't catch that before. Hence the "apparently" in my quoted statement...
  10. Home Fries
    I don't have the P-47 yet, but if people are interested in a quick turnaround on a profile I do accept donations toward purchasing the module. Please PM me if you're interested. FWIW it would probably be somewhere between the P-51 profile and the IL-2 profile which has a digital RPM controller. If you're getting a keyboard command, make sure you set "TeamSpeak/Voice Chat Hotkey as DirectX" to 1. That should free up Button 20 for you. As for the pulse, if you have SRS set to 1, it should sustain rather than pulse. I'll double check the Cougar code.
  11. Home Fries
    The very nature of TARGET means that my code is shared! I'll look into it.
  12. Home Fries
    Problem with breaking the code that way is that I'll have to do twice the work, or I'll have to develop one, then port it (which will be a configuration management nightmare with updates). However, if I can figure out a way to alias &Joystick and &HCougar, I could have over 90% of the stick solution with one code base. I'd still have to do the throttles individually but that isn't a big deal. I'm thinking three things are going to happen, and sooner than later (though I need a big block of uninterrupted time to make it work). First, I'll tweak the communications routines. I have completely separate routines for Cougar and Warthog because I ported the Warthog later and I wanted to be able to compare the code side by side. I could combine much of that and use the same variables, and I will need to streamline the comms code. This means that the PTT Common option will go away (this is obsolete since SRS became the game standard anyway). That will reduce the permutations in the comms. options (especially true in the Cougar routine). Next, I'll stop programming for every single option and start programming for a common denominator (or series of popular options). This is where I could use your input on what you all use and what you don't care about. Next, I'll start globalizing as much as I can, particularly with MFDs. Right now there is a convention, but each module library has its own MFD routine. Globalizing the MFDs and then calling individual routines to re-assign differences is less efficient programming, but may reduce the stack overhead. Finally, I'll move the non-DCS programs like IL-2 and Elite Dangerous to a separate profile. I'll ideally want to update the CTS EXE to have a new GUI and call different files, but nothing else needs to change. I welcome any other inputs or suggestions
  13. Home Fries
    Ok, I'll try to duplicate with the Cougar.
  14. Home Fries
    Fellas, I'm glad we're having this conversation. I started this profile years ago for the Cougar when the only modules were the A-10C, Ka-50, and FC3 (then the P-51 shortly after). The baseline was the A-10C and the only voice solutions were TS3 and the TS3-based TARS (a spiritual predecessor to SRS). Since then I have modified the code to include the Warthog and then two years ago I changed VAC/TARS support to VAICOM/SRS. Now that I'm very close to the stack limit that TARGET can handle, I will need to revamp my comms code again to streamline it. I have already tried to make the Warthog Mic Switch as standardized as possible, but I'm not sure I'll be able to do the same level of standardization with the Cougar without sacrificing some functionality. Here's what I try to do with comms: Single Radio: T1 (Cougar) or MSD (Warthog). MSU/MSP for TS3/Discord (often shared with T1 for Cougar, but sometimes T3 Up). Dual Radio: T4/T5 (Cougar Left/Right) or MSR/L (Warthog). MSU/P TS3/Discord (T3 for Cougar). Three Radios: T2/4/5 (Cougar) or MSR/L/D (Warthog). Again, MSU/P or T3 for TS3/Discord. I changed the helos to match their HOTAS (trigger is normal for helos, except for the Ka-50 which uses the pickle button), but you should always get MSP for TS3/Discord. I also changed the F-16 to do Up/Down on the TQS, which matches the actual F-16.
  15. Home Fries
    I have reserved DX20-23 to comms, and in doing so have even remapped the combinations that use these commands (such as the MFDs). However, not all modules use all commands because not all modules have three discrete radio buttons. I have tried to match the layout of the source aircraft as closely as possible. This is why for helicopters you normally have a single comm button (usually the trigger) and you select the radio. It's also why the MiG-21, P-51, and other single-radio aircraft use one comm button instead of three buttons. SRS and VAICOM both support this.
  16. Home Fries
    2.46a (Hotfix 1) is up. It fixes the UH-1 Cargo Hook/Unhook as well as the F-14 LANTIRN H4P bug. Note: the database was updated, so be sure to rebuild your profile.
  17. Home Fries
    Do you think hook would be better as TEMPO Long and Unhook as TEMPO Short?
  18. Home Fries
    Page 17 of the Setup Guide PDF starts the specific VAICOM configuration instructions. If I"m missing something or they need to be more clear, please let me know.
  19. Home Fries
    This is by design with the Huey. Trigger does the radio selected with the radio selector, and TX4 should activate the selected radio.
  20. Home Fries
    Ok, I think since the Huey doesn't use landing gear I can assign a tempo to the paddle switch. However, I need to know exactly how sling loading works since it's been a while and my knowledge is obsolete. Do I need to have a short for hook and long for pilot unhook, or is autounhook sufficient? Which is preferable, and how does autounhook work?
  21. Home Fries
    Sounds like you have it set up correctly, but I can't duplicate the error. With exception of the Slew axes, all LANTIRN commands are keyboard commands without the JoyBtn30 modifier. I did find a bug with H4P reverting from BHOT/WHOT to DLC, but this can be worked-around by using H4R instead. I was able to use all S4 commands as well as laser latch and the trigger settings. BTW, your keyboard layout looks okay from what I can see as well. I'm assuming you're using both Warthog Stick and Throttle, and not the Hornet stick.
  22. Home Fries
    Version 2.5.61 is available for DCS 2.5.6.49798
  23. Home Fries
    To clarify, I like the idea that is being implemented with the custom borts. I would love more options and the ability to apply the number of digits I would like. I would just like to be able to do it with custom bort textures and have the alpha channel work as advertised.
  24. Home Fries
    I could also be wrong. It has been quite some time since I did any sling-loading, and back then it was normally using CTLD because the in-game sling loading was borked. The paddle switch (or at least the pinkie button on the actual stick) is supposed to be for emergency unhook, but I felt the "normal" toggle was the way to go. If the controls have been changed since then (a very distinct possibility), what would you recommend the mapping to be. Also, have they mapped the ability to extend or retract the cable yet (supposed to be the hat switch)?
  25. Home Fries
    Saluting with the left hand is authorized if the right hand is engaged. In the case of being on Cat 1, a left handed salute is more easily seen by the Shooter who is to the pilot's left side. CV NATOPS does not specify how to salute (e.g. hand toward the shooter), so there is some leeway for interpretation. Now whether this is done on a regular basis is up for debate. My sample size is limited and 20 years obsolete...
×
×
  • Create New...