Please help, I think its a bug...

[Raphael]

ok so there is something going really wrong with my latest mission and this is a really important thing.
when I want one fligth to wait in the base for 5 minutes and then take off i put on the roll delay 300 seconds, but first i test the whole route with the fligth and it all works ok. after changing it to the 5 minutes wait once the fligth takes off and goes the the following segment, lets say cruise, it doesnt follow the segment, it just goes randomly faaaar away and then turns 180 to follow the other waypoints. the idea in the mission i am doing it that there are some idle airplanes and after sometime pilots (AI) will jump on the planes and take off to fly towards the scramble or interception mission... but with this bug of the fligth going to some place else i have the timing of the fligth start ok... but it is useless since they will just go far away before consider folloing the route waypoints.. if I didnt make myself clear let me know, i can make some videos or take screen shots. please help me. does anyone has this "fligth not following the route after changing the roll delay" thing?

PS: I made a quick temporary fix that involves warping but i still want to fix this the rigth way... warping is not good for what i am trying to make here ):

[bbosen]

Raphael:

I've noticed something similar with versions of the Mission Editor since 2.13.1. Earlier versions were better.

Here is what I've noticed:

During offline missions, if you watch the map, you'll see a triangular marker that follows the mission plan. It advances across the map, and seems to be indicating where your mission plan INTENDED for planes to be located at that point in time. In earlier versions of the Mission Editor and Aces High, the bot planes followed that moving indicator quite closely.

However, with later versions like those now in popular use, the planes get delayed. Usually this comes about due to the oft-mentioned "slower than scripted" flight. However, in your case the problem may be made even worse by the 5 minute delayed departure. In either event, when the bots are off course, they seem to fly toward that moving indicator. Now, if the moving indicator happens to be straight ahead of their current course, you won't notice the effect. But if the moving indicator is off to the side due to a course change that your bot SHOULD already have encountered, then the bots may depart SIGNIFICANTLY from the scripted course, taking a "shortcut" toward the scripted location. In my recent experience, the bots rarely actually catch up with the scripted course, so they are always wandering through this "shortcut" logic.

Keep in mind that this is just my unscientific observation. It may or may not be accurate even in my case, and it may or may not explain what you are seeing. But it might....
 

[Raphael]

greatly detailed response bbosen, that is exactle what is going on. I guess soon I ill start making missions for the old version, but since im on the middle of this project i cant let it unfinished. anyway. thank you very much for your help. the departure time bugs the route logic even more but im finding some quick ways to get around it of course not with the results i would get from nice following bots but anyway...
im dealing with another REALLY big problem rigth now. my mission is kinda long and it is suppose to last for about 3 attack waves or more. what is happening is that when i test the mission on ME's run mission the fligths are all there until the very end of the last one. when i test it in game however, the AI disapears on the second wave. it is like. the first wave goes and i play nicely, then im there rearming and justkeeping my eyes open to see the dive bombers getting closer. they start to get closer. my AI team mates go for them and before the bombers get much closer the mission fligths disapear and the offline practice drones appear flying on the top of the airbase ._. just like if the mission was suppose to end rigth on that moment... wich is not.  Im trying to figure out some quick exits around that one too but with no success so far.

[Raphael]

fixed this second bug!

[bbosen]

What fixed that second problem?

[Raphael]

well it is quite simple actually. when you start a mission you must make sure all routes on the same mission ends after or at the same time of the route your fligth is at. so in example if you make a bishop mission and you join lets say a fligth with the p51. this fligth will have a total time of action witch is the segments' total time on all the waypoints you use, not mattering the glich were the AI cant follow some speeds. if on the same mission (bishops) there is an AI p38 fligth that has its total time shorter then yours the mission for all fligths will end when this first fligth end.
im my case i had several routes and one of them had a really short period of time. fixed that by making this route last longer.
it is really wierd when you let that go and you see it happening... one second you see all the AI in front of you and next thing you know they are all gone and there are the drones again.