Military AI Works • 65th Aggressor Update Support Thread
Page 1 of 1

65th Aggressor Update Support Thread

Posted: 13 Aug 2013, 01:30
by MIKE JG
Post support related comments for this package in this thread. The Package Manager will look into your problem as soon as possible.

NOTE 1: Keep this thread clean and post ONLY support related comments here. For all other discussions about this package, please reply to the release announcement.

NOTE 2: We will only provide support for bugs in our packages, not for conflicts with other addons in a user's highly modified simulator setup.

NOTE 3: Support for FSX users will not be offered in this thread. Instead FSX community support can be had from other users by posting questions in our "Unofficial Flight Simulator X Forums".

NOTE 4: Elements contained within this package, replace elements from the previous MAIW Nellis AFB AI packages. Please consult the included Readme carefully to prevent file conflicts when you install this package.

Re: 65th Aggressor Update Support Thread

Posted: 13 Aug 2013, 01:44
by MIKE JG
To avoid confusion, this update will swap out the F-15 Aggressor models included with the original release of the MAIW Nellis AFB package with the new KRAI versions including the two blizzard cammo schemes.

The included Nellis AFB airfield file is an AFCAD 2.21 file that is based off of the originally released version from 2009. It has been modified to add overflow parking to allow for the extra F-15 Aggressor models included in this update.

The installer will place this newer KLSV AF2 file inside the FS9/Addon Scenery folder. This is done to prevent the file from accidentally overwriting your current Nellis AFB airfield file.

Once the the installer has finished, you can locate the newer KLSV AF2 file installed in the location listed above. If you want to make use of it, you can simply place it inside the MAIW Nellis AFB (KLSV)/Scenery folder and overwrite the older version.

If you do not want to use it, you can safely store it or delete it. Keep in mind this is an AFCAD 2.21 file that normally would be able to be open and edited with ADE9. However this AF2 file has more than 256 parking spots which will not permit it to be compiled by ADE9 if you are trying to modify it.

The only way to compile the KLSV AF2 file is to use AFCAD. The other option is to delete parking spaces until you reach 256 total spots.

A third option is to make modifications to the KLSV AF2 file using ADE9, remove enough parking spaces until the compiler will work, then go back in with AFCAD 2.21 and finish your modifications. Note there are side effects to trying this method, users are cautioned.

Re: 65th Aggressor Update Support Thread

Posted: 14 Aug 2013, 02:02
by Joseph29
I am keeping the newer Nellis AFCAD, do I need to re name the new AFCAD? The new AFCAD is named updated_MAIW_AF2_KLSV_CUSTOM.bgl and the old AFCAD is named MAIW_AF2_KLSV_CUSTOM.bgl.

Re: 65th Aggressor Update Support Thread

Posted: 14 Aug 2013, 02:43
by MIKE JG
The actual file names are irrelevant, they are for organizational purposes only.

You can name them anything you want to.

Re: 65th Aggressor Update Support Thread

Posted: 15 Aug 2013, 21:30
by 800nates
all textures for all AI civil and military dont show up after this!!! at any airport

Re: 65th Aggressor Update Support Thread

Posted: 15 Aug 2013, 21:47
by Firebird
:?:
That is quite a staggering statement. Considering that the textures for each aircraft are in different folders I can't see how any package can wipe out textures for all aircraft in your FS World.

Are you sure that that this is a package problem?

Re: 65th Aggressor Update Support Thread

Posted: 15 Aug 2013, 21:48
by 800nates
Logged on flew on a new plane i loaded everything was fine Uploaded that then nothing!

Re: 65th Aggressor Update Support Thread

Posted: 15 Aug 2013, 22:14
by Firebird
I don't doubt that you have a problem, but there is no way that every aircraft at every airport can be blank.
The most logical way I could see what you are saying occurring, would mean that something had renamed every single scheme folder on your system from 'texture.' to something else.

Our package does not include any renaming plus everybody that downloaded this would have the same problem.

We will be happy to help you work out both the cause and a solution but this should be done in a thread in the general forum. If you could post there with as much specific information possible we shall see what can be done to help you.

Re: 65th Aggressor Update Support Thread

Posted: 16 Aug 2013, 03:00
by 800nates
Redownloaded Nellis then the 65th Fixed!

Re: 65th Aggressor Update Support Thread

Posted: 16 Aug 2013, 04:47
by Joseph29
I installed the new Nellis traffic file then ran ACA2005 v1.6.6 and it had a few NBAI F-15C's (and one F-15D) listed as "aircraft in flightplan not present in FS"

They are:
MAIW_NBAI_F-15C_USAF_OT_422_83-0018 (ac#47)
MAIW_NBAI_F-15C_USAF_OT_422_80-0014 (ac#50)
MAIW_NBAI_F-15C_USAF_OT_422_81-0030 (ac#51)
MAIW_NBAI_F-15C_USAF_OT_422_83-0037 (ac#52)
MAIW_NBAI_F-15C_USAF_OT_422_80-0040 (ac#53)
MAIW_NBAI_F-15C_USAF_OT_422_84-0012 (ac#54)
MAIW_NBAI_F-15C_USAF_OT_422_81-0063 (ac#55)
MAIW_NBAI_F-15C_USAF_WA_433_78-0438 (ac#333)
MAIW_NBAI_F-15C_USAF_WA_433_78-0434 (ac#334)
MAIW_NBAI_F-15C_USAF_WA_433_80-0002 (ac#335)
MAIW_NBAI_F-15C_USAF_WA_433_82-0009 (ac#336)
MAIW_NBAI_F-15C_USAF_WA_433_82-0014 (ac#337)
MAIW_NBAI_F-15C_USAF_WA_433_82-0018 (ac#338)
MAIW_NBAI_F-15C_USAF_WA_433_83-0012 (ac#339)
MAIW_NBAI_F-15C_USAF_WA_433_83-0019 (ac#340)
MAIW_NBAI_F-15C_USAF_WA_433_83-0027 (ac#341)
MAIW_NBAI_F-15C_USAF_WA_433_83-0041 (ac#342)
MAIW_NBAI_F-15D_USAF_WA_433_83-0050 (ac#343)

I deleted all of the NBAI F-15 Nellis paints, were those not supposed to be deleted? Or were these not deleted when the new Nellis traffic file was made?

Re: 65th Aggressor Update Support Thread

Posted: 16 Aug 2013, 09:38
by RKE
Joseph29 wrote:I deleted all of the NBAI F-15 Nellis paints, were those not supposed to be deleted? Or were these not deleted when the new Nellis traffic file was made?
They weren't supposed to be deleted. Only the 65th Aggressor squadron have been painted for the Kevin Reed model.

Re: 65th Aggressor Update Support Thread

Posted: 16 Aug 2013, 10:18
by Joseph29
RKE wrote:
Joseph29 wrote:I deleted all of the NBAI F-15 Nellis paints, were those not supposed to be deleted? Or were these not deleted when the new Nellis traffic file was made?
They weren't supposed to be deleted. Only the 65th Aggressor squadron have been painted for the Kevin Reed model.
Oh ok, I did not realize Nellis had more than 1 F-15 aggressor squadron. That's why I deleted all of the NBAI Nellis F-15's that I had.

Re: 65th Aggressor Update Support Thread

Posted: 16 Aug 2013, 10:56
by RKE
Only the 65th is an aggressor squadron, the other two are the 422d Test and Evaluation Squadron and the 433d Weapons Squadron :wink: