Can't Get AI To Orbit

[VAF [136] Striker]

I've always been able to make this work without any problems. Set a waypoint about 3 or 4 miles ahead and then racetrack. But no matter what I do now the AI will not orbit. And I've tried it with a lot of different aircraft. I've tried deleting the default task too. What I've found works is if I put two waypoints with the first about 3 miles and the second a mile after that with the exact same properties, then it works.

 

It seems like the AI are basically ignoring anything at the first waypoint but taking commands from the second one. Any ideas what could be causing this problem and how to fix it? Or has something been changed in the editor that you need to set to make them obey the waypoints properly?

[Grimes]

Gonna need a sample mission to see what you mean.

[VAF [136] Striker]

Here's a couple examples.

VAF Georgia On My Mind Triggers Caucasus.miz

VAF Georgia On My Mind Triggers2 Caucasus.miz

[Grimes]

Its orbiting as expected in both missions attached.

[VAF [136] Striker]

I'll have to do a track file then. They are definitely not orbiting for me when I run the mission. They all just head home.

[feefifofum]

Cleanup/repair your DCS installation etc. etc.

[Falcon_S]

In your first mission TYPE: A10C but in mission is MiG29A and not ORBIT ... check mission

After edit mission, TYPE: A10C ...A10C is in mission and ORBIT

 

Same problem is in second mission. Check attachment. Something is worng in mission. Fighter symbol are on the map, fighter is in mission but selected TYPE is A10C

Edited April 18, 2018 by Falcon_S

[VAF [136] Striker]

Cleanup/repair your DCS installation etc. etc.

Completely fresh installation on a new SSD drive.

[VAF [136] Striker]

Its orbiting as expected in both missions attached.

I don't know what's going on because I just ran one of them on our server and they won't orbit. You'll see that the Mig-29 ignores the orbit order and just continues on to the next one.

VAF Georgia On My Mind Triggers Caucasus-20180418-150304.trk

[VAF [136] Striker]

In your first mission TYPE: A10C but in mission is MiG29A and not ORBIT ... check mission

Sorry Falcon, I should have mentioned that we change the db_countries.lua file to add aircraft to other coalitions. But it was doing this prior to that so it's not a coalition problem. The reason you're not seeing it in the editor is that they're not available in there by default. The orbit command is there in my editor.

[Falcon_S]

However... i changed aircraft and orbit work.

[VAF [136] Striker]

Look at my track file. I put it on our server and it still won't orbit.

[feefifofum]

Are you using any modded aircraft?

[VAF [136] Striker]

Devrim's English cockpit mods for the FC3 birds but I've had the same problem with the IL-78 and the KC-135 refuelers. Other than those and my A-10C lua changes nothing else has been altered. I never had trouble with getting planes to orbit in 1.5.

[feefifofum]

Interesting. It's peculiar that when we open your missions the aircraft are showing as A-10Cs but with fighter map symbology...I am also seeing the same thing. See below

 

When I run the mission the aircraft appears in-game as a MiG-29 and orbits as programmed. I added a GM slot and moved your test APC into the trigger zone and the MiG-29 broke orbit as expected and continued on its flight plan. Track is attached, I made no changes to the .miz apart from adding the GM slot.

 

I've never seen this particular issue you're having or experienced it myself...my best suggestion is to perform a cleanup and repair of your DCS installation.

Orbit.trk

[VAF [136] Striker]

You might not have seen my previous post but I completely wiped my installation of 2.5 and started over fresh with a new install of 2.5 onto a clean SSD drive. This has been happening since the first time I installed 2.5 beta and was happening prior to me installing any of my mods or liveries. I even started with a clean user folder but it was still happening. I also explained that the countries data file has been altered so that's why you see an A-10 in the mission file, but it's been happening with that unaltered as well. So this is not a problem happening caused by mods. Doing a clean up and repair has not helped either. I have tried that.

 

Did you look at my track file?

Edited April 19, 2018 by 75th-VFS-Striker

[feefifofum]

Sorry, missed the post about the altered database. No idea in that case. All I can say is your vanilla mission worked fine on my rig.

 

I don't doubt that it's not working on your system but it is 100% working on mine and neither myself, Baltic Dragon, or any of the guys in my squadron designing missions have had any problems setting up orbits. :dunno:

 

Try deleting the MissionEditor folder from your user directory and allowing it to rebuild? I know you said you started with a clean user directory at some point but can't hurt to give it one more try.

 

I'll post a .miz here shortly with a simple orbit. Curious if it will work on your machine...might give a better indication where the problem lies.

Edited April 19, 2018 by feefifofum

[feefifofum]

Here's a .miz built from scratch on my PC with more or less the same setup, minus the Iranian MiG-29.

 

The A-10C should perform 2 complete orbits over Kutaisi in a 10 minute period. After 10 minutes, flag 1 becomes true and the orbit breaks through the advanced waypoint action stop condition as in your mission.

 

Curious if this exhibits the same behavior. That will tell us if it's a problem with the mission editor on your end, or if perhaps something in the main installation pertaining to AI behavior is corrupted. It might be worth checking your logs as well to see if any strange errors are being reported.

Orbit test.miz

[VAF [136] Striker]

I tried it and the AI orbits at the second waypoint even though the orbit is set at the first waypoint. Can you confirm that this is just happening to me? I did try deleting the folder and letting DCS rebuild it but it didn't change anything.

[discwalker]

In your "VAF Georgia On My Mind Triggers Caucasus.miz" (the first)

the racetrack orbit between wpt1 and wpt2 working for me

- then i use my CA module to drive to the "Change Flight" trigger zone,

that breaks the first orbit (set flag1, stop condition: flag1 is set)

- then the MiG-29 heading to wpt 3 and not start orbiting between wpt2 and wpt3 because

the flag1 is set already, and that is the stop condition AGAIN :-)

- after wpt3 fighter landing to closest airfield

DCS do what you programmed.

[VAF [136] Striker]

In your "VAF Georgia On My Mind Triggers Caucasus.miz" (the first)

the racetrack orbit between wpt1 and wpt2 working for me

- then i use my CA module to drive to the "Change Flight" trigger zone,

that breaks the first orbit (set flag1, stop condition: flag1 is set)

- then the MiG-29 heading to wpt 3 and not start orbiting between wpt2 and wpt3 because

the flag1 is set already, and that is the stop condition AGAIN :-)

- after wpt3 fighter landing to closest airfield

DCS do what you programmed.

You need to look at the track file that I posted. As I already posted, it's happening only on my system for some odd reason.

[discwalker]

Please open "VAF Georgia On My Mind Triggers Caucasus-20180418-150304.trk" in the mission editor. You don't wait in the track to fly the MiG-29 the only one orbit, a racetrack between wpt1 and wpt2(far-far away), you added to advanced waypoint actions!

"VAF Georgia On My Mind Triggers2 Caucasus.miz" also has one orbit and working in SP.

 

If you want to clarify problems I suggest you to use the free Su-25T and add a plus free user plane to trigger F10 custom communication menu radio items. That way is better to set flags than Combined Arms module. "TIME MORE(seconds)" trigger condition is also useful.

Edited April 19, 2018 by discwalker
racetrack

[discwalker]

I slightly edited your first mission, then multiplayer also working as intended.

I did all tests in 2.5.0.15365.345

 

You can select Circle pattern for orbit if you want. (Race-track is selectable only if you program following waypoint.)

You can set stop condition for flag 2 is set for second orbit.

What do you want?

[VAF [136] Striker]

Please open "VAF Georgia On My Mind Triggers Caucasus-20180418-150304.trk" in the mission editor. You don't wait in the track to fly the MiG-29 the only one orbit, a racetrack between wpt1 and wpt2(far-far away), you added to advanced waypoint actions!

"VAF Georgia On My Mind Triggers2 Caucasus.miz" also has one orbit and working in SP.

 

If you want to clarify problems I suggest you to use the free Su-25T and add a plus free user plane to trigger F10 custom communication menu radio items. That way is better to set flags than Combined Arms module. "TIME MORE(seconds)" trigger condition is also useful.

You are not understanding the problem Discwalker or I'm not explaining in a way that makes sense. This is a problem that appears to be happening on my system only and it's possible that something is wrong with the track file. I will upload a video.

Edited April 19, 2018 by 75th-VFS-Striker

[VAF [136] Striker]

OK, here's a video showing the problem (ignore the jitters, not sure what caused it). Unless something has changed in the way you are supposed to send an AI into orbit since I started doing this 5 or 6 years ago then I'm stumped. And apparently this only is happening on my system. I deleted the end flag trigger because it was confusing to people what I was trying to do apparently. The AI should just go to waypoint 1 and go into an orbit but it clearly turns to the North and ignores the orders at waypoint 1. This problem happens with other aircraft as well like IL-76 or KC-135 with default coalitions so it's not because of my coalition changes. It was happening right from the first time with 2.5 beta.

 

Edited April 19, 2018 by 75th-VFS-Striker