CougarFFW04

Hi feefifofum Thanks a lot for your advises :thumbup: What I have observed... They travel to the threat at > 400knt They return to their path orbit at 270knt (orbit speed).

Hi Guys, Another question concerning AI logic and in particular GS/ETA flags in the ME. At a given Ground Speed you need a certain time to go a given distance. CLEAR. That is the reason why the ME automatically edits ETA/GS or shows errors in case of insconsistancies. I am wondering how AI manage things if for some reason they cannot achieve the goals that were setup in the ME (assuming no errors in the ME). Lets' immagine the following scenario : I have setup a "package" (although there is no notion of package in DCS as far as I saw ?) with two flights (F1 and F2) starting from airbases 1 and 2. The flight plan is the following WPTs : 0 (TO), 1(ETA locked), 2, 3(ETA locked), 4 and 5 (landing). Except WPT 0 and 5, all WPTs are common to both flights. I have also managed that they reach WPT1 and WPT3 together in the ME (same ETA locked). Now immagine the following : for some reason (in particular because it seems that DCS ME does not take into account taxi time delay that might be very different in different airbases), although F1 is on time at WPT1, F2 take-off with a delay and is late at WPT1. In principle F2 should accelerate to try to be on time. But I have noticed that if the TO delay is too long (due to excessive taxy phase for exemple) F2 cannot reach WTP1 on time... How F2 will now manage WPT3 (ETA locked as well) ? Anyway F1 and F2 will not push together and my scenario is ruined :cry: A solution would be to introduce a waiting pattern at WPT1 (for both F1 and F2) with a stopping condition a bit latter (let's say 10 minutes delay for conveniance)... But now what about WPT3... Obviously neither F1 and F2 will be able to reach WPT3 on time... So what would they do ? In fact I have tested theses scenari and sometime I have observed very weird (to say the least) AI behavior : they were traveling WPT path at very low speed (~180 knt) / hight AOA and even sometime crashes... including path parts where I had locked the GS at 350 knt... Any comments ? What are the recommandations to have flight following as much as possible the flight plan as designed in the ME ? Thanks

Hi Guys, I have a question concerning AI behavior when they must change their MSL altitude on their flight path between two waypoints (let's call them WPT1 and 2). Altough I could not identify the reason, I have noticed that : - sometime they start climbing after passing WPT1 and then fly at WPT2 altitude till they reach it. - sometime they delay their climb and fly WPT1 altitude till a certain point where they start climbing to reach WPT2 at the selected altitude. What is the reason that determine the start/delay climbing behavior ? How can I choose between these two ? I searched in the manual but didn't find anything about that... Thanks

Hi, A few more questions about that : 1) The CAP scenario I was discussing includes two different tasks : CAP itself and Orbits. Concerning the duration which one should I set ? CAP duration ? Orbit duration ? Both ? When do the tasks start ? 2) Let's say that I do not want them to get away from more than 25 miles from their path. Is it possible to assign a maximum distance of engagement ? I didn't find this parameter in the CAP task (Not speaking here about a completly new home made CAP task with a area trigger). 3) I have noticed that when they detect a threat they fly at high speed towards the ennemi. However, after engagement they return to their path at the path speed (which I setup at 270 knt). Is it possible to make them returning to their path at hight speed without changing the track speed ? 4) Although I cannot find the page right now, the manual claims that when the task is selected, the planes are loaded with the corresponding missile, bombs or whatever. When I choose CAP, the plane loadout is empty by default... Comments ? Thanks again.

Hi Guys, Thanks a lot for the tips :thumbup: I am gonna experiment this now. Regarding Flight path on map, although I certainly missed something, I did a simple mission with four planes taking off for a "none task" mission where they are supposed to fly along their path. F10 view shows that although they pass WPT1, the dashed line stay sticked to it till they pass WPT3 which has nothing special... Anyway please do not discuss it here as I will come back to this in another thread because this behavior seems very strange to me. Dont worry I have still many more questions :lol:

Thanks feefifofum, I will have look at your missions

Hi feefifofum Thanks. As there is no parameters for the circle orbit I thought that the racetrack would do the same (different géometry) around WPT. Although the documentation is not very clear about that, the track picture suggests that you are right. Will try and report. What about the dashed flight path connected/not connected in F10 view ? Thanks.

Hi, Thanks for your advise. I know this, But actually it is NOT what I want to do. I DO want that they loops on MY WPT1 and 2. Thanks anyway

Hi everybody, I am new to DCS and DCS Mission Editor and I want to apologyse if someone already anserwed this question but I didn't find what I was looking for. So the question is the following : I would like to create a simple mission with a plane (doesn't matter which) taking-off (doesn't matter where) for a CAP mission. The flight plan would be just 3 WPT (0 (airbase), 1 and 2 (turning points)) and I would like that the plane loops on WPT1 <-> WPT2 for a given duration (let's say 15 mn for the discussion) before RTB. I tried this but I was unsucessfull to achieve this simple scenario. First I just setup the discussed Flight Plan with the default CAP enroute task. As the manual mation : I thought they would loop WPT1, 2 automatically BUT in fact they flew through WPT1 and WPT2 and then RTB to land. Then I validated the starting task condition to 100% and the stopping condition to 15mn duration but this didn't changed anything. Finally I was able to make them looping WPT1 <-> WP2 by adding a command option at WPT2 (switch to WPT1) but they still ignore the duration condition whatever I did :( I have noticed the "Last Waypoint" option in the stopping condition but didn't find something about it in the documentation (edit : got it p150 of the manual). I tried this as well but it didn't change anything. What did I do wrong ? what did I miss ? I have also a question about the dotted line flight path that show when we run a mission in map mode and click on a flight (it's path is displayed with the waypoints as circle symbols). I have noticed that sometime when the plane pass the WPT it is erased and the plane is linked to the next one. Sometime it isn't... What does this mean (erased / not erased) ? Looking forward for help, Thanks