Search the Community

UPDATE: Version 2.72 is available. The new installer now points to the new webhost. Special thanks go out to the Virtual Armed Forces for hosting CTS on their website. Hosting by the VAF is a significant improvement in uninterrupted service and consistency. Please check out the Virtual Armed Forces for an outstanding PvE multiplayer experience! You can also check out the VAF in the Air Combat Sim podcast #42. If you don't wish to do a fresh install, you can replace the top line of your CTS\DB\version.txt with the following entry: http://cts.virtualarmedforces.com/CTS/DCS/CTSversion.txt You may also download the new installer, or simply download and replace the updated version.txt below (note, this does not work for the CTS Legacy version; you'll need the installer for that). Special thanks to Tercio Sampaio for developing the GUI. If you wish to donate for this program, please send any donations to Fisher House, a charity that supports wounded veterans and their families. Exception: if you want me to program for a module or hardware I don't have, please PM me and we can discuss it. DCS World TARGET Script for Thrustmaster Cougar or Warthog and MFDs is now available. Download it from: Eagle Dynamics User Files Box.com This file is an installer which will install and launch the updater, which will then download the latest version of the script. You can also periodically run the updater to keep your script up to date. This script for the HOTAS Cougar/Warthog and Cougar MFDs includes dedicated profiles for the following aircraft: A-10C Warthog AV-8B N/A Harrier II AH-64D Apache Ka-50 Black Shark P-47D Thunderbolt P-51D Mustang UH-1H Huey Mi-8 Hip Mi-24P Hind F-86 Sabre Fw-190A8/D9 Bf-109K-4 Kurfürst MiG-21bis Fishbed MiG-15bis M-2000C SA-342 Gazelle L-39 Albatross F-5E Tiger II Spitfire LF Mk. IX Mosquito FB Mk. VI AJS-37 Viggen C-101 F-14 Tomcat F-15E Strike Eagle F-16C Viper JF-17 Thunder F/A-18C Hornet MiG-19 Farmer I-16 Ishak A-4E Skyhawk T-45 Goshawk Combined Arms Flaming Cliffs 3 The script is fully implemented with both code and custom keyboard and joystick LUA files. The included "Standard DirectX" profile can me used to create a versatile profile for anything else. This script uses TARGET, so you need to install it (though Cougar users can leave Foxy where it is). I also recommend the latest MFD Drivers, as I have found fewer profile crashes with these enabled. The script offers the following features: Graphical User Interface (GUI) to save your settings and auto-generate script files. Both HOTAS Cougar and Warthog Compatibility with F/A-18 Grip Support for selected modules. All documentation (except for the Setup Guide) is in HTML with context-sensitive help in the GUI. CommState routine allows for the selection of F1 through F12 keys with Hats 2-4 while the MIC switch is pressed Hot-selectable “TriggerZoom” allows you to zoom into your target or HUD when depressing the first trigger stage LED indications for airbrake, landing gear, TriggerZoom, CommState, and Teamspeak3 PTT Compatible with TouchControl (formerly TouchIR), VAICOM Pro, DCS Simpleradio Standalone, and all major VoIP solutions Optimized for TrackIR, but compatible VR or with Hat1 as POV Individual HOTAS profiles are mapped as closely to their real world counterparts as practical Flaming Cliffs 3 (FC3) HOTAS mappings correlate to the A-10C (attack aircraft) or F-16C (fighters) as closely as practical FC3 Context Sensitive Autopilot routine that reverts to last used mode on toggle A-10C Profile includes direct entry for CDU, CMSP, and UFC Ka-50 Profile allows direct entry for ABRIS (RMFD) and Rubicon Datapad Ability to automatically pause TrackIR while at the Door Gunner Station (UH-1) Context sensitive communications menus based on crew station (framework in place for DCS implementation) TARGET based Central Position Trimmer Mode that greatly improves upon the default trimmers when not using force feedback. Analog and digital differential braking routines, including paddle braking and nosewheel steering. Kneeboard mapping for all aircraft. NVGs for all capable aircraft, including "bonus" mapping for the A-10A, Su-25, Su-25T, and F-86 (H/T Zaelu). AWACS Mode for LotATC and SRS users. Simplified hot-selection of aircraft allows for potentially thousands of aircraft and variants in this script, along with audible feedback of aircraft selected. Screenshots are in the following post. I look forward to your feedback; any information that will help me improve this profile is greatly appreciated. To this end, there is now a public bugtracker for CTS. See the HTML documentation for instructions on how to submit a bug report or feature request. version.txt

Hi, since 2.7.7 I am having issues working with pilot - gunner logic. I ask Petrovich to look at an area where I expect a column of 3xIVFs. He looks there and locks up IFV without asking - no target list to select IFV 1, 2 or 3. Once target is locked I get constant launch tone although I am not aligned at all. In the track I overfly the target to present how the launch tone is constantly present without valid shot conditions. Maybe I am doing it wrong now? Thanks. Track is for Marianas map. BUG CHECK.trk

Hello! I'm looking for inspiration for realistic ground targets for ground attack missions. Are there any lists, reports or other documents detailing ground targets of for example the Gulf War, especially those targets hit in Baghdad on the first night, or, if unavailable for the Gulf war, the Vietnam war or the Korean war? Photos, plans and drawings of military installations such as depots, communications centers, bunkers, AAA batteries, formations etc etc would also be greatly appreciated! Thanks!

Hello, could someone please shed a light on the purpose and usage of the WYPT ID setting in a JDAM profile in the DSMS? Haven't found this in the manual or Chuck's Guide or anywhere. These are always describing dropping JDAMS on SPI using markpoints or something like this where the current steerpoint is SPI and in CCRP mode target and release information are based on that SPI. So how can the profile TARGET / WYPT ID setting be used? I tried yesterday and I can input a waypoint ID via scratchpad. But in flight to get proper ASL information I also have to set this waypoint as steerpoint. Maybe I did something wrong or missed a step on the usage? If I need to set the steerpoint to the same waypoint than there seems to be no further benefit of setting a target WP within the dsms jdam profile. Regards Jens

So this was driving me insane... one of my MFD 's would consistently disappear... but, I couldn't find the conditions under which it would disappear, I thought I had a cabling problem ... nope... I thought it was that the script I was using to create 128 buttons in TARGET... nope etc... A little about my controller set up: Thrustmaster Warthog HOTAS which I configure using TARGET, to get a full 128 buttons MFG Crosswinds v2 3 x Thrustmaster Cougar MFD 1 x Razer Tartus (configured as a joystick button box, because I prefer discrete DX button presses, as it creates less confusion keyboard collisions etc) 1 x Stream deck (configured as a joystick button box, using vjoy, because I prefer discrete DX button presses, as it creates less confusion keyboard collisions etc) I obviously turned of vjoy first and thought that fixed it but then in game, nope it would not work, re scanned device etc... nope still nothing ... I start looking into the Game Controller UI in desperation. Clue 1 I noticed that my MFD2 wouldn't configure correctly via the Game controller UI (even though it would still work in game) it would just show as a joystick, but, labelled as the Tartus so I pulled each of the controllers in turn, until i got it up as MFD... turned out it was the Tartus Resolution 1 I changed the MFD from MFD 2 to MFD 4 (luck more than logic) in the Game Controller UI, with the Tartus unplugged, each MFD number has a different VID in windows, so i guessed it was colliding. Each MFD now showed up correctly as an MFD the the Game controller UI. I ran Target and low there were still three MFD's hurrah ... or so i thought... I get into game and the MFD3 has gone AGAIN... some muttering (well swearing) what the hell is going on. Clue 2 why the hell do i have VIVE controller listed in DCS. 2nd order diagnostics (when does the MFD vanish) ... after many stages of testing it MFD3 only vanishes once Steam VR starts only when i have one or more hand controllers active (assumption what if to do the game controller mapping in SteamVR they are mapping the controllers to a VID that just happens to have collided with the MFD, as the newer device they would overwrite the existing device and the MFD vanishes, only if you run TARGET Resolution 2 Change MFD 3 to MFD 8 to see if that works it does hurrah Are we nearly there yet... no we bloody aren't Turn back on vjoy that works, turn back on the tartus and OFFS the configuration of the MFD4 via the Game Controller UI has c*cked up again... note the device works in game but FFS I won't less this beat me... Resolution 3 Turn the Tartus off Move the MFD to 7 because that is next to 8 that will be safe right ... wrong ... well 5 is next to 4 ... wrong ... 6 hurrah! Finally Left MFD1 is fine, my Right MFD is set to MFD6 in the UI, and the Center to MFD 8... conclusion getting multiple MFD's to work with multiple joystick devices is a complete pain in the bottom, and it would be really nice if the manufacturers would use a mechanism of ensuring their virtual joysticks dont collide with each other...

Hello, Not sure wether I should post it here or in the "objects" section. We made a mission where several bridges were the main targets. Planning accordingly to expert's advices regarding this type of target (e.g: https://www.airforcemag.com/article/1293bridge ), we aimed at the abutment with a 2000 lbs GBU-10, on DLY1. Direct hits on those abutments made no visible damage, but a bomb hole was visible below the bridge. For the second runs, we went for an INST fuse, and this resulted into a visible destruction of the bridge, while it should have made a crater on the pavement. The question is: - can you detail how a (large) bridge is modelled, so that we can do advanced targeting on it? - more generally, where can we find details about target models (buildings, bunkers, hangars, etc...) in order to make some basic weaponeering? - bonus: is it normal that only the PWY III with a BLU-109 is available on the F-18C (sorry for that, I did not find the answer)? If needed, the .trk file of that mission can be provided. Thanks!

Greetings chaps and chapeses, I'm creating this thread rather to share info about my struggle with HOTAS Warthog joy setup with T.A.R.G.E.T script editor and primarily to share the solution/workaround I found to work for me. I'd appreciate if someone more insightful explained/confirmed the reason for such behavior. My HW: HOTAS Warthog Throttle HOTAS Warthog Magnetic Base HOTAS Warthog F/A-18 Grip (? is this problem F/A-18 Grip specific ?) My T.A.R.G.E.T + HOTAS Warthog setup procedure: clean win10 install install HOTAS Warthog drivers (devices plugged first time after shut down system | unplug devices | - reboot probably unnecessary boot system | install target plug devices run script The problem: Running basic or advanced GUI profile works without problem, but running script from GUI or Script Editor either did not see the Warthog Joystick at all or generated the following error: Running script: C:\T.A.R.G.E.T\marbe's_profiler.tmc *** Allocated ProcInstances found from the previous run: use FreeProcInstance() *** Mapped plugin module "C:\Program Files (x86)\Thrustmaster\TARGET\Plugins\sys.dll" Compile Succeeded. Physical USB HID devices managed by script! Currently plugged USB HID devices[2]: 1: "Joystick - HOTAS Warthog" - "USB\VID_044F&PID_0402&REV_0100" 2: "Throttle - HOTAS Warthog" - "USB\VID_044F&PID_0404&REV_0100" USB HID device "Throttle - HOTAS Warthog"(USB\VID_044F&PID_0404\6&E264243&0&1) selected USB HID device with hardware id "VID_044F&PID_0402" cannot be found USB HID device "Joystick - HOTAS Warthog"(USB\VID_044F&PID_0402\5&357A1272&0&9) selected USB HID device with hardware id "VID_044F&PID_b351" cannot be found USB HID device with hardware id "VID_044F&PID_b352" cannot be found USB HID device with hardware id "VID_044F&PID_0400" cannot be found USB HID device with hardware id "VID_044F&PID_B10A" cannot be found USB HID device with hardware id "VID_044F&PID_B10B" cannot be found USB HID device with hardware id "VID_044F&PID_B687" cannot be found USB HID device with hardware id "VID_044F&PID_B679" cannot be found USB HID device with hardware id "VID_044F&PID_B68F" cannot be found USB HID device with hardware id "VID_044F&PID_0405" cannot be found USB HID device with hardware id "VID_044F&PID_0406" cannot be found USB HID device with hardware id "VID_044F&PID_0407" cannot be found USB HID device with hardware id "VID_044F&PID_0408" cannot be found Virtual HID devices managed by script! Connecting virtual joystick...Done Device name set to Thrustmaster Combined Connecting virtual keyboard...Done Connecting virtual mouse (absolute axes)...Done The 'Thrustmaster combined' virtual device is crated. Device analyzer shows it is consists of the throttle and the stick. The device analyzer shows all physical device interaction (both throttle and stick), but only throttle gets captured and transferred to the Combined virtual device.

Hi everybody. Is there a way to order to AI platforms to attack JUST a target instead to engage whatever enemy things they see? I see planes ordered to attack a single cargo vessel (mission type: anti ship strike, advanced waypoint actions->attack group->name of the group... and a small blue triangle is placed on the ship to be engage) engage another cargo placed miles away that is a target of another flight. Please note that in advanced waypoint actions i select to expend ALL the ammo's on this target. I saw this behaviour also on ground mission where an apache flight was attaccking my targets rather than their. Thanks a lot in advance and please excuse if this subject was already discussed. I wasn't able to find anything about it.

Is there a reason the targeting pod refuses to track moving targets?!? Perfect contrast, slow moving target still nothing. I've got it to track once for about 100', until I crashed into the target seeing I was a quarter mile away from it before it even started tracking.

I have found this weird behavior of the TGP (Litening): Use WPDSG to select waypoint as target. Activate the TGP and move it. Use SCS right 3 times to cycle to Area, Point and back to Inertial mode. When going back to inertial, the TGP is moved to the target designated point. Note that if TDC is pressed before moving the TGP away from the WPDSG point and then cycled with SCS to Area, Point and Inertial, the TGP does not move away from current position (last cycle in the track was done using this method). Track attached b-tgp-moves-to-tgt.trk