• There seems to be an up tick in Political commentary in recent months. Those of us who are long time members of the site we know that Political and Religious content has been banned for years. Nothing has changed. Please leave all political and religiours commentary out of the fourms.

    If you recently joined the forums you were not presented with this restriction in the terms of service. This was due to a conversion error when we went from vBulletin to Xenforo. We have updated our terms of service to reflect these corrections.

    Please note any post refering to a politicion will be considered political even if it is intended to be humor. Our experience is these topics have a way of dividing the forums and causing deep resentment amoung members. It is a poison to the community. We apprciate compliance with the rules.

    The Staff of SOH

  • Server side Maintenance is done. We still have an update to the forum software to run but that one will have to wait for a better time.

NAS Alameda, CA KNGZ for FSX

NAS Alameda roundtrip NAS North Island

Got back to flying tonight in my HU-16 Albatross (freeware) It was made for FS9 but works great in FSX with exceptions in the panel. Using FSPS I replaced all the FS98 gauges and some shouldn't be modern gauges with FSX gauges and the panel works great. It has both a nice 2D panel (pilot and copilot) and also a semi-functional VC pilot and copilot. The VC is really nice looking but no where near as good as Virtavia's. I may break down in a couple weeks and get that one. Here are some shots from tonight's flight.

This is us taxiing to Runway 31 to take off at 1730 PST.

attachment.php


Here we are in front of Hanger 20 shut down for the night. Notice the Beacon in the background.

attachment.php


This is Google Earth of Oakland Estuary North side docks which I want to try and add for V3.0

attachment.php
 

Attachments

  • Image_160410_000425.jpg
    Image_160410_000425.jpg
    17.5 KB · Views: 2
  • Image_160409_203217.jpg
    Image_160409_203217.jpg
    64.5 KB · Views: 2
  • Image_160409_150049.jpg
    Image_160409_150049.jpg
    121.6 KB · Views: 2
Regarding AI traffic tools of various sorts, here's a 'sneaky' for you:

AIFP uses the same three text files that people who use/used TTools are used to - namely Aircraft, Airports and Flightplans. They're even in the same formats.
Simply decompile your FS9 flightplans, and move the three files into AIFP's Flightplans subdirectory.

Once they're there, you can edit them manually, or open them in AIFP and edit them there.
You can then validate and compile for FSX (using AIFP) when you're ready.

Simples!

Dave
 
What a pretty shot!!! I operated with VF-96 aboard USS AMERICA, CVW-9 in 1970 with this exact aircraft. Tracked her for many hours, many days of AIROPS as AW on CARDIV2 staff. What texture file, the hanger? Not sure why.

Richard

I still don't have the texture for that hangar. Which model hangar is that? I'll have to play 'hunt the texture'.

Dave
 
This is all well and good but if you don't have any FS9 flight plans then this is all moot for FSX users I would think.....:engel016:


Regarding AI traffic tools of various sorts, here's a 'sneaky' for you:

AIFP uses the same three text files that people who use/used TTools are used to - namely Aircraft, Airports and Flightplans. They're even in the same formats.
Simply decompile your FS9 flightplans, and move the three files into AIFP's Flightplans subdirectory.

Once they're there, you can edit them manually, or open them in AIFP and edit them there.
You can then validate and compile for FSX (using AIFP) when you're ready.

Simples!

Dave
 
I don't use/have FS9 anymore so how in sam hill do you manage to use Traffic Tools? It flat out don't reconginse anything FSX related.
I pointed it to my FSX folder and I think it said....you gotta be kidding :biggrin-new:

Maybe I misunderstood what you said.

ttools.jpg
Butch,

In your case I would create a desktop folder and call it something like Traffic Files. Then I would change the default TTools paths for your Source Files and FS2004 Traffic Files to this Traffic Files folder. This will separate TTools from FSX and allow it to function properly.

Now create your Airport_XXXX.txt, Aircraft_XXXX and Flightplans_XXXX.txt files for FS2004 and save them in this folder. Then use TTools to compile these into a Traffic_XXXX.bgl file for FS2004.

Now open AIFP, open this FS2004 Traffic_XXXX.bgl file in AIFP, set the Target Version to FSX and compile it with the Compiled Path set to your desktop Traffic Files folder.

Voila, now you will find a new Traffic_XXXX_FSX.bgl file in your desktop Traffic Files folder which you can move to an appropriate FSX scenery folder. Personally I place all my Traffic_XXXX_FSX.bgl files in the scenery folder for whatever Addon Scenery the particular AI aircraft are based at. In your case if you have followed Richard's installation instructions that would be your FSX Addon Scenery/scenery folder.

Good luck,
 
I am trying out your suggestion but have to ask about the naming conventions you used for these dummy files.
Airport_XXXX.txt, Aircraft_XXXX and Flightplans_XXXX.txt << Do I create these txt files and save them exactly as you have it or is there some numbers in the XXX's

I have TT tools almost fooled or gamed but it won't pull up the 3rd file to compile. I think it is the Airport_XXXX.txt - so it is stuck for now.

tools.jpg


Butch,

In your case I would create a desktop folder and call it something like Traffic Files. Then I would change the default TTools paths for your Source Files and FS2004 Traffic Files to this Traffic Files folder. This will separate TTools from FSX and allow it to function properly.

Now create your Airport_XXXX.txt, Aircraft_XXXX and Flightplans_XXXX.txt files for FS2004 and save them in this folder. Then use TTools to compile these into a Traffic_XXXX.bgl file for FS2004.

Now open AIFP, open this FS2004 Traffic_XXXX.bgl file in AIFP, set the Target Version to FSX and compile it with the Compiled Path set to your desktop Traffic Files folder.

Voila, now you will find a new Traffic_XXXX_FSX.bgl file in your desktop Traffic Files folder which you can move to an appropriate FSX scenery folder. Personally I place all my Traffic_XXXX_FSX.bgl files in the scenery folder for whatever Addon Scenery the particular AI aircraft are based at. In your case if you have followed Richard's installation instructions that would be your FSX Addon Scenery/scenery folder.

Good luck,
 
As encouragement, i thought i'd post some shots of what you can achieve with ai,
Ive tweak'd the ADEX file for my own use, adding parking and connected up the taxiway-runway links, found some FS9 A-7's that work fine in FSX from the Owls nest, made up a quick and dirty traffic file for 10 aircraft, with 2 aircraft performing touch and go's for a couple of hours.
Ive also converted the Alphasim FS9 Skywarrior to static using SAMM, also running it through MDLX for better frame's. not the right unit markings but i'll figure that out later.
And if you have Henrik's Global AI Ship Traffic V1 installed, Alameda is a great place for ship spotting.

cheers ian


 
Maybe this will help, ive included the complete traffic file and the 3 components, Aircraft, Airports and Flightplans, maybe studying these will answer some questions, this is a FS9 traffic file so you must run it through AIFP first before using it in sim.
 
I am trying out your suggestion but have to ask about the naming conventions you used for these dummy files.
Airport_XXXX.txt, Aircraft_XXXX and Flightplans_XXXX.txt << Do I create these txt files and save them exactly as you have it or is there some numbers in the XXX's

I have TT tools almost fooled or gamed but it won't pull up the 3rd file to compile. I think it is the Airport_XXXX.txt - so it is stuck for now.



tools.jpg
Butch,

The XXXX in the text file names was intended to indicate where whatever name that you wanted your traffic file to be named would go. In other words something like Airports_NAS_Alameda.txt, Aircraft_NAS_Alameda.txt and Flightplans_NAS_Alameda.txt. These files should not be dummy files, but should contain your prioperly formatted lists of Airports, AI Aircraft and Flighplans respectively which will be used to compile your Traffic_Nas_Alameda.bgl FS2204 file with TTools that you will then recompile into your Traffic_Nas_Alameda_FSX.bgl file with AIFP.

Below are a set of the simple text files that I compiled first with TTools to create my FS2004 Traffic_AI_Appearance_Test.bgl file and then recompiled with AIFP to create my Traffic_AI_Appearance_Test_FSX.bgl file that I used to test for the appearance of HTAI F16D USAF_VT_134_86-0046 at my FSX VT ANG base at my local Burlington IAP while I was developing it.

My Airports_AI_Appearance_Test.txt file included the following:

KBTV,N44* 28.23',W73* 9.18',331

My Aircraft_AI_Appearance_Test.txt file included the following:

AC#1,536,"HTAI F16D USAF_VT_134_86-0046"

My Flightplans_AI_Appearance_Test.txt file included the following:

AC#1,1,30%,24Hr,VFR,13:00:00,13:27:40,240,F,1,KBTV,18:30:00,18:57:40,210,F,1,KBTV

My compiled Traffic_AI_Appearance_Test_FSX.bgl file simply had the VT ANG HTAI F-16D fly one VFR circuit around Rwy 15/33 at Burlington IAP at 13:00Z and again at 18:30Z.

I hope this helps. :encouragement:
 
Sorry I didn't get to this sooner...here is the Dropbox link to the airport file with that DC-3 removed from being buried on the apron. I decided that I will let you place your own static aircraft scenery / ai aircraft and stick to the airport. There seems to be enough other guys who know a lot more about that than I do.

https://www.dropbox.com/s/qwppn6a5ke447k3/NAS%20Alameda%20V24.zip?dl=0

I also remembered after snapping on Google Earth last night and posting that photo what TARPSBIRD said about the Google Earth Clock Slider and "slid" back to 1993 which gives me a much more accurate picture to work on the scenery continuation of NAS Alameda and the Port Of Oakland across the Estuary. It shows as you can see below a whole different port area with warehouses not container parks. That is the way I am going to do it for us. Will be working on that this week since I am having so much fun with the airport and with you guys.

attachment.php
 

Attachments

  • 1993 Port Of Oakland.jpg
    1993 Port Of Oakland.jpg
    98.6 KB · Views: 5
Butch,

I think the KNGZ.zip attachment in Ian's last post will probably be of the most value to you since it pertains directly to NAS Alameda. :encouragement:
I'll now get back to blowing things up with my newly acquired Milviz F-86F-30 with Tacpack integration. :ernaehrung004:

Good Luck,
 
What Can Be Done

As encouragement, i thought i'd post some shots of what you can achieve with ai,
Ive tweak'd the ADEX file for my own use, adding parking and connected up the taxiway-runway links, found some FS9 A-7's that work fine in FSX from the Owls nest, made up a quick and dirty traffic file for 10 aircraft, with 2 aircraft performing touch and go's for a couple of hours.
Ive also converted the Alphasim FS9 Skywarrior to static using SAMM, also running it through MDLX for better frame's. not the right unit markings but i'll figure that out later.
And if you have Henrik's Global AI Ship Traffic V1 installed, Alameda is a great place for ship spotting.

cheers ian



I am so glad that everyone here is enjoying my efforts so much. You have done a really great job Ian.
 
VF-24 at KNGZ

I was also attached to this Mig Killer outfit embarked on the USS Hancock and USS Bonnie Dick. I was with ordnance team (65-67) when we got the mig kills.
VF-24 was home based at NAS Miramar CA.

VF24.jpg


VF_24_1.jpg
 
Thanks Ian,
I will run this thru the ringer (AIFP) first and then she how it works. :engel016:


Maybe this will help, ive included the complete traffic file and the 3 components, Aircraft, Airports and Flightplans, maybe studying these will answer some questions, this is a FS9 traffic file so you must run it through AIFP first before using it in sim.



EDIT I don't have the A7 that you used for the traffic bgl so nothing was compiled.
 
Last edited:
Back
Top