Military AI Works

This is absolutely incredible work. Thanks to all involved.

Paul

Outstanding job Hartwig.
Can't wait to see it filled with the new JYAI F-35.

Just noticed that the file Traffic_MAIW_USN Airliners_KC-130s_VX-20.bgl duplicates the traffic already included in MAIW USN Airliners Part 3 package.

Thanks, Giorgio

Noticed another problem. I'd like to know if it's just for me.

SH-60 landing at PAX5 pass trough the trees and go to park at PAX4.
A couple of them take-off on Wednesday at 12:55.

It seems that the Runway overview.pdf is wrong.

Giorgio

bismarck wrote: ↑02 Apr 2018, 15:09 Outstanding job Hartwig.
Can't wait to see it filled with the new JYAI F-35.

Just noticed that the file Traffic_MAIW_USN Airliners_KC-130s_VX-20.bgl duplicates the traffic already included in MAIW USN Airliners Part 3 package.

Thanks, Giorgio

Seems I forgot to remove some of the traffic files of other AI packages.
These flightplans are extracted from the USN Airliners package.
I never installed the USN Airliners since the series was never completed until now.
I only installed the PAx River stuff out of it.

bismarck wrote: ↑02 Apr 2018, 16:08 SH-60 landing at PAX5 pass trough the trees and go to park at PAX4.
A couple of them take-off on Wednesday at 12:55.

I will have a look into this.

bismarck wrote: ↑02 Apr 2018, 16:08 It seems that the Runway overview.pdf is wrong.

Looks a little bit mixed up...
...since the last release

bismarck wrote: ↑02 Apr 2018, 16:08 SH-60 landing at PAX5 pass trough the trees and go to park at PAX4.
A couple of them take-off on Wednesday at 12:55.

OK, I can reproduce this issue on my system.
I have an idea what might be the cause of this.
Since I did not change anything on these AFCAD files I did not test them during the update.

I am working on it.

Added Start locations, same problem...

Sorted out.
Sent the modified AFD to Hartwig.

Giorgio

I am currently working on an updated set of AFCAD files to solve a few issues.

With that many AFCAD files covering the same area there seem to be some strange interactions between them.
Some files that were working in the past are showing issues now, mainly aircraft jumping between different AFCAD files.
As Giorgia reported earlier AI aircraft will land on one AFCAD file but then park on a position that is actually on a different AFCAD file.

I’m also having an odd elevation issue between the different AFCADS as well in P3d4. I tried to use the ORBX airport elevation tool, but I now realize that this will have only fixed the main airport file, and not be multiple other AFCADS that are not assigned the standard Airport ICAO code.

-Woog

I did mention in the FSX F-35B manual Woog, that the conversion of Pax for P3Dv4 is not perfect. In FS9, Hartwig has used an elevation of 6.56ft which is below the default and real world value of 39ft, but it works very well. My starting point for FSX/P3Dv4 was the 6.56ft value in each of the 16 AFCADs plus the new CVX flatten, but it caused chasms all lover the airfield. After much experimentation, I settled on the default value of 39ft and changed all the elevations accordingly. That produced a perfectly flat airfield, but with a ridge out to sea on one side. I ran out of ideas at that point.

If you can come up with a different formula, that would be good.

John

It seems maybe I still have some of the AFCADS populating at 6.56’. I did spot the water wall that you mentioned, so some of my install matches your update. I highly doubt that my novice scenery skills will come up with a solution that you professionals haven’t already. One question though: Is there a way to create a custom shaped flatten that matches a vector based coastline? Would something like that pull that water “wall” in tight, and instead give us a more “3d” shoreline? I really don’t know what I’m talking about, just theorizing out loud.

-Woog

You are talking about a new tool from Don Grovestine - Terrain Sculptor It is brand new and has reached beta state recently.

It is supposed to do exactly what you describe above, but I have not had a play with it yet so all I know is from the developer thread at FSDeveloper.

It can be downloaded from Don's web.

From mobile hence short

Here a fix for a little problem I've found during AFCAD tests.
The Italian F-35B had a double mistype in the Title line and in the aircraft.txt of the FP.
In the cfg, it was "Imbarkati" and in the txt it was "Imbakati", so the aircraft didn't fly.
Both corrected with the right word: "Imbarcati"
Just unzip in your FS9 main dir and overwrite.
Don't know if it's the same for FSX/P3D

Giorgio

bismarck wrote: ↑07 Apr 2018, 08:31 ...
The Italian F-35B had a double mistype in the Title line and in the aircraft.txt of the FP.
...
Giorgio

Brent's Beaufort flightplan for the Italian F-35B will also need a fix.
The title line in the aircraft.cfg was changed so now the aircraft.txt of the flighplans do not match anymore.

The fix is for both FP

Giorgio

Hi All

I've reinstalled this package loads of times over the weekend and I'm still having problems. These are to do with scenery objects not showing. I do not have the ski jump and several hangers, Titan, F35 hanger and sun shades etc. I've installed the latest MAIW Global Scenery package. am I missing other libraries? The bgl's are in the scenery folder but I assume I need another library?

The F-35 hangar is part of the original scenery. The object library should be in the scenery folder.
The Triton hangar is from the MAIW airbase objects which is part of the global object libraries, also the sun shades.
The skijump ramp model is embedded in the placements file and is also included in the scenery folder. Its filename should be something like PAX1...obj.bgl.
So beside the global object libraries nothing else is required. Everything should be in the scenery folder.

Sometimes if something complex doesn't work straight away then it is best to go back to the beginning. Sometimes your mind sees what it wants to read rather than what is there. So, you have to reboot your mind.

As Hartwig says, start by making sure that you have the FS9 MAIW Global Libs installed and active.
Then start by installing the original scenery that we released and activating that.

Once done, copy that folder in its entirety - that is your safety backup
Then upgrade the active folder with the Pax River 2015 update, remember that at the moment all you are interested in is the scenery.
Once you are happy with that, copy that active folder, that is your second safety checkpoint.
Finally update the active folder with the Pax River 2018 scenery.

Now the chances are that whatever you were missing the first time you have fixed now. Once you have checked that it is all working, you can add the traffic as per the 2018 update docs, and finally delete the two backup folders.

Thanks guys, I'll do what Steve suggests.

The 2015 package is only required for the AI traffic.
Everything that is required for the scenery is in the 2018 update.