Carrier 2006: AI aircraft with missing model files

[leuen]

As you know, Carrier 2006 comes with AI aircraft traffic files. These are the aircraft required:

AC#1,200,"ALPHA A-6 Carrier AI Version"
AC#2,200,"ALPHA F-14 AI Carrier Version"
AC#3,200,"ALPHA S-3 AI Carrier Version"
AC#4,200,"SH-3 Seaking AI"

I managed to obtain them somewhen and somewhere. However, none of these aircraft have the model folders and files. Does anyone happen to have these lying in one of the drawers? For obvious reasons, I would be very grateful to be able to include them.

Thank you very much for your eventual help.

Bernard

 

[Sbob]

The Aircraft Carrier Thread.

On to Traffic BGLs and AI. :wiggle: (PART 1) Again, just practical experience on my part but, you want to keep your AI and their flight plans to a minimum. Remember that the flight deck on the carrier is rather small and AI have a bad habit of getting into stand-offs. Also remember that...

sim-outhouse.org

You should note that the Traffic BGL for the carrier near NAS Miramar is screwed up in the original package.
Go back a couple of pages in the carrier thread and I posted a fixed version.

I use MAIW AI aircraft for my carrier scenery.

Aircraft Models (FS9) - Military AI Works

Military AI Works is the home base of military AI traffic for Flight Simulator and Prepar3D

militaryaiworks.com

I have some downloads I customized on my resources page:

Resources by Sbob

and some are posted directly in the carrier thread.

One thing I still need to make is "wet deck" (cable trap) AI using the MAIW F/A-18 Hornet family of planes.
I also have some Hornet AI from the Abacus Flight Deck series of carriers.
While they are set up for "wet deck" landings, the MAIW AI use newer, more detailed models.

You can use the MAIW "dry deck" aircraft but they act a little goofy when they land and taxi.

Meanwhile, I guess I should add that I tracked down some of those AI aircraft used in the C2K6 traffic BGLs and tried them out.
They worked OK back in 2006. Now?
Keep in mind, back in 2006 most of us ran a Pentium CPU and a 800X600 CRT monitor.
Those AI looked REALLY dated back in 2015.
Its better to edit those traffic BGLs with Traffic Tools and run the newer AI aircraft and choppers.

 

[leuen]

Thanks for your reply and the tips. I've already read through your very ample thread.

Of course, I could replace the incomplete aircraft with others. However, I don't really have the time or inclination to search for them in the net.
The incomplete files might be from the "Bige_ai.zip" package. However, this isn't currently available at FlightSim. Therefore, I'll probably have to use the ones from "Flight Deck 3" in Abacus' "Carrier Operations Collection" package.

In any case, thank you again for your help and support.

Bernard

 

[leuen]

I finally manged to substitude the missing aircraft.

I stii cannot unterstand how scenery package could be released with traffic files, whereas the user is aked to have a payware scenery. It's quite easy.

Bernard

 

[Sbob]

Yeah, I gotta go wayy back and remember what was going on at the time.

Most of this was info I picked up via Freeflight Design Shop, where we didn't poke our noses into what was happening in Payware.
Alphasim had two air craft carrier packages that were sold as payware, Enterprise and Kuznetsov.
Abacus also had its Flight Deck series.

Between the two of them, there were some VERY similar developers cranking out the source code.
Mostly, it was the same small group of folks "working" for both companies.
You can imagine why there would be some over-lap. I'm being very diplomatic here, if anyone has more info they'd like share, I'd still like to know what was really going on.

Alphasim did their Enterprise package for FS2002 and then shelved the project. The updates you see for FS9 were cranked out as Freeware updates. For what its worth, working on AFCAD and Traffic BGLs for FS2002 is a pain in the ###. Those files HAVE to be spliced into the "master" scenery list where in FS9, they can all be "stand alone" BGLs. That's why I don't like to mess around too much in FS2002, especially with Traffic AI.

Anyway, it all came down to "ownership" and Payware contract rules.
This got confusing when the "workers" decided to go back to Freeware (ARRCAB and RCBO as an example) and took their source files with them.
So, it all comes down to timing and whether you bought your AI or downloaded them as Freeware.

BTW, if you're running old carrier scenery with Traffic in FS9, I would REALLY recommend that you check the Traffic BGLs with Traffic Tools, especially the Flight Plan sub-files. If you see stuff that looks like machine code (@, $, ^, #, etc.), it usually means the flight plan was generated for an older version of FS. In theory, it should work. In reality, it usually doesn't.

 

[leuen]

So far I haven't encountered problems with the flight plans. The hastag symbols seem to be indispensable for porgramming reasons , whereas @- signs are normally used in airline FP to insure - more or less! - correct arrival times. CalClassic FPs are full or them without creating any inconviences. Those for Carrier 2006 are done for simple pattern lfights.

Concerning implemented AI aircraft, times obvisouly now changed. AI von Pingel added several AI aircraft in his and Ken Lawson's classic air base packages. As said, other times, other customs.

Bernard