Hi All,To illustrate what "us" addon developers sometimes have to go through (when approached by users because an addon doesn't work as described), to find out what a user MIGHT have done wrong during installation, just two recent examples from my daily support life...In spite of my usual extensive README's, which were in fact read properly by these two users (who will remain anonymous :-) ).And I can assure you that drawing the right conclusions (without access to their PC's) in these cases was a #### of a job :-)Maybe this will prevent you from ever making these same mistakes ...Just "Ter lering ende vermaak" (sorry, I can't translate this Dutch expression :-) )Case1: Multiple gauge versions.When a user was installing my recent Fokker100 Addon2 package, he couldn't get the sound working at all. Since he also used my first Addon package (that contained older versions of some of the included gauges), I didn't have a clue what went wrong here.Because installing the gauges from the new Addon2 were supposed to overwrite the older versions, as instructed in my README.Now, what did FINALLY appear: When installing the first Addon package, the user thought he was clever and installed the gauges in the local panel folder of the aircraft instead of the Gauges folder.Which I myself do as well, when installing addon aircraft (because when removing an aircraft you automatically remove the gauges that came with that upload).However, when installing the Addon2 package, he followed my instructions to the letter, and placed the new gauges in the main Gauges folder.Hence, FS2004 was STILL using the old versions of the gauges because gauges (with the same name) in the local panel folder have precedance over gauges in the Gauges folder !!!Case2: Double aircraft definition.When a user was installing my Groundhandling gauges, he couldn't them get them visible in his panel, whatever he tried...And actually everything was installed properly, including the modifications in his panel.cfg file.Now, it finally became appearant, that FS2004 wasn't using his modified panel.cfg file.Why ???I found out that this user (to be safe) made a backup copy of his whole aircraft into the aircraft folder, which causes the aircraft folder to have to identical aircraft.cfg files in two subfolder. Which means that suddenly the "TITLE= ..." definitions over all aircraft.cfg files wasn't unique anymore. And since FS2004 uses the "TITLE= ...." definition as unique reference to an aircraft, it appeared that FS2004 was constantly loading the OLD panel.cfg file (from the copied aircraft folder tree) instead of the one the user was modifying :-).Be warned ...:-)Cheers, Rob Barendregt

sigh :) - you're a braver soul than I sir, the sum total of my contribution is a single afcad for a relatively obscure airport.I've had no support issues :-bigangelregards,MarkXPHomeSP2/FS9.1/3.2HT/1GIG/X700pro256

Well Mark, why stick to one ??? *hint* :-)Cheers, Rob