Hi guys,
I am hoping that someone can help me out with a problem that is just driving me nuts. I have installed Keith Guillory's KDLF/2DLF AFCADS and traffic file (available on AVSIM & Flightsim). T6 traffic appears on the 2DLF ramp, taxis to the runway but never takes off; T1 and T38 traffic never appears on the KDLF ramp and arriving T1s disappear immediately after landing as if there is no available parking (haven't seen any base T38 traffic yet!). Visiting T38 aircraft from the MAIW Holloman package appear on the KDLF ramp, taxi and take off normally although I did notice that they just ran straight through the T6s holding short of the runway. My T1, T6 and T38 aircraft act fine at other airbases. I have checked FP aircraft text files and aircraft cfg files and can see nothing wrong; Aircraft Analyzer 2005 shows no faults. AFCAD fault finder reports no faults.
Has anyone had a similar experience with this or any other AFCAD scenery? Any ideas on what may be wrong - probably something really simple that I have missed?
cheers,
Geoff
LAUGHLIN AFB AFCADS
-
ronniegj
Sounds to me like you might have two AFCADS. I recently found that the addon scenery/scenery file may not necessarily be the only location to check for extra AFCADS to reside. Any addon scenery my have the AFCAD in a subfolder that you will need to check. I especially found that MEGAScenery/City has AFCADS in a folder other than scenery folder that has had an effect on my AI. In the megacity Atlanta for example, in a folder ALTobjects/scenery, there were AFCADS that caused multi AFCAD problems. I removed the AFCAD to a holding folder outside of the FS folder and cleared up my problems. You have to try and see in such a case, as it is necessary that the AFCAD you use matches up to the scenery or you'll have a/c taxing thru buildings etc.
If this has been cleared up, then you may want to check the active AFCAD to see if there are holdshort points missing as this will cause the a/c to taxi out and stop at the edge of the runway, but never request clearance to take off, and just sit there until they disappear.
If this doesn't clear it up, then perhaps a more knowledgeable person will comment.
Ron
If this has been cleared up, then you may want to check the active AFCAD to see if there are holdshort points missing as this will cause the a/c to taxi out and stop at the edge of the runway, but never request clearance to take off, and just sit there until they disappear.
If this doesn't clear it up, then perhaps a more knowledgeable person will comment.
Ron
Guys here is a great utility that everyone should have:
http://library.avsim.net/esearch.php?Ca ... DLID=45600
Called Scan AFD, it scans your FS9 folders looking for duplicate AFCAD files and then lists the ones it finds, allowing you to delete the duplicates.
Works great.
http://library.avsim.net/esearch.php?Ca ... DLID=45600
Called Scan AFD, it scans your FS9 folders looking for duplicate AFCAD files and then lists the ones it finds, allowing you to delete the duplicates.
Works great.
-Mike G.
Recovering flight sim addict, constant lurker.
Check out my real life RV-8 build here: RV-8 Builder Log
Recovering flight sim addict, constant lurker.
Check out my real life RV-8 build here: RV-8 Builder Log
-
scottr5213
- Captain
- Posts: 393
- Joined: 07 Dec 2006, 03:33
- Version: FS9
- Location: Atlanta Ga
-
Cianofranc
- Captain
- Posts: 204
- Joined: 17 Aug 2006, 08:53
- Version: FS9
- Location: Italy
-
ronniegj
Just a thought, if the folders in your copy of Windows/FS are not the same as the English versions of same, and if the SCAN AFCAD program was not written to take that into consideration, that could cause a problem. Else, try re-downloading and re-installing. BTW, I use the program, an altho it is very good, the reason I mentioned the MegaScenery/City thing in my example, is because the ScanAfcad did not find those, I just stumbled on those by accident, so nothing can be considered as perfect. I always check using both programs, sometimes twice or more, before I can track down a problem.
BTW for geoffj: the fault finder in AFCAD does not point out missing holdshort nodes, only ones that are located too far from the runway, so be sure to check for that.
Ron
BTW for geoffj: the fault finder in AFCAD does not point out missing holdshort nodes, only ones that are located too far from the runway, so be sure to check for that.
Ron
I know it can do a lot more than just check for duplicate afcads, but you could always check out Peter van der Veen's ACA2005 utility. It is marvelous for diagnosing all sorts of FS9 problems.
Steve
_______________________________________________________
Quid Si Coelum Ruat
_______________________________________________________
_______________________________________________________
Quid Si Coelum Ruat
_______________________________________________________
Laughlin AFB AFCADS
Hi guys,
Many thanks for all your responses. As mentioned in my first post I already use ACA2005. It has an AFCAD scanner which I use each time I install scenery, aircraft etc. I have also downloaded ScanAFD as suggested, 2 programmes to check for faults is better than one! I have also done an extensive manual check of my FS9 folders (I do not have any payware US scenery) just a few freeware addons. There are no duplicate AFCADS.
Still scratching my head!!
Geoff
Many thanks for all your responses. As mentioned in my first post I already use ACA2005. It has an AFCAD scanner which I use each time I install scenery, aircraft etc. I have also downloaded ScanAFD as suggested, 2 programmes to check for faults is better than one! I have also done an extensive manual check of my FS9 folders (I do not have any payware US scenery) just a few freeware addons. There are no duplicate AFCADS.
Still scratching my head!!
Geoff
For Ronniegj
Many thanks for the tip about hold short node errors. There were some nodes outside of the radius limits and I have adjusted these. However, still the same problems. Just to clarify what is happening with the T6s, one aircraft receives permission to take off, lines up and just sits there; subsequent ac hold short and disappear after the default time.
cheers,
Geoff
Many thanks for the tip about hold short node errors. There were some nodes outside of the radius limits and I have adjusted these. However, still the same problems. Just to clarify what is happening with the T6s, one aircraft receives permission to take off, lines up and just sits there; subsequent ac hold short and disappear after the default time.
cheers,
Geoff
Sorry, missed the bit about you already using ACA2005.
Now re-read properly your first post and something is immediately obvious. You do have duplicate afcads. KDLF and 2DLF. The T6's only use 2DLF, so there is something wrong with that afcad. The reason why the T-38's taxy through the T-6's is because they are completely separate bases so they ignore them. I will download the package and see if I can spot the problem.
Now the Holloman T-38's work ok, which says that the KDLF afcad is ok. The problems with the Laughlin Base aircraft appear to be aircraft based. Can you tell me which aircraft you are using?, and can you tell me whether you are using the bgl file supplied or whether you have amended the supplied text files?
If you have amended the text files could you zip them up and send them to me, along with the aircraft.cfg files of the aircraft that you are having problems with.
I will then take a look at your problems.
Now re-read properly your first post and something is immediately obvious. You do have duplicate afcads. KDLF and 2DLF. The T6's only use 2DLF, so there is something wrong with that afcad. The reason why the T-38's taxy through the T-6's is because they are completely separate bases so they ignore them. I will download the package and see if I can spot the problem.
Now the Holloman T-38's work ok, which says that the KDLF afcad is ok. The problems with the Laughlin Base aircraft appear to be aircraft based. Can you tell me which aircraft you are using?, and can you tell me whether you are using the bgl file supplied or whether you have amended the supplied text files?
If you have amended the text files could you zip them up and send them to me, along with the aircraft.cfg files of the aircraft that you are having problems with.
I will then take a look at your problems.
Steve
_______________________________________________________
Quid Si Coelum Ruat
_______________________________________________________
_______________________________________________________
Quid Si Coelum Ruat
_______________________________________________________
-
ronniegj
I had a similar problem surface the other day. It turned out that there were two taxiways going to the end of the runway, but one terminated directly on the runway, while the other (the problem one) met the runway link back in the over/under run portion of the runway. I got it working by highlighting the portion of the runway link between the node where the one taxiway terminated on the runway and the node where the other taxiway terminated on the link on the over/under run area. I then right clicked and selected properties and changed that short link from runway to taxiway, making the taxiway proceed on the runway until outside the over/under run area. This cleared up my problem, and might do so for you as well!
Ron
Ron
I am working on a replacement for my original AF2 for Laughlin.
So far it will be just 1 AFCAD2 facility not 2 as the previous versions.
There will be common radio frequencies. This should cure the taxiway conflicts. I will not provide new flightplans just yet. I might seek collaboration on this area later. If anyone desires to use the existing flightplans referring to 2DLF, you will need to run a replace all from 2DLF to KDLF.
Several years ago the best solution for what I wanted to accomplish with multiple runways and dissimilar aircraft using the same airfield was to create a condition in which T-6As would only use the shortest runway 13R/31L and the T-1s and T-38s would operate on the two longer runways. At the time of building up these AF2s, I had to accept my own limitations and try to minimize the problem areas to the best of my abilities. Thus, providing the best junk I could deliver at that time.
On my first early test of my rework KDLF, T-6s to go to Rwy 13R/31L based on runway length. In order to trick the Texans into using the short runway, I made the active about 4800 ft and it sits carefully along the original runway surfaces to round-out the visual rightness of this airfield. As a result the T-6s start short on the runway and make long runway touchdowns. This beats the other alternatives I had. The markings have been carefully applied to the runway surface. The designator numbers had to be removed, but this is much better than the original. At the same time I observed a T-38 taxiing to Rwy 31C without problems. So far none of the AI aircraft stall out at the holdshort areas or disappear. More to follow. I did have to change the T-6A aircraft.cfg file to change the previously used T-6A from engine type=1 (jet) to engine type=5 turboprop. This was factored into the short runway considerations.
More to follow.
Keith
So far it will be just 1 AFCAD2 facility not 2 as the previous versions.
There will be common radio frequencies. This should cure the taxiway conflicts. I will not provide new flightplans just yet. I might seek collaboration on this area later. If anyone desires to use the existing flightplans referring to 2DLF, you will need to run a replace all from 2DLF to KDLF.
Several years ago the best solution for what I wanted to accomplish with multiple runways and dissimilar aircraft using the same airfield was to create a condition in which T-6As would only use the shortest runway 13R/31L and the T-1s and T-38s would operate on the two longer runways. At the time of building up these AF2s, I had to accept my own limitations and try to minimize the problem areas to the best of my abilities. Thus, providing the best junk I could deliver at that time.
On my first early test of my rework KDLF, T-6s to go to Rwy 13R/31L based on runway length. In order to trick the Texans into using the short runway, I made the active about 4800 ft and it sits carefully along the original runway surfaces to round-out the visual rightness of this airfield. As a result the T-6s start short on the runway and make long runway touchdowns. This beats the other alternatives I had. The markings have been carefully applied to the runway surface. The designator numbers had to be removed, but this is much better than the original. At the same time I observed a T-38 taxiing to Rwy 31C without problems. So far none of the AI aircraft stall out at the holdshort areas or disappear. More to follow. I did have to change the T-6A aircraft.cfg file to change the previously used T-6A from engine type=1 (jet) to engine type=5 turboprop. This was factored into the short runway considerations.
More to follow.
Keith
Keith, Steve and guys,
Many thanks for all the posts in response to my plea for help! As per Steve's post, if my ac are working at other airfields it is likely that those files that I added to get Laughlin busy are the problem. I have uninstalled and reinstalled the T38 files (for the FSD model) and I now have the Laughlin T38 traffic flying, taxiing and parking as expected. I am going to do the same with the T6 and T1 files and see if this works before troubling anyone again!
Steve,
Many thanks for the offer to look over files and I will certainly take you up on that if this does not work out. Going to be busy for a few days so may be start of next week before I can go fly!
Keith,
Many thanks for the work on the AFCADs and good luck with updates.
Geoff
Many thanks for all the posts in response to my plea for help! As per Steve's post, if my ac are working at other airfields it is likely that those files that I added to get Laughlin busy are the problem. I have uninstalled and reinstalled the T38 files (for the FSD model) and I now have the Laughlin T38 traffic flying, taxiing and parking as expected. I am going to do the same with the T6 and T1 files and see if this works before troubling anyone again!
Steve,
Many thanks for the offer to look over files and I will certainly take you up on that if this does not work out. Going to be busy for a few days so may be start of next week before I can go fly!
Keith,
Many thanks for the work on the AFCADs and good luck with updates.
Geoff
I just exchanged a PM with Steve on this. I attempted several other solutions and for a short time got pretty close to a fix with a ghost runway as texture under a shorter Rwy 13R/31L to prevent AI from sending jets to this runway. It creates an unusually short takeoff run as the T-6s go to taxiway D instead of E for Rwy 31L departures, due to the rwy link being related to a shorter (4988ft) runway instead of the 6246ft original. Of course the full 6246 appears on the ground but I no longer call the link for this surface by the same name. I can still do some adjustments that came to my mind as I am writing this because on the other side never reached the holdshort line so the T-6s just sat there. This solution resulted in adversities that were considerably worse than the first version. The other problem associated with this change is that if the T-6 has engine data for Jet instead of turboprop, the T-6 will never go to the short runway.
If nothing else works, I might just have to settle for the 2 ICAOs and overlaid airfields. I would prefer to have one common ICAO and common frequencies.
Also chatting with Steve and looking at this base on Google Earth, it looked as if the center runway was been demolished. However, there are current NOTAMS pertaining to operations to Rwy 13/31C. Altogether, I appreciate everyone's interest in this base and my attempts to make it the best possible. I have re-worked some problems I had with radio frequencies and will go into the XML code for this facility and recode the taxiways. In the existing default and mod, the taxiways are all generic. Once you write the taxiway names into the XML and recompile back to a bgl, you can label them accordingly in AFCAD2.
Thanks!
Keith
If nothing else works, I might just have to settle for the 2 ICAOs and overlaid airfields. I would prefer to have one common ICAO and common frequencies.
Also chatting with Steve and looking at this base on Google Earth, it looked as if the center runway was been demolished. However, there are current NOTAMS pertaining to operations to Rwy 13/31C. Altogether, I appreciate everyone's interest in this base and my attempts to make it the best possible. I have re-worked some problems I had with radio frequencies and will go into the XML code for this facility and recode the taxiways. In the existing default and mod, the taxiways are all generic. Once you write the taxiway names into the XML and recompile back to a bgl, you can label them accordingly in AFCAD2.
Thanks!
Keith
-
Victory103
- Colonel
- Posts: 4073
- Joined: 13 Aug 2007, 03:35
- Version: P3D
- Location: KPHX
Yes I know well over a year since last post. Just today had a Laughlin T-1 in the pattern with me at GRK(Ft. Hood AAF-Killeen Regn). Since we have some nice AETC MAIW packages (Sheppard,Columbus,Vance), I thought I would get Laughlin (KDLF) going with T-1/6/38's. Anyone ever do a Laughlin (XL) repaint for the T-38?
I've got the T-1's, and the non-AI T-6's already.
I've got the T-1's, and the non-AI T-6's already.
DUSTOFF
ARMY PROPS
NAVY SAR
-Chris
ARMY PROPS
NAVY SAR
-Chris
T-38
There are some repaints for the XL T-38s. Don;t remember from where I picked them up, if you want them, I can send them to you. It uses Jakes T-38 ai fantastic model.
Tail #'s
XL_61-3186
XL_65-338
XL_68-217
XL_70-564
XL_65-461
XL_68-152
XL_70-568
Tail #'s
XL_61-3186
XL_65-338
XL_68-217
XL_70-564
XL_65-461
XL_68-152
XL_70-568
- Attachments
-
- xl152_188.jpg
- (31.86 KiB) Downloaded 377 times
Re: T-38
Those are paints I did and e-mailed to a few people requesting them... they're really not that great as there has been no paint kit published publicly so I just kind of winged it.lewis wrote:There are some repaints for the XL T-38s. Don;t remember from where I picked them up, if you want them, I can send them to you. It uses Jakes T-38 ai fantastic model.
Tail #'s
XL_61-3186
XL_65-338
XL_68-217
XL_70-564
XL_65-461
XL_68-152
XL_70-568
--Chris
T-38's
Good to know or should I say remember from where I aquired those repaints. I looked on any "read me" files included but did not find the author. I will add that info for future reference. Thanks again Chris.
Lewis
PS By the way, as those repaints are the only ones available, they suit the needs, to me, they are as good as they can be.
Lewis
PS By the way, as those repaints are the only ones available, they suit the needs, to me, they are as good as they can be.
-
Victory103
- Colonel
- Posts: 4073
- Joined: 13 Aug 2007, 03:35
- Version: P3D
- Location: KPHX
-
CelticWarrior
- Lieutenant Colonel
- Posts: 1122
- Joined: 15 Aug 2006, 17:16
- Version: FSX
- Location: Llareggub