Hello alastair!I will be more than happy to share my AFCAD file with you guys. As Bob mentioned below, there are additional praking problems. I did not address the parking issues because that piece is extremely difficult for me to do with AFCAD. Since AFCAD does not show the scenery buildings, it's like guesswork. I did fix all the runways and taxiways, as well as a bunch of broken tarmacs and such. If you guys are interested in my afcad file, send me an e-mail to [email protected] and I'll send it right away.Sincerely,Dennis D. Mullert

Paul's scenery isin't final. According to Airnav, none of the runways are closed, howevefr there has been a lot of demolition on Smith to make way for teh 'new' Smith terminal.TIm

Hi Tim,When I was there at DTW this past fall, there was a big X on 27R which is why I made my comments. I checked their web site, but could not find anything.The Smith Terminal (old one) is really not correct at all for now. As I am sure you know the new North Terminal will house all the current airlines except for NW which uses their new mid-field terminal. This is really a nice airport. I have watched it grow since I was a little boy. I don't live in DTW anymore, but go back often since I have lots of family there.I would love to see a real accurate update for this nice scenery.CheerBob Johnson

Thanks all! For the great comments. I appreciate all feedback that I get.I'll try to briefly address some of the issues here and hopefully shed some light and understanding to them.History-------This scenery was originally intended with FS2002 in mind and has been an on-going project and probably always be, with each release showing marked improvement over the last. Obviously if you follow my thinking here it is never really complete, but goes through phases of improvement.I delayed the release until FS9 appeared and then of course had to further delay as we all awaited Lee's program. I agree with most of you that Lee's program is a god send to our community, however personally, and this is a personal opinion, I find too much emphasis is placed on the scenery designers on these files. To me they are normally customized to a user's taste rather than to any universal standard. Obviously being of that frame of mind I don't spend a whole lot of time in this area. Personally I probably go in and tweak certain things within my AFCAD file daily. Lol!On to the ILS problem. Someone mentioned AFW here. Well the known problem with AFW is the reading of dual ended runways using the same frequency. It just isnt possible and its my understanding that further builds on AFW will not occur as Tom has moved on to SceneGenX an XML based designer. I have dabbled into this area and at this time will be for future development.As someone else correctly mentioned the early version of AFCAD for FS9 did not have NAVAID capability. I believe this came into being in version 2.11 which was released after I released this version of the scenery.SOLUTION--------Obviously AFCAD 2.21 is the solution to the NAVAID problem as someone brilliantly pointed out to me in e-mail. I did try it out in another project and it does handle the issue quite well. Therefore at this time my suggestion is to tweak your personal AFCAD files in this way. Lee's documentation is excellent in how to accomplish the task.OTHER ISSUES------------The other issue brought up is the older Smith and Davies Terminals. Yes there is major construction and reorganization going on in these areas. I am just awaiting for documentation to go in and reconstruct these areas when it arrives as they are pretty much leftovers from the 2002 version of the program. In fact the majority of the macros there were created with Nova while the McNamara Terminals were done with Rafael Sanchez' newer Novasim.As to the gate logos. This is a bit of an inside joke I'll let you in onand was a compromise to a nasty e-mail I received from a former Virtual Airline I was CEO at. The McNamara terminals if you look closely all have my current VA logo. I plan on eventually replacing them with the proper logos in later versions. The punch line was here you go guys you can use it but park over there. Lol!Thanks once again for all the support and help.

Will you be releasing an update that removes the AFW created ILS's so that the AFCAD created ones will work? The AFCAD ILS's will not work until the imbedded scenery ILS's are gone.

Kevin, I'll post an updated bgl at my site without the ILSes this weekend and will make a notation here when I have. I am still looking for a more permanent non-AFCAD solution for the next version without having to completely re-design the entire project. I'll post the address here when I have done the update.Just to add a note to this: I have investigated and tried to correct the file using AFCAD. I was not able to achieve the proper results either with this solution, but that doesn't mean its not possible, as I have not had a whole lot of time to devote in this area at this time.

>Hi Tim,>>When I was there at DTW this past fall, there was a big X on>27R which is why I made my comments. I checked their web>site, but could not find anything.You are completely correct, 27R/9L is closed because of the taxiway traffic problems it would cause. 27L/9R is hardly ever used unless in the case of very strong west/east winds. The primary runways that DTW uses are 22's and 21's, southflow. Second is the 3's and 4's, and third is 27L. Also, when noise appatement procedures are in effect (0000-0600 local) takeoffs are done on 21R, 22L and landings performed on 4L and 3R. Landings at DTW are simple, land outboard runways (21L/3R, 22R, 4L) and depart inboard runways (21R/3L, 22L,4R). Hope this helps.:-)

Download the AFCAD AF2_kdtw_139015.zip All the gates are assigned for AI. You'll still need to move the loc. beams into theb right possition using ACFCD.Dave FisherCYYZP4 2.8 GB 478P 533 MHZ CPUP4P800S Asus Motherboard512 DDRGeforce Ti 4200/128Maxtor 80 Gig ATA 133 HDhttp://www.precisionmanuals.com/images/forum/ng_driver.jpg

I have also posted a non-ils version of the bgl files at my site.http://www.vnwa.com/noramair/downloads/kdt.../Kdtwnonils.zip

>Kevin, I'll post an updated bgl at my site without the ILSes>this weekend and will make a notation here when I have. I am>still looking for a more permanent non-AFCAD solution for the>next version without having to completely re-design the entire>project. >>I'll post the address here when I have done the update.>>Just to add a note to this: I have investigated and tried to>correct the file using AFCAD. I was not able to achieve the>proper results either with this solution, but that doesn't>mean its not possible, as I have not had a whole lot of time>to devote in this area at this time.Hi Paul,Nice job with the scenery, and thanks for all your hard work. I don't think it is possible with AFCAD2. I also found the same ILS problem with John Young's London EGSS scenery, I tried and tried to fiddle with the AFCAD2 but finally had to break down and write him about it. He sent me a patch in the form of an updated .bgl file for Rwy 23 at EGSS. And he also sent a nice response and explanation, saying for some reason (as the poster above stated) FS2004 it can't handle the same ILS frequency on both ends of the same runway in the xml code, which explains why I was wasting my time with the ILS alignments in AFCAD2. Rwy 5 worked fine but not 23. His solution was to create a whole new .bgl file for Rwy 23 at EGSS but change the freq by one click (110.50 to 110.55). Works like a charm, but the problem with this is it brings a whole new set of problems in keeping accurate info. Jepps immediately become obsolete and it's up to the individual to keep accurate records. I experimented with an AFCAD for EGGD/Bristol England for some add on scenery that I downloaded from Birdman. His scenery has the same problem. I haven't been able to get this one fixed either. Rwy 09 works fine, but Rwy 27 doesn't have a working ILS at the moment. Don't know if any of this info helps, but this is what I've discovered.

The old link will work and so will this one. If you downloaded yesterday you will have to do it again. Sorry, but I corrected a crucial problem to make this fix work. (See below)http://www.vnwa.com/noramair/downloads/kdt.../Kdtwnonils.zipFirst of all thanks to all of you for your support and patience and a very special thanks to Kevin Au for pointing me in the right direction.Originally the fix he suggested tied me in knots as I tried his method of using AFCAD to fix this situation to no avail. No matter what I combination I tried I still did not get the ILSes working properly even after unchecking the Navaid ILS box in AFW. It is obvious I became too focused on solely the ILS when in fact I had duplicate NBD's and VOR in AFW and they were checked also. Unchecking them and recompiling fixed the error and bingo the ILSes were functioning properly although there still seems to be an issue with the Name but as long as the right frequency is tuned they should now work. Mind you will need to either adjust them with your AFCAD program or use the one I included in the file. This of course is optional as it is customized to my traffic.