I downloaded version 3.01 last night and tried a short flight. I cleared all weather for the flight and while cruising at 17,000 feet at approx 220 knots, I received a call from ATC approximately every 4 minutes telling me that the altimeter was 29.91. On a previous flight, using FSMeteo, I received multiple calls (some minutes apart) telling me the current setting even though it had not changed from the previous value. My recollection, which is usually poor, is that in the previous version we only got altimeter info when it changed. Is this an update to better match reality?Tom

Same with my updated 3.01 download. I had been using the 3.01 Beta and had no calls about altimeter settings except in the descent clearance to below transition level and the weather.RichR

was the pressure really 29.91 via fsmeteo or active sky? or was it something different?

In my case, one flight was with FSMeteo and the actual altimeter was something in the thirties. RC properly reported the correct setting. It just did it about four times, three minutes apart, even though the value hadn't changed.In the second flight I cleared weather and got the repeated calls at 29.91.Tom

I am not using any weather addon program. I am using S-Combo and that is all. The altimeter setting given is always 29.91. As I stated before this did not happen with 3.01 Beta.RichR

I can confirm that I'm also getting repeated altimeter calls, at intervals of a few minutes (2 or 3?).Also, when FSMeteo updates, RC doesn't give the new altimeter straight away, it seems to wait for the 2 or 3 minutes to elapse, then gives the new setting, and then repeats it again within a few seconds.On the flight last night I had a slightly different problem - having reached my crossing altitude, FSMeteo updated with a large change in pressure. RC then told me I'd busted my altitude twice before it gave me the new altimeter setting. I know I could have hit 'b' to set the altimeter, but in the real world I wouldn't have known the pressure had changed until the controller told me.Ian

two questionswhat is your altitude deviation set for? what number is in the altitude deviation window (30 means 300, etc)is this happening about every 100 miles travelled? if so, the altimeter call is by designjd

>is this happening about every 100 miles travelled? if so, >the altimeter call is by design >>jd In my case it was at less than 100 mile intervals. Could this be a problem with running with high priority?Tom

Hi,I've never altered altitude deviation so I'm using the default 300. This means 300 feet, doesn't it, not 3000?The first problem with the repeated calls was at much less than 100 mile intervals - I was flying the Baron at the time and getting repeats every 2-4 minutes (maybe 5-10 miles?).The other problem, where altitude was busted twice before the new altimeter setting was given to me, was in an A320. It's possible that RC was waiting for 100 miles to be flown before giving the new setting, but in this case wouldn't it be better if RC checks to see if there is a 'pending' new altimeter setting before giving the 'you busted your altitude' message?Ian

you're right 300 is 300 (i was thinking, wrongly, that 30 was 300 because internally to the program i use 30 for 300). my mistake. the altitude bust in the airbus, i don't wait for 100 miles to give you an altimeter call. could you try it again, and save a dat prior to when when you get busted, and then the descent clearance.

OK jd - It might be a few days, as I'll be away from the PC for a while.Ian

i have updated 3.01 to fix this problem. silly little mistake. download an updated v3.01 from www.jdtllc.com/v3/rcv301.zipand i won't be sending a list serv based message announcing it to everyone :-lol