Is there any way that during the update install process, that you can optionally install the new afcad to each airport?
No point doing that, since if the AFCAD which was there in the scenery folder before updated is different than the one we have on the server, a BACKUP will be made, with current time/date.
I know that it makes a back up copy of the afcad that is being replaced. Its quite annoying always have to remember to back up for one just in case the install process does not make the back up file
This doesn't make any sense: the installer WILL make a backup, if a backup is not made, is because the AFCAD was identical and no, we don't use an unreliable time/date check, but a real MD5 hashing of the file so, you can be sure if the file is different, it WILL be backed up.
and two to have to rename and replace the newer one with the one that I have customized the way I want.
This has even less sense, it takes 1 second to rename the backup.
Or any other suggestion is to only update the afcad every so often and not every time or every other time there is an update.
This does even *less* sense than the other two combined: are you suggesting we should restrain from updating our own sceneries, in order to allow to customize the AFCAD ? Sorry, no. We update our files when we decide to, most of users don't customize their AFCAD and expect bugs to be fixed as soon as possible, those able to customize an AFCAD, are SURELY able to rename the backup file to continue their work.
In any case, it's not that we update the AFCAD "too often", the AFCAD might not have been updated, but it's downloaded anyway, because the installer found YOUR AFCAD on your scenery was DIFFERENT! As I've said, it doesn't matter if it's newer or older, making a date comparison would be too unreliable so, if the local AFCAD is *different* it will be replaced with the one from the server.