Jump to content

Home Fries

Members
  • Posts

    3515
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by Home Fries

  1. Any headway on this bug?
  2. Folks, just an update on things: When I had a free moment during the trial, I started to build simple profiles for the Christen Eagle II and the Yak-52. Compiling started to give me full stack errors, and further analysis leads me to the conclusion that my code is approaching the limits of what TARGET can handle in a single script. I am abandoning the dedicated CE2/Yak52 profiles, as they work just fine with a customized DirectX profile. My focus will be on combat modules. While I ceased support of the Hawk a while ago, it is currently available to select in the script for people who wish to use an earlier version of DCS World. Starting in 2.45, the Hawk will be completely removed in order to free up resources for future improvements. People who want to use the Hawk profile will need to use CTS Legacy for DCS 1.5.8. Eventually, I will need to remove the non-DCS profiles from the script and make them their own script. This is a longer term issue because I will need to build a new infrastructure for a separate CTS-based script. However, this should at least get us through the P-47 and Mi-24. After that, I'm open to suggestions...
  3. If you have TrackIR enabled then the hat switch should default to trim. It will only revert to POV when TrackIR is paused using the HOTAS. I'm not sure what the issue is, but please post your hardware and your dcs_world.tmc for analysis. Don't count on much customization beyond stuff that is in the database. There are often dependencies with switches and keystrokes, so it's often not a 1:1 relationship with keymappings. For those switches, the in-game commands move the switch in a direction instead of to a discrete setting. This allows the profile to get out of sync with the game. You can either click the switches to match the logical state of the switch with the profile, or you can hold S3 and press the rocker switches to put match the logical switch position to the in-game position without actually pressing keystrokes.
  4. There is a CMS Z button in the Options menu, and the CMS Push button is properly mapped. I tested it SAT with the diff.lua updated for version 2.44. I would make sure your diff.luas are set properly.
  5. Your DCS_World.tmc file is a blank template, except for the values designated as constants. The only thing I can think of is a corrupt database. In your CTS folder, then backup and delete the CTS.dat file (not CTSn.dat). Then run CTS again and rebuild the user database.
  6. Go to the Values tab in CTS and select Head Tracking Options from the Global category. Make sure there is a value for "Default POV Hat function in VR." My guess is that it was accidentally deleted, in which case you can press the Def button to set the default value, or you can manually enter 0 or 1 depending on your preference.
  7. 2.44 Hotfix 2 is up. Hotfix 2 is only for DCS 2.5.6.47224, and it fixes some diff.lua mappings for the F-14 and F-16 and updates the lua controller mods for the F-14 and M-2000C. Not for use with the Stable version of DCS.
  8. Ok, reason I asked is that it couldn't find a value that should be part of a generated DCS_World.tmc. Please try rebuilding the file, then if that doesn't work please upload your DCS_World.tmc file so I can review it.
  9. You did build a profile, right? You need to create your own DCS_World.tmc using the CTS GUI.
  10. Much appreciated! Thanks for the bug report as well.
  11. Uninstalled and reinstalled all TM drivers, including TARGET (and disconnecting devices before reinstalling TARGET). Same issue.
  12. Thanks for the link. DIView is pretty slick, and while it doesn't show the inputs from the original controller (only the virtual), it should be a good workaround. Next step is TM tech support when I get an opportunity. But this virus thing has me working like a dog...
  13. I recently bit the bullet and updated to Windows 10 on my gaming rig. Now my TARGET Device Analyzer only shows a maximum of two selectable controllers no matter how many times I Enumerate Devices. It will show my MS SWFFB2 and the first Thrustmaster controller (I have six TM controllers, up to 5 I use in a TARGET profile at any one time). For example, it will show the HOTAS Cougar, and when I unplug the Cougar it will then display my Warthog Throttle. Plugging the Cougar back in will replace the Throttle with the Cougar. I have uninstalled and reinstalled TARGET, rebooting both times. I have tried with and without the Windows Store disabled. FWIW, I can see all of the controllers in the TARGET GUI program, just not the Device Analyzer. Since the Device Analyzer is my primary tool for testing my CTS profile, this is a big deal. Thanks in advance for any help. -HF
  14. If I'm a single RIO (i.e. no wingman or single seat wingman with no human RIO) I'll often reduce my scan width and increase the scan bars, then cheat my azimuth toward the threat axis or the air picture if the datalink is good. It is intuitively easier to scan azimuth than it is to scan elevation. I do like the RWS until you get contacts, then convert to TWS technique as well. I'll go to PD Search if there's a known target at long range that I have cueing on (e.g. datalink), because then I can pay attention to the DDD if I know where I'm looking and what I'm looking for. Finally, Pulse search for slow targets like helos. You can pick them out of the ground clutter, but it's as much art as science.
  15. DTC did it for me as well! Thanks!
  16. 2.44 Hotfix 1 is up. Hotfix 1 addresses changes in the Axis Warbirds and the M-2000C default.lua change in DCS 2.5.6.45915, and fixes airbrake assignment on the JF-17 if TQS is selected with both Cougar and Warthog hardware available.
  17. https://forums.eagle.ru/showpost.php?p=3751441&postcount=1 Bottom line: it is possible by linking your Steam account to your ED account.
  18. We were noticing the same thing. Despite attaching to the shuttle and having the JBD come up, we're more often than not unable to launch using the Salute command. One of my VS mates believes that the jet doesn't kneel all the way anymore. I can't confirm this, but figured it might be worth a datapoint for investigation.
  19. D'oh! :doh: I forgot about the batch file, despite mentioning it a few posts up. Manually updating the path in your batch file should fix your issue.
  20. The CTS executable is hard-coded to use the default TARGET folder. If you used AppMover, I recommend placing a Symlink to the new TARGET folder at the location of the default folder.
  21. Shift mode is sustained, not toggled. You need to hold down S3 to use a shifted command. Releasing S3 reverts to default mappings.
  22. Not at all. S3 will always enter shift mode, but a quick tap will toggle FOV.
×
×
  • Create New...