Solved at last, after I decided to take the easy route.A check on FS9 showed the problem wasn't present. FSC is common to both, so not FSC related. That left FSUIPC. Checked both versions of FSUIPC's ini file but both looked the same, re TCAS. Deleted the FSX version and let FSUIPC creat a new one. Problem now disappeared. No idea how or where it held the data but not too worried.
Meanwhile, why didn't it apply to the A350? My guess is because FSUIPC was set to pick up the aircraft model names. The model name for the A350 is unusual, so perhaps it didn't recognise it as a model, so couldn't trigger the TCAS.
Now, perhaps, I won't be up at 0530, tomorrow, with this one no longer niggling at me.
Gerry Winskill Gerry Winskill wrote:
Meanwhile, it gets curiouser.I worked my way through the various aircraft in my normal use fleet. All started from the same saved situation; sitting on the threshold of Aldergrove's 25, with engines running. Of the seven aircraft tested, all triggered the self imaged TCAS alarm. The one that didn't, in a series of repeat tests, was the A350. This differs from the others only in that I downloaded and installed it after the FSCC TCAS problem surfaced. There's no reference to TCAS in any of the Aircraft.cfg or Panel.cfg files.So, it could be either that it was post FSC, or recently downloaded.I flew the Default B737 and B747, neither of which I've previously used. So it's not whether it's been used that's the deeciding factor. Next I downloaded and installed the Beechcraft Starship; an ugly looking piece of artwork. That triggered the TCAS!So, how come the A350 doesn't. Baffled of Ramsey! Gerry Winskill Gerry Winskill wrote:Paul, Thanks for the lead, though it may take a while to follow up.I tried to log in but was rejected because my password was wrong. I went for the password reminder option but that was rejected because of incorrect email address. My email address must have changed since I first registered. I can remember the old one but that's no use 'cos I won't get a password reminder that's sent to that address.If I try to re register I can't, because I already exist. Its called a Catch Twenty Two! I've emailed asking if they can suggest a way out of the impasse. Gerry Winskill Paul Reynolds wrote:Hi GerryI've been trying to recreate the problem on my system but cannot manage it. I've looked through all the possible avenues I can to come up wih some suggestions but you've covered the obvious so all I can do is point you to the FSC forum for a potential solution.http://forums.simflight.com/viewforum.php?f=155 Paul ----- Original Message ----- From: "Gerry Winskill" <gwinsk@xxxxxxx> To: <jhb_airlines@xxxxxxxxxxxxx> Sent: Thursday, July 05, 2007 3:58 PM Subject: [jhb_airlines] FSCommanderIs there an FSCommander gru in the house?Some weeks ago the FSC TCAS took it into its head to disply user aircraft. This has the unfortunate effect that the TCAS Alarm goes all the time, triggered by the proximity of the user aircraft to the user aircraft.In FSX Options Settings Display Traffic, there is no tick against User Aircraft. I've gone ito FSUIPC Miscellaneous and tried switching off TCAS and changing the distance for detection settings.Whe I recently flew the A350 for the first time, it didn't trigger the TCAS.Does anyone know if there's an .ini file setting that might be storing the Show User?It's one of those things that really niggles, during a flight. Gerry Winskill