Hello,Since it looks like Airsimmer is gone, I decided to begin some heavy modifications on the Wilco A32x to bring it up to par. I've taken care of everything from autotrim to sounds thus far, but now I have two problems which I need more hardcore coders to look into. After fixing these problems, I will be releasing a guide to my updates, which means that your help would be helping everybody who owns the Wilco A32x serries. The problems are broken down below.1. APU Startup Timesa. The APU flap on the Wilco product opens immediatley after hitting the APU master switch. In the real aircraft it takes 20 seconds for it to open. Here I only need to create a delay. Since there is NO indication of the flap's progress as it opens, nor any 3d model of the flap on the aircraft exterior, I do NOT need to extend the process of the APU flap opening, I simply need to add a 20 second delay before it opens instantly as normal.b. The APU start sequence on the real aircraft takes 50 seconds on average, while the Wilco has it happen in 12. This time I need to extend the process, since the startup is indicated. I just need to slow down how long it takes to start to be at 50 seconds, and have the ECAM reflect this. I've muted all APU sounds (they can't be heard from the cockpit), so no concern with the sounds not matching.2. Avionics Cooling FansA major sound missing from the Wilco is the avionics cooling fans, which run whenever the aircraft is under power. I have three sounds (startup, run, and shutdown, just like the APU), which need to play as appropriate when the aircraft is under APU or Ext power. I don't think this should be too hard, since the aircraft already has to keep track of the power to decide when to display the autopilot digits (I'm not saying gauges, since these won't display unless BAT 1+2 are on). I just need to add a sound to this aspect.Any help is appreciated, and I hope that I will soon be able to release a modification guide that will help many people.Thanks!

What you proposing sounds like a breach of Wilco's (or any other developer's) rights.

As I said on flightsim.com, I am not selling or distributing any original Wilco files, nor am I selling a guide to the modifications, nor distributing any modifications for that matter. People do these modifications in the ways of soundsets, panel updates, etc, and what I'm doing is really the same.

As I said on flightsim.com, I am not selling or distributing any original Wilco files, nor am I selling a guide to the modifications, nor distributing any modifications for that matter. People do these modifications in the ways of soundsets, panel updates, etc, and what I'm doing is really the same.

You are talking about recoding the files. That surely implies hacking into them and you are also proposing to publish a guide for others.Both those are breaches of the developers rights.

Perhaps recoding was the wrong term. I am simply looking to add extensions to the coding in intentionally easy-to-access files (such as the .cfg), something that has been done by hundreds of people here on AVSIM, many who directly uploaded the modified files. No hacking is involved. I could link to specific examples if you'd like, but I think my point is clear.

[i doubt whether the changes you mentioned in your OP can be done by changing the .cfg files, or indeed any other of the supplied text files - there is no coding in the .cfg file. [i]APU Startup Timesa. The APU flap on the Wilco product opens immediatley after hitting the APU master switch. In the real aircraft it takes 20 seconds for it to open. Here I only need to create a delay. Since there is NO indication of the flap's progress as it opens, nor any 3d model of the flap on the aircraft exterior, I do NOT need to extend the process of the APU flap opening, I simply need to add a 20 second delay before it opens instantly as normal.[/i]I suggest that would need a change to a gauge file which, as it's a commercial product, I suspect is compiled not XML. Can you confirm if it is compiled or XML? I don't have the add-on?

I appreciate your insight. You are correct that this function can't be found in the .cfg, which is what I've been primarily modifying so-far. I'm still looking for the gauge files, but I'll let you know when I find them.Just to clarify, is this an offer of help or a confirmation that indeed modifying these files would be a violation of Wilco's rights? I appreciate the input either way, I really don't want to step on any toes with these modifications.