Just a shame that a number of the parking spots in the AFCAD supplied for 'No static aircraft' are not actually linked to the rest of the airfield. Anyone clever up to fixing these?
Alan Robertson wrote:Just a shame that a number of the parking spots in the AFCAD supplied for 'No static aircraft' are not actually linked to the rest of the airfield. Anyone clever up to fixing these?
Hi Alan,
Haven't tested it, but have fixed the isolated parking problem.
Well, you appear to have managed to fix the 'stranded' parking spots, Stewart. Now, if I can just get the aircraft to move off the 'hold short' line at Runway 10L and actually take off..........
Thanks Stewart. Unfortunately, although the likes of a C-5 manages to advance beyond the hold-short point at Rwy 10L, anythng smaller (p-3's, metroliners etc) gets decidedly stuck.
I was having problems with AI aircraft not getting past the hold short as well(everyone using this AFCAD should run into the problem I imagine). C-17s took off fine but B-1s would just stop at the node and wouldn't even contact tower.
I noticed that the aircraft taxi through the overrun in order to take off and thought that might be an issue(not sure why some aircraft were able to overcome it but others weren't) so I loaded GE and looked at LICZ and noticed that the overrun isn't taxied through in real life. I made the appropriate adjustments(adding a displaced threshold near real life size and overrun area proper as well) and everything seems to work fine now.
I haven't tested every aircraft under the sun but C-17s, KC-135R, F-16s, B-1s, E-8s, and C-130s have all taken off without issue.
I took a look at the AFCAD and there were a few errors in it. Runway 10L/28R had 3 runway links in one section . Runway 27L/9R had a bad start location and the link at the end of runway 27L was labled wrong.
I hope someone understand what I ment when I said Runway 10L/28R had 3 runway links in one section.
Joseph29 wrote:I took a look at the AFCAD and there were a few errors in it. Runway 10L/28R had 3 runway links in one section . Runway 27L/9R had a bad start location and the link at the end of runway 27L was labled wrong.
I hope someone understand what I ment when I said Runway 10L/28R had 3 runway links in one section.
I do know what you mean by the 3 links, I found those and forgot to mention them. There is no 27L/9R only 28L/10R and 28R/10L. I don't see the bad start location or where it was labeled wrong... could you clarify?
I would imagine that the reason they are holding short at 10L is that the runway entrance is via the undershoot
If you extend the runway so that you cross as per 28R i think this will solve the problem
I have just extended the runway try this
Gary
Last edited by Garysb on 15 Oct 2007, 21:38, edited 1 time in total.
Garysb wrote:I would imagine that the reason they are holding short at 10L is that the runway entrance is via the undershoot
If you extend the runway so that you cross as per 28R i think this will solve the problem
I have just extended the runway try this
Gary
That is the reason, as I pointed out earlier in the thread.
CelticWarrior wrote:I don't want to rain on anyone's parade. But has the author of the AFCAD given permission to distribute any modifications of his work?
Not sure, which is why I didn't post the changes I made.
CelticWarrior wrote:I don't want to rain on anyone's parade. But has the author of the AFCAD given permission to distribute any modifications of his work?
Previous post attachment deleted
I didnt think there would be a problem as it has already been posted as modified several times, but to be strictly PC i have deleted my alterations to it so everyone will just have to modify it themselves