1. I limited that some time ago, since the real engine parameters are usually lower than 100% Its not really the fadec controlling this at the moment but it will be in the future. Keep in mind that the real engine does produce 100% thrust even at 90% N1 in some conditions and maybe 95% N1 in other conditions.
You can adjust the fan buzz in the tmd file, in the sound section. There should be a sound for the fan buzzing and it has an input soundmapping where you can adjust the n1 value from which to fade. N1 is a fraction in Aerofly, so 0.95 in the mapping would be 95% on the display.
2. You can just copy the wind sound files from the gliders over into the A320 folder and then copy paste the section of the tmd that defines the wind sound. Again using the sound mappings you can adjust the volume and pitch of the wind sound for airspeed or angle of attack or what ever you want. The tmd is unlimited in this regard, you could make the wind sound play if you set the flaps for that matter.
3. At the moment yes, but they don't have to be. Its mainly because we don't have separate samples for the fan and the hp and ip compressors, burner and hp and lp turbines or nozzle. You can define a new input using the sound input, then feed it through a mapping and then play new sounds on top of the existing ones, or use an existing sound, change the file name, adjust the sound mapping for volume and pitch and implement your own sounds this way,
No matter what you do, keep a good backup of your own sound creations. Last thing you want is Steam to erase all your work when Aerofly is automatically updated.
Thinks for the info, yes backing up is standard. Ok great, I'll get back into the tmd file. Regarding the N1 limits, am aware that ambient temperature will influence the N1 limit on the real aircraft, does the temperature always stay the same in aerofly? no matter where you are, night/day, weather setting? I'll admit I haven't been looking closely at the SAT when lined up on the runway.
Cheers