Military AI Works

Hello. I'm hoping someone can help me out here. I tried to post this in the "MAIW Package Support For FS9" forum but it wouldn't let me for some reason.

I am using the "AMC West Coast C-17's" package and have noticed that I am getting multiple C-17's for the flightplans. Well, at least one of them anyway. But, I don't know how to resolve this. What I have seen is four C-17's grouped together flying through the sky and I'm pretty sure it shouldn't be that way.

If anyone can help me figure this out I'd appreciate it.

Thanks!

Guessing the forum security wouldn't let you post in that forum because it was your first post, I think you need at least 3 total posts to have unrestricted access, keeps the spambots from flooding the forums.

You could have a couple things going on.

The first that comes to mind is that you might have the same traffic .bgl file in two different locations which would double your AI traffic.

One way to check to see what's happening is to find that flight of four C-17s and use something like Traffic View Board to look at the flight numbers and serial numbers of the individual AI aircraft. MAIW packages use individual flight numbers and serial numbers. If in that flight of four, you have four separate serial numbers and flight numbers then it's not a mistake, it's just a 'simism' or the way the flight plans were written.

On the other hand if they all have the same flight number or serial number, you have duplicate flight plan files and then you should be able to hunt down the offending files.

Hope this helps.

MIKE JG wrote:Guessing the forum security wouldn't let you post in that forum because it was your first post, I think you need at least 3 total posts to have unrestricted access, keeps the spambots from flooding the forums.

You could have a couple things going on.

The first that comes to mind is that you might have the same traffic .bgl file in two different locations which would double your AI traffic.

One way to check to see what's happening is to find that flight of four C-17s and use something like Traffic View Board to look at the flight numbers and serial numbers of the individual AI aircraft. MAIW packages use individual flight numbers and serial numbers. If in that flight of four, you have four separate serial numbers and flight numbers then it's not a mistake, it's just a 'simism' or the way the flight plans were written.

On the other hand if they all have the same flight number or serial number, you have duplicate flight plan files and then you should be able to hunt down the offending files.

Hope this helps.

I've checked for duplicate traffic files and that isn't happening. I don't even know where it was that I saw them so finding them again would be impossible. All I did was grab the package and install it. Which makes me think there is an error in the traffic file that is available. But I don't know how to check it as it's pretty intense.

Do you have any other traffic installed, for example the JustFlight traffic systems?

Firebird wrote:Do you have any other traffic installed, for example the JustFlight traffic systems?

No payware traffic stuff. Only freeware stuff either I or others have put together. I'm pretty sure the only military traffic I have though is from MAIW. And I know it's only that for the C-17.

OK another simple question do you have John Stinstrom's Travis AFB scenery installed?

Firebird wrote:OK another simple question do you have John Stinstrom's Travis AFB scenery installed?

Not sure. I'll have to check. If so, what should I be looking for?

Well if you do have that scenery installed he has included in the scenery folder 5 traffic bgl's, My guess would be that this is your problem.

As a general rule traffic bgls normally go in your 'Flight Simulator 9\Scenery\World\scenery' folder but they can go, and be loaded, from any active folder that is in your scenery.cfg file.

I would search your scenery file to see if you have a Travis folder from John. I would then suggest that you create an archive folder in your Travis\scenery folder and move thise traffic bgls into it and re-test.

If the error has cleared up then that is the problem and you can then work on which traffic files you need to put back and which you need to keep archived.

I don't seem to have any addon scenery for KSUU. Only the "MAIW_AF2_KSUU_DEFAULT.bgl" file containing parking, etc.

Then my next test would be to create an archive folder and move ALL your traffic bgls into it EXCEPT the West Coast C-17s bgl.
Then re-check to see if you have the same issue.

Just to make sure on the Travis scenery do a system search for 'Traffic_C-17_Travis.bgl'

Firebird wrote:Then my next test would be to create an archive folder and move ALL your traffic bgls into it EXCEPT the West Coast C-17s bgl.
Then re-check to see if you have the same issue.

Just to make sure on the Travis scenery do a system search for 'Traffic_C-17_Travis.bgl'

That's the problem though... I don't know how I can check for the multiple aircraft issue. When I saw it I was in the middle of nowhere and have no clue what time it was. And, I don't know how to check the flightplan file to see if that's where the issue is. I still think that's where the problem is at but would need someone at MAIW to check the package.

Don Grovestine's AI Flight Planner (AIFP) has some impressive analyzing features. You may want to give it a go.

OK what you saw was a planned formation. Pure and simple.

My initial read was that you had a duplicate traffic file where everything was duplicated. If you install AIFP, as Martin suggests, you can either load a compiled bgl or the raw txt files and check what is included.

Firebird wrote:OK what you saw was a planned formation. Pure and simple.

My initial read was that you had a duplicate traffic file where everything was duplicated. If you install AIFP, as Martin suggests, you can either load a compiled bgl or the raw txt files and check what is included.

If you can tell me without a doubt there are planned formations in that package then I'll certainly buy that. That was the whole reason why I posted to the MAIW forums in the first place because it was your package. I figured you would know. But, can someone tell me that for sure?

Yes, confirmed. There are some groups of four aircraft flying the same route at the same time in the package.

Giorgio

bismarck wrote:Yes, confirmed. There are some groups of four aircraft flying the same route at the same time in the package.

Giorgio

Did you use AIFP for this? If so, how?

No, I just check the flightplan.txt in the package. You can find it in th C:\....your FS dir\Military AI Works\USA\USAF\AMC West Coast C-17s

Giorgio

bismarck wrote:No, I just check the flightplan.txt in the package. You can find it in th C:\....your FS dir\Military AI Works\USA\USAF\AMC West Coast C-17s

Giorgio

I can decompile the plans okay but after that I don't exactly know what I'm looking for. Reading one specific flight is difficult enough but trying to find multiple ones that are the same seems crazy.

Call me Hawkeye.....

AC#78,00-0180,30%,WEEK,IFR,1/18:00:00,2/06:03:30, 400 ,F,0180,UAFM,2/08:11:00,2/09:41:24, 330 ,F,0180,OAKB,3/02:11:00,3/11:51:27, 350 ,F,0180,PGUA,3/13:11:00,4/00:20:37, 400 ,F,0180,KTCM
AC#79,00-0184,60%,WEEK,IFR,4/20:05:00,5/00:35:55, 330 ,F,0184,KLSF,5/02:11:00,5/06:41:55, 270 ,F,0184,KTCM
AC#80,02-1102,40%,WEEK,IFR,1/19:00:00,1/22:16:00, 370 ,F,0021,KVOK,2/17:11:00,2/20:27:00, 400 ,F,0021,KTCM
AC#81,02-1106,40%,WEEK,IFR,1/19:00:00,1/22:16:00, 371 ,F,0022,KVOK,2/17:11:00,2/20:27:00, 401 ,F,0022,KTCM
AC#82,02-1110,40%,WEEK,IFR,1/19:00:00,1/22:16:00, 372 ,F,0023,KVOK,2/17:11:00,2/20:27:00, 402 ,F,0023,KTCM
AC#83,90-0535,40%,WEEK,IFR,1/19:00:00,1/22:16:00, 373 ,F,0024,KVOK,2/17:11:00,2/20:27:00, 403 ,F,0024,KTCM
AC#84,98-0049,50%,WEEK,IFR,1/21:00:00,1/23:51:55, 300 ,F,0031,KBIF,2/03:00:00,2/05:51:55, 270 ,F,0031,KTCM
AC#85,98-0056,50%,WEEK,IFR,1/21:00:00,1/23:51:55, 301 ,F,0032,KBIF,2/03:00:00,2/05:51:55, 271 ,F,0032,KTCM
AC#86,99-0061,50%,WEEK,IFR,1/21:00:00,1/23:51:55, 302 ,F,0033,KBIF,2/03:00:00,2/05:51:55, 272 ,F,0033,KTCM
AC#87,00-0181,60%,WEEK,IFR,2/21:00:00,2/21:41:23, 220 ,F,0181,KSKA,2/23:11:00,2/23:52:23, 300 ,F,0181,KTCM,3/17:11:00,3/18:44:15, 300 ,F,0181,KSJC,3/21:15:00,3/22:48:15, 300 ,F,0181,KTCM,5/21:45:00,6/01:39:24, 300 ,F,0181,KEFD,6/03:11:00,6/07:05:24, 300 ,F,0181,KTCM
AC#88,00-0185,50%,WEEK,IFR,4/13:47:00,5/00:05:12, 330 ,F,0011,RKSO,5/03:15:00,5/13:33:12, 330 ,F,0011,KTCM
AC#89,02-1103,50%,WEEK,IFR,4/13:47:00,5/00:05:12, 331 ,F,0012,RKSO,5/03:15:00,5/13:33:12, 331 ,F,0012,KTCM
AC#90,02-1107,50%,WEEK,IFR,4/13:47:00,5/00:05:12, 332 ,F,0013,RKSO,5/03:15:00,5/13:33:12, 332 ,F,0013,KTCM
AC#91,02-1111,50%,WEEK,IFR,4/13:47:00,5/00:05:12, 333 ,F,0014,RKSO,5/03:15:00,5/13:33:12, 333 ,F,0014,KTCM
AC#92,92-3291,30%,WEEK,IFR,2/16:06:00,2/18:15:58, 330 ,F,0021,KNFG,2/22:11:00,3/00:20:58, 270 ,F,0021,KTCM,5/18:51:00,5/21:09:07, 270 ,F,0021,KCOS,6/00:11:00,6/02:29:07, 270 ,F,0021,KTCM

As you can see, the aircrafts AC#80; AC#81; AC#82; AC#83 start from the same airport (KTCM) at the same hour 1/19:00:00 (1= Monday) and go to the same airport (KVOK)
Also AC#88; 89; 90; 91 have the same flightplan.

Giorgio

Carob wrote:Hello. I'm hoping someone can help me out here. I tried to post this in the "MAIW Package Support For FS9" forum but it wouldn't let me for some reason.

I am using the "AMC West Coast C-17's" package and have noticed that I am getting multiple C-17's for the flightplans. Well, at least one of them anyway. But, I don't know how to resolve this. What I have seen is four C-17's grouped together flying through the sky and I'm pretty sure it shouldn't be that way.

If anyone can help me figure this out I'd appreciate it.

Quite simply: it should be that way. For multiple aircraft types from multiple bases to multiple locations. You're probably just seeing a mass airlift exercise being simulated. But go look at any MAIW flightplan (especially those from fighter units) and you'll see that a lot of aircraft are not flying alone. I think there's one unit with as many as six aircraft traveling together from one location to another at the same time.