A question for Martin
A question for Martin
Martin...sorry to bother you with this and I looked through alot of posted questions before writing this...First I'm a huge fan of Fly Tampa's KMDW...I live 15 miles from Midway and take all my trips out of Midway as well as Flight Sim2004...It's an unbelievable program....my question is ...in the real world Midway only lands commercial jets on runways...31C...13C...4R....22L....that's it....Flight Sim 2004 ATC still instructs commercial jets to land on 31L or 31R...13L...you get the picture...this would never happen at Midway...I've tried adjusting AFCAD file for Midway closing all runways except above mentioned but ATC still instructs jets to land on "closed" runways..I noticed in one of your postings...you mentioned Fly Tampa's AFCAD file for KMDW...with 22L and 22R..closed..first why close 22L when it's one of the main runways for take-offs and landings at KMDW..and is there a way to adjust Fly Tampa's AFCAD file to allow take-offs and landings only on 31C..13C..22L..4R.... and if so where would it be located in FS2004??...sorry for the barrage of questions but I like this program so much...I want it as real as it can be....thanks so much for taking the time to read this and thanks for a terrific program......
- martin[flytampa]
- Site Admin
- Posts: 5290
Runways 22 are closed because of the following. You can reopen them in Afcad2 if you wish.
quote:
As far as closing 31L etc in oder to force landings on 31C... I also tryed that during development without sucess. I'm not an expert with Afcad but KMDW was the only location where I ever encountered this problem.
quote:
PS: I hacked/removed all data related to`the KMDW area from the AP924170.bgl file during development without any effect. Only deleting the whole AP924170.bgl file removed the bumps for good. Note that deleting this file is not a solution since it contains a lot of other vital data.KNOWN BUGS
FS2004: Aircraft may “jump” when taxiing south on taxiway Y around G intersection.
This bug not only affects taxiway Y but the whole airport and surrounding area. The reason for this bug, which is also present without FlyTampa-Midway when using only the default Microsoft KMDW scenery is caused by the Flight Simulator file FS2004/Scenery/NamC/scenery/ AP924170.bgl which contains Airport (Afcad) data for the whole region. The bug doesn’t affect aircraft taxiing the opposite direction and runways 22L and 22R have been closed to prevent bumpy landings.
As far as closing 31L etc in oder to force landings on 31C... I also tryed that during development without sucess. I'm not an expert with Afcad but KMDW was the only location where I ever encountered this problem.
Midway Scenery
Martin...thanks for the info...like I said ..I'm not complaining...Midway Scenery is a great program that has all other airport sceneries beat by a mile....it's realistic enough for me and I can only hope there are future additions to KMDW that will make it even more real than it is...thanks again...