I love the new KDTW airport! Paul J. Mainville did a great job. 1 problem - Whenever I try to ILS land runway 27R in my 737NG, the plane always lands about 30 feet to the left of the runway if I follow the instrument prompts from the localizer. The glideslope is perfect, but the localozer puts me well to the left. Anyone else having this problem? Anyone know how I can fix it?Thanks. Excellent work just the same Paul (wherever you are!) :-)Chris Catalano

Sounds like the scenery isn't lining up with the default navaids in FS9. In FS2002 the freeware program called easynav allowed you to move navaids, but I don't believe the program works with FS9 (yet).I guess you'll have to treat it like an offset localizer and sideslip :-)BlairCYOW

With the latest version of AFCAD2 you can now adjust and save navaids. Check out the location in the base layer and couple it, if you have FSUIPC paid with an overhead shot of the scenery and modify if you wish.

I think Mainville's KDTW replaces the default ILS with his own in the KDTW50.BGL file. I noticed while working on an AFCAD for 2002 that the 9L and 9R runways are too far north, compared to the positions shown in www.airnav.com. Running easynavs2k against KDTW50.BGL I was able to extract all the ILS elements into an easynav database. for 27R I-DMI:easynavs IDMI 108.50 KDTW RWY 27R N42-13-04.6 W083-21-41.7airnav Antenna location: 42-13-00.717N / 083-22-08.843WBut using slew it appears the runway is actually 42-13-04.854Nwhich is pretty close to the easynavs locationfor 27L I-EPA:easynavs IEPA 110.15 KDTW RWY 27L N42-11-59.9 W083-21-37.0airnav Antenna location: 42-11-56.230N / 083-21-55.680WAnd again using slew: 42-12-00.036N again pretty close. Could be tweaked I suppose.scott s..

OK - now I guess I am still a bit confused - is there something that I should do with the new data you uncovered? Do I enter it in a file somewhere (I am kind of new to editing, etc)?Thanks for the help.Sincerely,Chris

Has anyone posted any pictures of KDTW yet?_____________________________http://home.comcast.net/~jsnyder99/sigs/nameavsim.jpg

>>OK - now I guess I am still a bit confused - is there something that I should do with the new data you uncovered? Do I enter it in a file somewhere (I am kind of new to editing, etc)?<

Navaids can not be added via Afcad2 into FS2004 like they could in FS2002, due to the difference in how the two sims handle them. This is even stated within Lee's documents.He is hoping to change this with a future version(?).They can be added, however with a program like Airport For Windows(AFW).

As of yesterday, no. I have been tweaking the AFCAD file that is included by default.Having never been to DTW, I understand that parts of the old Smith terminal are being demolished for a replacement. Now that McNamara is open and NWA is there, the old maze can be replaced.I'm under the impression that all domestic airlines other than NWA and COA are in Smith. DAL will soon move to McNamara. Does COA use gates in Concourse B at McNamara? (b5, b7, b8) Lufthansa is also there, but at what gate?I've largely got McNamara done (all concourses- just need to add COA, KLM and DLH assignments)I'll need to work a bit at SMith, but that is not a major project. I'll add extra gates at Smith to account for the default AI.As of right now, it is very interesting to catch a bank of departures. Those runways get clogged fast. Even with 2 in use!

As I said, I don't do FS9, but here is an excerpt from Lee's document for 2.21:Changes For This Release 2.21NavaidsAFCAD can now create, move, and modify navaids. This includes ILS (LOC / GS / DME), VOR / DME, marker beacons (OM / MM / IM / BC), and NDBs. These changes will appear in the Flight Simulator Map View and GPS windows and your aircraft instruments will recognise the changes. There are, however, certain limitations with regard to navaid changes, as follows:Creation: AFCAD can create any of the above navaids at any location.Modification: AFCAD can move or modify any navaids that you create. It can also move or modify all stock navaids except for marker beacons, stock marker beacons cannot be changed in any way. You cannot change the identifiers for any stock navaids but almost all other parameters can be changed.Deletion: AFCAD can delete any navaids that you create, but it cannot delete any stock navaids.scott s..

Also I believe if you recreate (use the same name as in a base layer) a navaid, it will supercede that of the same ID on the base.It should be noted that the term layers here is not used in the same way as FS2K2 AFCAD layer files of different ICAO codes for flight plans, etc.

Hello Chris!Unfortunately, Paul's AFCAD file included in the scenery .zip file is HORRIBLE. Not only are the ILS's not aligned, but the whole airport is a mess. The taxiway and runway inersections are all messed up and the AI aircraft do not follow the runways and taxiways through the centerline because the lines are all messed up - it was really bad. Soooooooooo!!!!!! I went to work with AFCAD-2 and fixed it all really nice. Everything now works fine!My 2 cents!Dennis!

Hi Dennis,Would you be prepared to share your update ? I'm sure that there would be a good take-up !Alastair

Even if the AFCADs need a little work, it still is a nice addition to the fltsim hobby.scott s..

Hi Dennis,My experience with this nice scenery is that it needs some additional work.first the AI aircraft do not park at the right positions. Northwest is no longer at the Smith Terminal. Next, the Smith Terminal does not have the correct parking spots for Smith Terminal, there is no A2 parking spots where UAL uses. In fact the scenery does not have a gate for A2.When I was in Detroit, I believe that runway 27R is now inactive, which still shows on this scenery as an active runway.The old NW terminal is not active and the scenery is still showing aircraft parked there. Until the refurb of those terminals are done, no aircraft should be parked there. The Smith Terminal has some unfinished tower stuff showing up that is not realistic. This is a nice addon but it does need some attention to detail IMHOCheersBob