Military AI Works

This time it's Lajes AB. There are a lot of planes from the MAIW package that stop for fuel at this base, so this scenery should be downloaded by everyone that uses the MAIW packages!

The file name is lpla_j.zip

PS: The scenery is circa 1990

Quick question, when John says the scenery is circa 1990 does he mean he made the airport how it looked in 1990 or is it circa 1990 beacause of the P-3 Orions that come with the scenery?

those P3's are visiting at least they are in my LPLA lajes along with A10,f15,f16,kc135,c130 etc etc and i havn't downloaded the new scenery yet

Thanks for the head's up, Joseph

Is this scenery compatible with the payware REAL AZORES ?

i found 1 issue with this scenery, with all the MAIW traffic thats stops at LPLA, there are only 5 non military parking spots ?

I think the scenery did not include an AFCAD, the MAIW LPLA AFCAD seems slightly off.

Well to semi-solve the afcad issue this is the one that John had in his beta version of his scenery.
I attach this as a courtesy and untouched as I know it is sourced from John. This should not be construed as either my work nor an official MAIW update. Once John reads here, or from direct contact, that there was no afcad with his scenery I am sure he will release an official update should this not be the finished article.

THANK YOU!!!!!!

Thank you .

Is anyone else having problems with this scenery? I installed it in the usual way, but on loading FS9 it would get to 38% (loading terrain) and stop. I thought it might be to do with the mesh file, so I disabled that and restarted only to have the loading stop at 38% again. Any ideas, anyone?

Keith, when you say it stops does it then CTD?
If so its that the global textures have not been put in the right place, Dark_Road.bmp and DarkRoad_LM.bmp into your FS9\Scenery\World\Texture folder.

Check there.

In the read me file John explains why you would be having a CTD.

I loaded this scenery this afternoon and having checked for the correct placement of all files I'm still getting a CTD. Problem is different from Keith though, my crash comes whenever I try to create a flightplan using the inbuilt flightplanner. If I try to create a manual flightplan as soon as I try to zoom into the LPLA area to select VOR/Waypoint/NDB Flightsim crashes.

This scenery has now bee disabled UFN

pete

No problems here with the scenery.

petebramley wrote:I loaded this scenery this afternoon and having checked for the correct placement of all files I'm still getting a CTD. Problem is different from Keith though, my crash comes whenever I try to create a flightplan using the inbuilt flightplanner. If I try to create a manual flightplan as soon as I try to zoom into the LPLA area to select VOR/Waypoint/NDB Flightsim crashes.

This scenery has now bee disabled UFN

pete

This is the second time that I have heard of something like this and to be honest it would never occur to me to check something like this as I don't think I have ever used the FS9 flightplanner, but will have a bash now. This should be a laugh.

...... ...... ...... ...... ...... ......

OK, so now I have checked it and I too get an error, and I don't get it with the scenery disabled. The nature of this seems to mean to me that there must be some conflict with other scenery, maybe even the default afcad. I altered the navaids to correspond exactly with the default afcad and the problem disappeared.
My guess is that at least one of the navaids is far enough out of tolerance so that FS9 sees two navaids with the same characteristics in the same area and blows a fuse.


So in a nutshell today we have at least found another problem that we can fix, if we ever bothered to look for it in the first place.

Firebird wrote:Keith, when you say it stops does it then CTD?
If so its that the global textures have not been put in the right place, Dark_Road.bmp and DarkRoad_LM.bmp into your FS9\Scenery\World\Texture folder.

Check there.

Thank you. That's what caused it. I thought I already had those files in the texture folder but forgot that I hadn't put them back in after a re-install. D'oh!

Cool, so all I need is Pete to confirm that I found a fix for his problem as well.

version 1.1 now on avsim

Mick

Will tip-toe off to Avsim now and D/L Ver 1.1
and report back


Pete