Post by Tom/CalClassic on Oct 16, 2008 15:10:54 GMT -5
Hi,
I think that moving all AFCAD files from addon airports into the Addon Scenery/scenery folder is the worst idea I've heard of in a long time.
I don't know how this FS legend got started, but AFCAD files for the same airport but in separate scenery layers do NOT cause CTD's, and never have.
Worse, moving them all into the Addon Scenery/scenery folder is MORE likely to cause duplicate AFCAD files in the SAME scenery layer, and this DOES cause CTD's! I've only used ScanAFD to find out if I have duplicate AFCAD's in the SAME SCENERY FOLDER, usually the Addon Scenery/scenery folder.
I have up to 5 AFCAD files for the same airport, but each one is in it's own scenery layer (usually the folder for a given addon scenery). I have never had a CTD. This includes mods to default airport AFCADs in the Addon Scenery/scenery folder, from PAI and other sources. Thus there are AFCAD files for the same airport in more than one active scenery layer. No CTD's.
I have released scenery packages downloaded by hundreds of people, which all create duplicate AFCAD files for that airport for most people. But, they are always in their own scenery layer. Not one complaint about a CTD.
With each AFCAD file located in its scenery's folder, I have all AFCADs right where they need to be - if I deactivate an addon scenery, the modified default AFCAD in the Addon Scenery folder takes over. If I have multiple addons for a given airport, I can pick and choose them as I wish, with the AFCAD file working just like the rest of the scenery BGL files.
So in summary, this phobia about duplicate AFCAD files is:
1. Way overblown
2. Making things much more difficult than they need to be
3. Usually not a problem at all
Hope this helps,
I think that moving all AFCAD files from addon airports into the Addon Scenery/scenery folder is the worst idea I've heard of in a long time.
I don't know how this FS legend got started, but AFCAD files for the same airport but in separate scenery layers do NOT cause CTD's, and never have.
Worse, moving them all into the Addon Scenery/scenery folder is MORE likely to cause duplicate AFCAD files in the SAME scenery layer, and this DOES cause CTD's! I've only used ScanAFD to find out if I have duplicate AFCAD's in the SAME SCENERY FOLDER, usually the Addon Scenery/scenery folder.
I have up to 5 AFCAD files for the same airport, but each one is in it's own scenery layer (usually the folder for a given addon scenery). I have never had a CTD. This includes mods to default airport AFCADs in the Addon Scenery/scenery folder, from PAI and other sources. Thus there are AFCAD files for the same airport in more than one active scenery layer. No CTD's.
I have released scenery packages downloaded by hundreds of people, which all create duplicate AFCAD files for that airport for most people. But, they are always in their own scenery layer. Not one complaint about a CTD.
With each AFCAD file located in its scenery's folder, I have all AFCADs right where they need to be - if I deactivate an addon scenery, the modified default AFCAD in the Addon Scenery folder takes over. If I have multiple addons for a given airport, I can pick and choose them as I wish, with the AFCAD file working just like the rest of the scenery BGL files.
So in summary, this phobia about duplicate AFCAD files is:
1. Way overblown
2. Making things much more difficult than they need to be
3. Usually not a problem at all
Hope this helps,