Military AI Works

Post any and all support related comments for this package in this thread.

NOTE: Support for FSX users will not be offered in this thread. Instead FSX support can be had by posting questions in the MAIW Packages in FSX support thread located here:

http://www.militaryaiworks.com/newforum ... =15&t=6975

Ohhhhhhh!
You gave me something to spend the whole evening with!
Thanks!

Vipers! Vipers! LOTS OF VIPERS IN MY SIM!
I reached [fltsim.1011] in the F-16C Aircraft.cfg file!

1011
Are you sure you can see all of them?
I beleaved that the maximum allowed was 256!

BTW...go to download...

bismarck wrote:1011
Are you sure you can see all of them?
I beleaved that the maximum allowed was 256!

BTW...go to download...

That is a myth that has persisted for years and debunked many times.

bismarck wrote:1011
Are you sure you can see all of them?
I beleaved that the maximum allowed was 256!

BTW...go to download...

Don't know... so far, I had more than 900 and I could see them. This is the first time I get over 1000 entries... let's see!

Gentlemen, they work! I can see them all!

james84 wrote:Gentlemen, they work! I can see them all!

Cool! I have a few folders where I stopped adding entries at 199. Now I will go and combined then.

The mentioned limitation was due to ACA2005 not to FS itself

There was a limit to ACA2005 because of the alleged limit in FS9, however later versions have that limit either removed or you can ignore the limit at your choice.

Hi all,

Wonderfull pack again! Great to fly in the Southwest again. I do have a question, but maybe this is an inappropriate place to ask. The screenshot on the instructions shows also C-5 Galaxies at Kelly. Did I miss something in this package? Or is this something you guys been working on for another pack? Or is there allready a Galaxy pack availabe that I miss?

Best regards,

Arjan

Not part of this package, part of an upcoming package.

Yeeehaaaa! Can't wait!

Wonderful...I had the same question about the Galaxies lurking in the background of the readme.

I am having a problem with this package. I did a scan with ACA2005 and it pointed out that Traffic_MAIW_SWANG.bgl is missing the following aircraft entries:

CFG File Aircraft Error
Traffic_MAIW_SWANG.bgl MAIW_HTAI_F16C_UAEAF_AZ_00-3028 (#AC2) Aircraft in Flightplan not present
Traffic_MAIW_SWANG.bgl MAIW_HTAI_F16C_UAEAF_AZ_00-3029 (#AC3) Aircraft in Flightplan not present
Traffic_MAIW_SWANG.bgl MAIW_HTAI_F16C_UAEAF_3030 (#AC4) Aircraft in Flightplan not present
Traffic_MAIW_SWANG.bgl MAIW_HTAI_F16C_UAEAF_3031 (#AC5) Aircraft in Flightplan not present
Traffic_MAIW_SWANG.bgl MAIW_HTAI_F16C_UAEAF_3032 (#AC6) Aircraft in Flightplan not present
Traffic_MAIW_SWANG.bgl MAIW_HTAI_F16C_UAEAF_3033 (#AC7) Aircraft in Flightplan not present
Traffic_MAIW_SWANG.bgl MAIW_HTAI_F16C_UAEAF_3034 (#AC8) Aircraft in Flightplan not present
Traffic_MAIW_SWANG.bgl MAIW_HTAI_F16D_UAEAF_AZ_00-3010 (#AC10) Aircraft in Flightplan not present
Traffic_MAIW_SWANG.bgl MAIW_HTAI_F16C_USAF_AZ_87-0361 (#AC15) Aircraft in Flightplan not present
Traffic_MAIW_SWANG.bgl MAIW_HTAI_F16C_USAF_AZ_88-0417 (#AC16) Aircraft in Flightplan not present
Traffic_MAIW_SWANG.bgl MAIW_HTAI_F16C_USAF_AZ_88-0427 (#AC17) Aircraft in Flightplan not present
Traffic_MAIW_SWANG.bgl MAIW_HTAI_F16C_USAF_AZ_90-0720 (#AC30) Aircraft in Flightplan not present
Traffic_MAIW_SWANG.bgl MAIW_HTAI_F16C_USAF_AZ_90-0741 (#AC31) Aircraft in Flightplan not present
Traffic_MAIW_SWANG.bgl MAIW_HTAI_F16C_USAF_AZ_83-1135 (#AC47) Aircraft in Flightplan not present
Traffic_MAIW_SWANG.bgl MAIW_HTAI_F16C_USAF_AZ_83-1144 (#AC48) Aircraft in Flightplan not present
Traffic_MAIW_SWANG.bgl MAIW_HTAI_F16C_USAF_AZ_83-1148 (#AC49) Aircraft in Flightplan not present
Traffic_MAIW_SWANG.bgl MAIW_HTAI_F16C_USAF_AZ_84-1216 (#AC50) Aircraft in Flightplan not present
Traffic_MAIW_SWANG.bgl MAIW_HTAI_F16C_USAF_AZ_84-1237 (#AC51) Aircraft in Flightplan not present
Traffic_MAIW_SWANG.bgl MAIW_HTAI_F16C_USAF_AZ_84-1247 (#AC52) Aircraft in Flightplan not present
Traffic_MAIW_SWANG.bgl MAIW_HTAI_F16C_USAF_AZ_84-1258 (#AC53) Aircraft in Flightplan not present
Traffic_MAIW_SWANG.bgl MAIW_HTAI_F16C_USAF_AZ_84-1271 (#AC54) Aircraft in Flightplan not present
Traffic_MAIW_SWANG.bgl MAIW_HTAI_F16C_USAF_AZ_84-1282 (#AC55) Aircraft in Flightplan not present
Traffic_MAIW_SWANG.bgl MAIW_HTAI_F16C_USAF_AZ_84-1284 (#AC56) Aircraft in Flightplan not present
Traffic_MAIW_SWANG.bgl MAIW_HTAI_F16C_USAF_AZ_84-1285 (#AC57) Aircraft in Flightplan not present
Traffic_MAIW_SWANG.bgl MAIW_HTAI_F16C_USAF_AZ_84-1312 (#AC58) Aircraft in Flightplan not present
Traffic_MAIW_SWANG.bgl MAIW_HTAI_F16C_USAF_AZ_84-1318 (#AC59) Aircraft in Flightplan not present
Traffic_MAIW_SWANG.bgl MAIW_HTAI_F16C_USAF_AZ_84-1375 (#AC60) Aircraft in Flightplan not present
Traffic_MAIW_SWANG.bgl MAIW_HTAI_F16C_USAF_AZ_84-1383 (#AC61) Aircraft in Flightplan not present
Traffic_MAIW_SWANG.bgl MAIW_HTAI_F16C_USAF_AZ_84-1385 (#AC62) Aircraft in Flightplan not present
Traffic_MAIW_SWANG.bgl MAIW_HTAI_F16C_USAF_SA_87-0235 (#AC136) Aircraft in Flightplan not present
Traffic_MAIW_SWANG.bgl MAIW_HTAI_F16C_USAF_SA_87-0248 (#AC137) Aircraft in Flightplan not present
Traffic_MAIW_SWANG.bgl MAIW_HTAI_F16C_USAF_SA_87-0253 (#AC138) Aircraft in Flightplan not present
Traffic_MAIW_SWANG.bgl MAIW_HTAI_F16C_USAF_SA_87-0255 (#AC139) Aircraft in Flightplan not present
Traffic_MAIW_SWANG.bgl MAIW_HTAI_F16C_USAF_SA_87-0256 (#AC140) Aircraft in Flightplan not present
Traffic_MAIW_SWANG.bgl MAIW_HTAI_F16C_USAF_SA_87-0264 (#AC141) Aircraft in Flightplan not present
Traffic_MAIW_SWANG.bgl MAIW_HTAI_F16C_USAF_SA_87-0285 (#AC142) Aircraft in Flightplan not present
Traffic_MAIW_SWANG.bgl MAIW_HTAI_F16C_USAF_SA_87-0286 (#AC143) Aircraft in Flightplan not present
Traffic_MAIW_SWANG.bgl MAIW_HTAI_F16C_USAF_SA_87-0339 (#AC144) Aircraft in Flightplan not present
Traffic_MAIW_SWANG.bgl MAIW_HTAI_F16C_USAF_SA_87-0341 (#AC145) Aircraft in Flightplan not present
Traffic_MAIW_SWANG.bgl MAIW_HTAI_F16C_USAF_SA_87-0344 (#AC146) Aircraft in Flightplan not present
Traffic_MAIW_SWANG.bgl MAIW_HTAI_F16C_USAF_SA_88-0409 (#AC147) Aircraft in Flightplan not present
Traffic_MAIW_SWANG.bgl MAIW_HTAI_F16D_USAF_SA_86-0049 (#AC148) Aircraft in Flightplan not present

I do not see corresponding texture folders or entries in my install. Any ideas?

I tried a re-install but ACA2007Light indicates :

C:\Program Files\Microsoft Games\Flight Simulator 9\aircraft\MAIW_HTAI_F-16C SWANG [fltsim.0] is missing
C:\Program Files\Microsoft Games\Flight Simulator 9\aircraft\MAIW_HTAI_F-16C SWANG fltsim number between 33 and 52 is missing
C:\Program Files\Microsoft Games\Flight Simulator 9\aircraft\MAIW_HTAI_F-16D SWANG [fltsim.0] is missing
C:\Program Files\Microsoft Games\Flight Simulator 9\aircraft\MAIW_HTAI_F-16D SWANG fltsim number between 9 and 11 is missing

When I use renum.exe to correct these problems and I back to the problem above.

I have an idea. see if any of the [fltsim.x] entries are coded [Fltsim.x] I have a feeling that the latest versions of ACA2005 throw a wobbly at that. If so alter them to the lower case 'f' and then try Renum again.

Renum will not alter the case this it just ignores them. If you ran this first then it could be that this screwed everything up.

Here is what I did :

Re-installed SWANG package
Opened both F-16C/D aircraft.cfg's and changed all Fltsim.x w fltsim.x
Re-ran renum.exe

Re-ran ACA2007 Lite and got this :

No errors found

So far so good

Re-ran ACA2005 and checked for 'aircraft in flightplan but not in FS' and got this :

No errors!

Problem re-solved. Thank you for your help!

Very happy you are sorted now Jerel, but im not sure why you had the issue. Im using the latest ACA2005 and have not changed the case on the flightsim entries and all is sweet.



Anyhow glad your running now.

Mark

Well, my theory is that out of habit he runs Renum first. That is fine unless there are 'F's instead of 'f''s. The renumber goes awry and that is when you get the problem.
I get that sort of thing all the time, I only figured it out as I spent all of yesterday evening manually altering all the titles and scheme names and putting them into combined folders and I got the same error.