Jump to content

Home Fries

Members
  • Posts

    3515
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by Home Fries

  1. Could be. Please post your dcs_world.tmc file so I can review it.
  2. I know the pots are dead, but could you please try reattaching the cougar stick to the cougar base and running the profile with WarthogStick = 0? This will at least eliminate a variable, as your configuration is not one I can truly support. If the buttons work on the Cougar base, then at least we know it's the Warthog base/Cougar stick that is likely the issue.
  3. This is interesting (not in a good way). TG1 should return DX1, and S3+S5 (NWS) should generate LCTL+C (with DX30). What is normal is that Hats 3 and 4 do map to keyboard combinations. Hat 1 should map to mouse based on the VR selection you have, and TMS should map to DX7-10. The logfile says that you're using a Warthog stick with a Cougar throttle. Have you tried this with your Cougar stick, and not the warthog?
  4. I can answer the last question: yes! The modules are tied to your account, so you need only log into your account and the modules will be available for download (via the download manager) when you start DCS.
  5. TARGET natively only recognizes two MFDs. However, MFD3 will be recognized as a controller separate from the TARGET profile. Fortuitously, I have also created diff.lua files for a 3rd MFD for quite a few profiles in CTS, the Hornet being one of them.
  6. You can still run the installer, and just select either update when prompted. You won't connect to the server, but you will still complete the installation. Then download the previously linked zip files and extract them to your CTS folder. You should be good to go at that point. Glad it's working.
  7. Version 2.5.66 Uploaded for DCS 2.5.6.59398.
  8. 2.53 is up. Since you won't get text in the updater, here is the text for the update file (including the change log): Here is the link to download the files. If you already have 2.52, you can just download the new files from the 253 Update folder. EDIT: Just applied a hotfix for the F/A-18 diff.luas. Be sure to download the updated 2.53 CTShtml and CTSext files.
  9. The Logical Gear State must be Up (i.e. TARGET must think you have the gear up) for the mod to work. If you don't use S3+H3U/D Long to cycle the gear, holding S3+T6 Long should toggle the state for you. That said, it appears that the LANTIRN half-trigger setting isn't working properly on the Cougar. I'll have to look into that.
  10. I was able to do theta up using both of these commands. You may want to verify that you have the latest diff.luas applied (TARGET M2000C wh v246.diff.lua for the Warthog).
  11. Hi Guys, Sorry, still troubleshooting things on this end and busy with Real Life (TM), so I haven't had a chance to look at those issues yet. However, I did find one nasty bug with the P-47: I assigned the Gun Safety Switch Cover toggle to DX1, but didn't remove the DX1 assignment from the first stage trigger. This results in toggling the cover (and safeing the gun switch) when you go to shoot something. For now, remove the Joy_Btn01 mapping from the Gun Safety Switch toggle in your DCS Control options and cycle the cover manually. This will be fixed in the next version, if not a hotfix before then.
  12. Another reason for the control wipe is to ensure full range of movement, e.g. no Foreign Object Damage (FOD) in the control mechanisms. FOD is an ever-present hazard, and the time to determine that you don't have full range of control is not after you launch from a carrier deck at just above stall speed.
  13. Alright, everybody, here's an update: This internet issue is not fixing itself, and it will likely persist for at least another week. To get around this, I have made the 2.52 files directly downloadable on my cloud. Just download all zip files from box.com, extract them with folder structure intact into your CTS folder (the folder with CTSupdate.exe), then back up the zip files for good measure. If you're prompted to overwrite existing files, you're likely doing it right! Sorry for any inconvenience.
  14. The problem was a bit complex, but hopefully it gets itself sorted by the end of the week. This is also delaying my CTS for Windows release, so I'm anxious to get it taken care of. Compounding the issue is the updated forum software which apparently trashed the topics I was tracking (and also dorked up the hyperlink in my signature). Now I can look at the posts and reply accordingly. Thanks everybody for your patience.
  15. Buying on Steam and playing on Standalone gives you the most compatibility, putting it that way.
  16. Yes. Steam version will allow DLC purchased only on Steam. Standalone version will allow DLC purchased either on Steam or directly from ED.
  17. One thing about steam is that it auto-updates instead of checking for updates when you launch DCS. This can be good (convenient) or bad if you like to use mods and would like to control your updates. You can use the steam overlay in standalone DCS by adding DCS as a non-steam game, but it won't track your play like it would the native steam version. Also, to clarify, you can buy DCS modules on steam and play them on standalone by linking your steam account to your ED account. However, modules purchased directly from ED will not work on the steam version of DCS. Standalone gives you maximum flexibility in this matter. My personal opinion: the benefits of standalone outweigh the convenience of steam.
  18. Thanks. I was with CVW-8 just prior to that deployment, so my frame of reference was more with VF-213. I think 103 had the upgrade as well, though IIRC they were on home cycle during that timeframe (GW/CVW-17 got back in December 2000).
  19. Hi everybody, and Happy Thanksgiving! Apologies for being radio silent the past week. My internet has been unreliable (putting it charitably), and this has undoubtedly affected the ability for you to update CTS. I am currently on travel (which is why I currently have reliable internet), so I am unable to properly troubleshoot issues. @trigen have you tried performing a "full update" rather than a "normal update?" A full update will force-download all files, which may help if my internet caused issues while the WAV file was downloading. A corrupt zipfile is the only reason I can see for the error you received. I would be suspicious of the uploaded zipfile itself, except the WAV zipfile is not a file I changed in the latest update. As far as the throttle goes, you can reverse the axis by selecting "Axis Tuning" in DCS Options. That may be your best bet for now. @tomeye Those assignments are the plan for now, though I was really just trying to fix something that was broken. The way it's set is up for radio, down for ICS, and push for discord. I will have completely new DX assignements for 3.0 when that finally lands. @Wikkus I'll have to troubleshoot when I get back.
  20. Nicely done! :thumbup:
  21. You're welcome! In other news, 2.52 is uploaded. Change Log: Fixed Commstate issue with T4/T5 not mapping (Cougar). A-10C: Added flashlight to S3+LOSB02 Long. AJS37: Added NVGs (toggle on S3+LOSB02). UH-1: Reassigned RPM Gov to deconflict with VAICOM/SRS F-14: Added Emergency Wing Sweep to Warthog (Custom LUA required) Added Asym Limiter to Warthog and LMFD Added Left/Right Engine Fire Suppression systems to MFDs (Handles require custom LUA). Switched ICS and TACAN CMD OSBs, added TF-30 Mid-Compression Bypass Circuit Breaker to LMFD. Updated Diff Luas: F-14, AJS-37, A-10C, UH-1 Updated Custom Luas: F-14
  22. I use both VA and VAICOM with CTS, so I highly recommend it. I try to integrate as much as possible, but keep in mind that 1) the profile was built before VAICOM/SRS were around, and 2) when I integrated VAICOM/SRS, I didn't have a lot of free time so I did what I could rather than completely rebuild from the ground up. As such, some of the older modules have some issues when I would use DX20-23 for functions other than radios. I've tried to get this removed as much as possible, but I"m sure things persist. Note that this wasn't the issue with the Mirage; rather it was simply the use of a MapKey command when I should have used MapKeyR. I use a separate mapping routine for the Cougar, and since I don't have the time to test it as much as the Warthog I depend more on others to report issues for the Cougar. Version 3.0 will be built from the ground up with dedicated DX for VAICOM/SRS/Discord and (as much as possible) dedicated DX commands specific to each button on the stick, throttles, and MFDs. The goal is to reduce the number of modifiers in use for each function and to reduce the number of key macros required for each profile. This should in turn reduce the required stack space taken by the DCS profile, allowing for more modules in the future before running into the same wall.
  23. Setting the shutdown delay to 0 disables the routine. Set it to 1 (as in 1 ms) to make it near-instantaneous. Also, to be clear, you are using the HC diff.lua (for the Cougar), right? If you use a mixed HOTAS, base your diff.lua on the throttle.
  24. You can startup/shutdown by holding S3 while moving the TQS across the idle detent. To shut down, you need to hold S3 and keep the throttle behind idle for 5 seconds. I tested the throttle axis using the TARGET F16C HC v249.diff.lua file. I couldn't duplicate the inverted axis, but if it persists just invert the axis in the DCS settings. There are no curves for the Cougar TQS so that shouldn't cause any issues.
×
×
  • Create New...