Jump to content


  • Content Count

  • Joined

  • Last visited

About ColonelPanic42

  • Rank
    Junior Member
  • Birthday 03/09/1991

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. F-14s can carry TALDs which are fit for SEAD missions, but the F-14 is not allowed to be assigned to that mission type in the ME (and attempting to do so will cause the group to switch airframes). I've attached screenshots showing the full list of airframes that are allowed to use this mission type. The result of this is that F-14s cannot use the Escort enroute task to defend against SAMs, which only groups assigned to SEAD may do.
  2. Any luck? Any more info I can provide? We're quite interested in getting a fix for this because not being able to predict the path that the escorted group takes (or how long they'll take to finish their attack) means that we currently rely on just setting the escorts on a path through the target area. If the attacker is quick, the escorts loiter in a dangerous area and don't escort the attacker out of the area. If the attacker is slow, the escorts might leave before the attacker is done, leaving them unprotected.
  3. The goal here is to have a flight of F-14s launch their decoys and use them as cover while they approach to bomb the target. AI skill is set to ace, and the SAM starts in red alert mode. I've set up an Attack Group task on the target (aiui this does not require the target to be visible to the AI, but I have a Kiowa AFAC to spot the target just in case) set to auto weapon, group attack. Expend all ordnance is not an option when "auto" is selected. I expect the AI to fire their decoys and then continue with the rest of their weapons. Instead they fire their de
  4. This railroad is missing a connection (as is the smaller road that's supposed to go beneath the highway) near Tishreen Lake in Syria (37 S BV 304 497). This prevents connecting Aleppo and Damascus by rail. This does seem to be complete IRL: https://earth.google.com/web/@35.65424842,36.02085321,136.79718617a,604.71390451d,35y,0.00000331h,0.62922038t,0r
  5. Based on a precise reading of the manual, I think it's a misleading name rather than a behavior bug: "Same as the Search Then Engage Enroute Task, but with an added restriction of a user-defined target area." It's not "search the zone and engage the targets", it's "search the route and filter by the zone". Would be nice to have an option for the behavior I expected. https://forums.eagle.ru/forum/english/digital-combat-simulator/dcs-world-2-5/dcs-wishlist-aa/7149996-task-for-attacking-aircraft-on-the-ground
  6. Looks like this is actually a bug in the search then engage in zone task. https://forums.eagle.ru/forum/english/digital-combat-simulator/dcs-world-2-5/bugs-and-problems-ai/ai-ad/7150830-search-then-engage-in-zone-does-not-search
  7. The attached miz and track show that the Search Then Engage in Zone task does not actually perform a search. There are three flights in the mission. The leftmost has a single Search Then Engage in Zone waypoint with the target area over the airfield. This flight RTBs the moment they hit their IP, without ever searching the target area. The second is the same as the first but also includes a flyover point over the airfield. They fly to the airfield, then back off and begin their attack run. The third is the same as the first but the search task has a duration of 15 minutes. They do not wait
  8. There doesn't appear to be a way to task AI aircraft to attack enemy aircraft on the ground. CAS search then engage will not attack planes, CAP search then engage will not attack things on the ground and will not use air to ground weapons, fighter sweep does not work, CAP does not work, CAS does not work. Bombing appears to be the only option, but that has its own issues. The target location must be set in advanced (if the target begins to taxi it will not be hit) and with groups of AI fighters there is no way to have them split up tasks among themselves, so attacking 8 grounded planes will
  9. Just to be clear up front, everything in the sim is behaving correctly here :) The problem is that the way the ME displays speeds for waypoints with a TOT when the previous waypoint has a departure time different from its arrival time confuses people. I've attached a mission (and track file) that includes two flights. The first travels a longer distance from waypoint 0 to waypoint 1 and is set to arrive (based on speed, not a fixed TOT) at waypoint 1 at T+0:10:00 and waypoint 2 at T+0:15:00. The second flight has the same waypoints 1 and 2 but shifted south a bit. Waypoint 0 is much c
  10. Spreading the waypoints out does give the wingman more time to catch up, but that's not the behavior I'm looking for. They're on the way to their rendezvous point, so I don't actually want them waiting for their wingman at this point. Still, the workaround is a good idea, so thanks! I think I can also improve things by slowing them down a bit, since I think the wingman is at MIL trying to catch up and just barely closing. I probably should have filed this as a feature request instead. Are you able to move it or do I need to repost?
  11. Yeah, that matches what I'd observed. I agree that this isn't high priority, but it does seem to demonstrate a real (if a fairly avoidable) issue with the AI's flying. If they find themselves stuck at high AoA while flying in a straight line they should pitch down enough to recover if that won't run them into the ground or override AB restrictions if needed. I appreciate them trying to save gas, but the gas isn't worth much if they can't get anywhere :) If I can come up with a demo that shows this happening on the attack task (where the mission creator has no control over the distances the
  12. Done, thanks! https://forums.eagle.ru/forum/english/digital-combat-simulator/dcs-world-2-5/dcs-wishlist-aa/7121311-options-for-alternate-ai-escort-behavior
  13. https://forums.eagle.ru/forum/english/digital-combat-simulator/dcs-world-2-5/bugs-and-problems-ai/ai-ad/250183-task-follow-and-escort-temporarily-aborted is the expected behavior for the Escort task, but it doesn't appear that there is a way to task the AI to perform a close escort mission while the escorted AI performs their strike. Could we get a new task type added (for both Escort and SEAD mission types) or some new options for the existing task to provide the behavior expected in that report? I'm not sure if the alternate behavior for the AI should have them follow the escorted group e
  14. I've attached a mission and track that demos an AI aircraft taking off, ascending toward a waypoint specified in AGL, and then turning toward another waypoint. It seems that in attempt to maintain exact radar altitude the AI commands huge pitch oscillations that bleed speed until they reach 18.5 AoA, at which point they seem to be unable to recover. The exact same flight plan with the waypoint specified as MSL (the altitude MSL is the same in both cases; it's the radar altitude specification that seems to affect the AI). I suspect this could be because the buildings the AI is flying over is ca
  15. The attached mission is a simplification of the desired flight plan: take off, ascend to a hold point, loiter until a push time, then push to the objective (objective omitted in this demo). Both pilots are AI. The AI wingman isn't able to follow the flight lead through the first turn, and it seems that the AI lead will not climb toward the hold point unless the wingman is joined. Once the wingman joins they do begin to climb, but not in time to reach the altitude of the hold point, so instead they do most of the climb in a high speed circle. If you remove the wingman so it is only a single
  • Create New...