Had a real lousy flight today! Kind of broke the straw. Activesky and RC3 combination (latest versions) just do not work properly together. Frequent altimeter calls from RC3, tried my flight twice both with on line and offline files. Both times the result the same, on approach, frequent chastisement from RC3 on maintaining alt, RC3 just can't see what ActiveSky is reporting. Hitting the barometer key gave me mixed results. RC3 was seeing the same altimeter settings I was but on alt-tabbing out I see the Active sky settings as different and RC3 is not picking it up. Very frustrating! Think I'll dump the ASKy program. I've been fighting Active Sky, Flight Max Remote, RC2 and RC3 combinations for a long time and the ActiveSky and FSMax portion still don't work as advertise when I spent my money,,hmmm! I stopped using the AS and FSMax awhile back but the latest aggravation is AS and RC3 even with the new Advdisplay. Think I'm going back to FS2k2 weather and RC3 alone. BTW before you hammer me. I'm 50 years old, not a kid, with private pilot's license; retired with 26 year of service in the USAF veteran. ex-AC130H gunner, and currently a network security engineer, I'm not over the top on how badly these programs interact nor do I exaggerate. Posted this also on the AS forum Katopapa

you'll be even unhappier with fs2002 weather.let's tackle the problems.have you download the 3.01 beta of rc? that helps with the altimeter calls over and over againalso make sure you have active sky properly configured, so it smoothes out those different pressure settings over a longer period of time.

JD, Funny you should mention unhappier with FS2K weather, did a flight this morning with just that and RC3, very very unhappy with the stock weather. Ok, I looked at the build from my RC3 and it's from a file you sent me late January during testing. It's build 3.0.1723. I downloaded the build from your beta announcement and I noticed the build on the file was 3.0.1727. Lately the problems with ASky and RC3 are occuring mostly in European airspace. As the transition altitudes vary, I could be at fault there but as I climb and reset the altimeter to standard, no problem. Cruise altitude settings and RC3, no problem. However it's after I descend through the transition altitude that things keep going awry. After the transition I can't keep RC3 happy. I get repeated calls that I'm busting my altitude. I reset the barometer to local (forced weather checked in ASky menu settings for 60miles)and verified by the RC3 weather calls and I still get the busted altitude complaints.I'll give the newer build a try this morning, below is my ASky settings, if you see something I'm doing wrong with it and RC3, I'd appreciate the help.[General]WXREOfflinePath = C:GamesFS2K2ActiveSky wxRETodayExportPath = C:GamesFS2K2ActiveSky wxREOperationMode = OnlineDefaultOfflineFile = expcycle22Z.wxdDisableMessages = FalseExportMetars = TrueMETARUpdateInterval = 15FDUpdateInterval = 45UpdateMETAROnNewStation = FalseUpdateFDOnNewStation = FalseWindsAloftSimulation = TrueIdlePriority = TrueVATSIMMetars = FalseDefaultForceRange = 60ZuluConversion = -6RainVisReduction = TrueOvercastHorizonVis = TrueDisableForceWindUpdates = TrueTAFProcessing = TrueWakeTurb = FalseCloudTransitionInterval = 30MinimumCloudThickness = 200UseSystemTime = TrueProxyAddress = 90.0.0.1

Funny you have reported problems with using European transition levels; that is where most of my problems are. I recently used Rc3 and ActiveSky on a flight from Heathrow to Toronto. As part of the RC setup the London transition altitude was set to 6000', and arriving in toronto set to 18000'.Now the thought was what to set the transition to? I settled on 18000' since the descent will be shallower than the climb out. But I still got a couple of warning Altimeter calls as I left London.JD can you do something about the range of departure and arrival transition levels are active for. I think if you could adjust these, we could solve a lot of problems for those doing flights which cross different transition levels.Thanks,Kevin

seemed like a pretty simple concept when i put multiple transition levels into v3. beta testers merrily tested, and right when i'm ready to release, everyone had an opinion on this.i left it the way it isthe departure transition level, is good until you are out of departure airspace. when you are on center, the center transition level takes affect. when you are in approach airspace the approach transition level is in effect.does that match your findings. 6000 while in departure, but during center operations, it was expecting you to take the 180 transition level for the rest of the flight?

I was going to say yes, but now I think about it I am not sure if I don't get quizzed by Departure. I'll let you know when I get a chance to try it at the weekend.Don't get me wrong its not usually too much of an issue, because normally I am re-cleared above FL200 before I level out at the initial cleared level of say FL140 - so I can ignore it. When you first mentioned including it, I didn't even consider the differences around the world and I will say it is much better with it even with the niggles than without!Also thinking about it, I suspect if I were flying the other way (US - > Europe), I would set the enroute transition to 6000 since the descent would be gentler, and I would just have problems being cleared to FL140 on departure.Enough ramblings from me. I let you know how I get on at the weekend.Kevin.

JD, Kevin, My problems this week have all been on flights in Europe. Did two flights from Oslo, one to Stavanger, the other to Milan. Transition in Norwegian airspace was set to 7000. No problems on departure flying both the PSS Dash 8 and Airbus. Dash 8 was to Stavanger and the Airbus to Milan. Set the altimeter on the Dash 8 flight to standard leaving the layer. On descent to Sola I left the setting at standard on clearance to 7000. No problems from the RC controller. Didn't change QNH until I was cleared to 5000, set the altimeter to local, started my descent and leveled off at what the sltimeter said was 5000ft and thats when things went south in a hurry. Same story again, eventually got the inevitable "You've busted your altitude a fourth time". Man was I miserable! This has been going on all week. The exact same thing happened in the A320 going to Milan. Great flight until I was in local airspace. Since PSS has the pressure indicator flash for barometer adjustment on climb and descent I knew something was off even before I got the controller warning. Was wondering if the setup for controller options was the problem on the Milan flight since I started with a transition of 7000 for Norway, figured Milan should have been 6000.Weird part is the Airbus was at directed altitude, FS2K showed local pressure the same as the weather check, even ASky had it right and the weather check confirm the QNH but the RC controller didn't agree with my altimeter. I'm using the latest FSUIPC, RC3 3.0.1727, Advdisplay, and Showtext. My next step is a short flight in the US today to see if it happens again.

What was your enroute transition set to? You don't say. If you set it to 18000 then they may help to explain why the situation was exacerbated.As for PSS flashing the STD on PFD. You probably have the FMGC programmed with 18000 as the transition level. Therefore it will flash when you climb above this level and haven't pulled the selector and equally will flash when you drop below this level and haven't pushed the selector to tune the setting.If you want to e-mail me the flight plan (FS2002 format so I can plot it and enter into the FMGC before I fly) along with a list of all the settings on the RC pages (frequencies, transitions, etc), I'll try it at the weekend.Kevin