SnappyComebacks

Hi Rainmaker, thank you for the interest. In DCS, GBU-12s will successfully track even with nose only fuses. However for completeness, and to address any possible concerns, I have created additional tracks with Nose/Tail fuse set. The attached file contains the following tracks (and a mission file): 2x CFT config BDU-50LGB failing to track with N/T fuse. 4x CFT config BDU-50LGB failing to track with N/T fuse. 1x centerline BDU-50LGB successfully tracking with N/T fuse. 2x CFT config GBU-12 successfully tracking (and exploding) with Nose only fuse F-15E_BDU-50LGB_TrackingBug.zip

If I have the F-15E configured with 2x or 4x BDU-50LGB on the CFTs (as in 2x or 4x on each CFT), the LGB released from the CFT will not track a laser. If I configure 1x BDU-50LGB on the CFTs, the bomb will track the laser. Track and Mission file attached. F-15E_2xBDU-50LGB_DoesNotTrackLaser.zip

DCS 2.9 Open Beta In a simple mission I have two F-15s escort a B-52. In level flight the B-52 flies with a nose down attitude as well as the escorting F-15s. F-15s that are not escorting fly with the correct nose up attitude. Track and Mission file attached. NoseDownFlight.zip

I can communicate in/with FC3 aircraft ok in other missions. It's just this one acting weird.

The instant action on the Nevada map called "F-15C Aggressors" prompts you to work with your wingman to fight the enemy F-5Es. However, I cannot communicate with my wingman. I'm not getting any response to radio commands. (I have Easy Comms off). Track file attacked. F-15_Agressors_AI_Wont_Communicate.zip

In the typical use case of CCRP, the ASL will guide you to the target. If the ASL is to the side, you turn towards the ASL until the flight path vector intersects the ASL. Unfortunately, when the aircraft is upside down the ASL encourages you turn away from target, and not towards the target. When upside down, the more you deviate from a perfect target lineup, the more the ASL wants to guide you away from a good target lineup. I believe that the ASL should encourage you to steer towards the target, regardless of if the plane is upside up or upside down. Mission and Track are attached. F-16_ASL_Off.zip

I uninstalled several terrains in one line (./DCS_updater.exe uninstall MODULE1_id MODULE2_id ... ). The program reported success. Was it intended for me to need to manually delete the folders after as well? Or was the executable supposed to do that for me?

A server queue feature would be great. There are several servers that I want to play that get full frequently.

Hello, The AI F-15 does not let you manually load Air to Air missiles on the CFT stations. It should be possible to manually put AIM-120s and AIM-7s on stations 13, 11, 9 and 7. There are presets that have missiles on those stations, but you cannot choose them yourself. This makes it difficult to create mixed A-G/A-A loadouts, as the presets are only available for CAP/Escort/Fighter Sweep mission types. Please see the two images attached for reference. Thanks

Mission: Instant Action > A-10C II > Persian Gulf > CSAR Sandy The description mentions a Sam site but provides the distance as "xx" instead of a number. null

Mission: Instant Action > A-10C II > Persian Gulf > CSAR Sandy The mission features two convoys that approach the FA-18 crash site. In the past, both convoys converged onto the crash site. But recently (I believe with the first DCS 2.8 release) the convoy that traverses the narrow canyon stays in its starting position. I have attached a track and tacview. Thanks CsarSandy_ConvoyDoesntMove.zip

Hello, It appears that the AI flight models do not account for damage to engines (and possibly control surfaces). This was discovered when I did an instant action BFM mission, and the aircraft I was fighting did not lose any performance after severely damaging its left engine. I have attached three tracks showing me damaging all but one engine of several different AI aircraft. (A-10C, Mig-29S, Il-76M). The result is that DCS reports through the info bar that all engines are still running, even though visible damage is shown. The AI appear to suffer no adverse effects to the flight model, though they do change their navigation behavior once damaged. The IL-76 track I have included is the most obvious offender, and is the only one of the three tracks that follows through until landing. Thanks AI_IgnoresEngineDamage.zip

I have tried the following waypoint actions: I removed the Reaction To Threat action and removed the Jamming action as well. Still no change in behavior.

I deleted the SEAD task in waypoint actions on purpose. I do not want the SEAD escort to attack every SAM site on the map, just the ones within the engagement distance. In the modified mission you shared, the SEAD flight attacks the SAM immediately, instead of when the flight reaches engagement range. Edit: In the shared mission, the distance between the SAM and the SEAD flight is almost immediately at engagement range. You can test this by moving the flights starting position further away.

Setup: Three Blue AI flights (Package) ToBeEscorted: Flight flying from WP0 to WP1 SeadEscort: Flight with SEAD main task and Escort advanced options task, escorting "ToBeEscorted" AirEscort: Flight with Escort main task and Escort advanced options task, escorting "ToBeEscorted" One Blue AWACS One Red flight flying parallel and in opposite direction to the package, offset by a distance, with "Nothing" task One Red SAM site (SA-3) near the package's flight path Expected: When SeadEscort reaches the Engagement Distance of the Red SAM site, the SeadEscort flight engages the SAM site in a reasonable amount of time. Actual: When SeadEscort reaches the Engagement Distance of the Red SAM site, the SeadEscort flight flies directly away from the SAM site to about a 50 mile distance from the SAM site, then return and attack the SAM site. Mission, Track, and Tacview attached. AI_SEAD_Escort_FlyAway.zip

Mission: Missions > F-16C > Turn Out The Lights (Persian Gulf) When trying to start the mission I receive: `This mission is newer than this editor.` I am on the latest Open Beta.

Mission: Instant Action > F/A-18C > Persian Gulf > Missile City. The briefing of the mission consistently references F-16C instead of F/A-18C, and lists an incorrect loadout (Should be GBU-24, but is listed as AGM-65K). Graphic and Title also display F-16C.

If you lock (or soft lock) a contact in the Range While Scan (RWS) mode, then break lock using TMS aft, the PDLT feature no longer works correctly for that same contact. When you try to use PDLT again on the same contact, the octagon will flicker and then disappear. This behavior effects each aircraft you attempt to lock. If you lock a contact, then drop lock and PDLT off axis, where you would get the dashed line and the degrees off indicated on the HUD, the indicator does not appear to update either. Track and Mission attached. F16_CannotPDLTAfterLocking.zip

When changing formation, occasionally the wing men will collide with each other. My most recent instance attached is when the flight hadn't completely formed up. (Number 4 was lagging behind, 2 & 3 were in position). I changed formation to "Spread Four" and wingman 2 + 3 turned into each other and collided. Track and Tacview attached. (~10 minutes long, incident happens at the end.) The mission was the second mission of the F-15C campaign that comes with Flaming Cliffs 3. I am on the current Open Beta. AI_Wingmen_Collision.zip

With the Tornado GR4 it is possible to have a weapon mounted to station 8 and 9 simultaneously, as well as 5 and 4 simultaneously, which causes direct overlap. In addition, putting a GBU-12 on pylon 7 clips with a GBU-12 on pylon 8, and a GBU-12 on station 6 clips with a GBU-12 on station 5.

If an E-2D and F-14 happen to spawn next to each other on runway start, the F-14 will never take off. Happens on the Stennis as well as the Supercarrier module. Trackfile and mission attached. Setup: At mission start: AI E-2D (single ship flight) runway start at Catapult 1. AI F-14B (flight member 1 of 2) runway start at Catapult 2. AI F-14B (flight member 2 of 2) runway start at Catapult 3. Player (1/2) and AI (2/2) 2 ship F/A-18C Lot 20 cold start. Current Behavior: E-2D takes off F-14s never take off Expected Behavior: E-2D takes off F-14s take off E-2D_F14_CarrierConflict.zip

Right on; thank you. Solved.

Track and Mission has been attached. When performing a cold and dark start on an aircraft carrier, the radar altimeter does not function. Setup: Player F/A-18C cold and dark start on the Stennis carrier. Winds at various velocities at different elevations Atmospheric pressure set to `30.08` Completed cold and dark start, radar switch by alignement switch set to `OPR`. Expected Behavior: Radar altimeter to be on. When BAR/RAD Alt switch below UFC is in RAD position, Radar altitude to be presented on the HUD. Current Behavior: The radar altimeter does not turn on, even though the radar is on, and can scan for air and ground contacts. Flipping the BAR/RAD Alt switch does not effect the altitude displayed on the HUD. Cannot use Autopilot Radar Altitude hold. Here is a video demonstrating the behavior: To Reproduce: Begin a cold start in the F/A-18C with quick alignment. When turning on the radar, keep the radar knob next to the alignment knob in standby. When alignment is complete, turn alignment knob to `IFA` and radar knob to `OPR`. Continue with startup. Launch and play with BAR/ALT switch to see that radar altitude is never displayed. See that A/P Radar Altitude hold does not function. Switch to A/A master mode to see that radar is on and scanning. F18_NoRadarAltimeter.zip

Trackfile, Mission, and Tacview attached. If an AI F/A-18c Lot 20 is set to have the `ECM Using` option enabled with anything other than `Always Off`, it can be bullied into not firing radar missiles to defend itself. This lets the player fire BVR missiles without concern getting engaged by hostile radar missiles. I suspect this could be the case with any aircraft where the radar also has the role of jammer, like the F/A-18C. Setup: Player in F-15C with favorite BVR loadout. Hostile AI F/A-18C Lot 20 (CAP task) with AIM-120Bs and AIM-9Ms; `ECM Using` option enabled and set to `Use if only lock by radar` Player and hostile in hot aspect at 20,000 feet altitude, 50nm seperation. Hostile has AWACS support. Expected Behavior: AI F/A-18C should turn off ECM and fire AIM-120Bs (or other missiles) when air threat is determined to be too severe to defend from with ECM. Current Behavior: When using STT to lock the AI F/A-18C lot 20. It will keep ECM on and be unable to fire AIM-120Cs to defend itself. Usually will use AIM-9Ms to defend itself but sometimes will not. This lets the player fire BVR missiles without concern of return fire from the jamming F/A-18C. To Reproduce: Have mission where AI F/A-18C Lot 20 has ECM Using option `Use if only lock by radar` or similar enabled. Lock F18 with STT (and continue to attempt lock if lock is broken by jamming) Continue closing and do not fire. See that AI does not fire radar missiles. Bullying_F18s.zip

Trackfile: https://we.tl/t-Qv76S1JNSb (WeTransfer service. Expires one week from posting.) Trackfile is 6MB (too big for forum, sorry) Edit: Added second trackfile from new mission with only F16 in it. (Small enough to attach) Setup: Instant Action - F16 - Caucasus - Cold and Dark Performing a cold start in the F16. All systems are ready from normal startup, except for HMCS. Expected Behavior: Upon release of `Enable` key command after receiving `Align OK` when performing course alignment, the HMCS alignment position should be set. Current Behavior: Pressing `0` on the ICP after receiving `Align OK` to progress to Az/El alignment sets the position of the coarse alignment. This makes your coarse alignment misaligned if you turn your head to press `0` on the ICP. Here is a video showing the current behavior. Video shows full cold and dark start, feel free to skip to HMCS alignment: To Reproduce: Start a cold and dark jet completely, except for HMCS. Turn on HMCS. Navigate to the HMCS DED page. Dobber right to the coarse/az-el/roll page. Ensure coarse is highlighted and press `0` on the ICP to start. Align HMCS cross with HUD cross. Hold `Enable` keybind with crosses aligned until seeing `Align OK` and then release `Enable` keybind Move head away from centered HMCS cross Press `0` twice on the ICP to move to `Az/El` Az/EL alignment crosses are set where you are currently looking, instead of where they were set by coarse alignment. F16_HMCS_Alignment_Issue.trk