Thanks for your quick response

I too am having issues with altitudes being read incorrectly, and also with altimeter settings. For example, after setting STD when cleared to a FL and then calling 'set STD' (button control), it says 'standard set, passing FL 80........ now'. The 'now' occurs at a lower altitude, in my most recent flight this was 6600, but it varies. Then, when carrying out the after-takeoff checklist below the line, the co-pilot reads out a totally different altimeter setting - '2026 set',most recently. 

I've just finished uninstalling and re-installing the A320, A319 and FS2Crew but the problem persists.

I'm using the latest version of ActiveSky.

I know you can't reproduce it, which is frustrating for you and us, but I thought I'd add my report to the list in case something comes to you!

 

Thanks,

Filbert

Hi Filbert

There's not much more I can do regarding the altitude callout.  Active Sky totally changes the weather internally.

I'll ask the FS Labs developer if there's something they can add to the sim so I can read the Altimeter Setting better.  

Cheers,

I'm following this topic and taking note that there is not much you can do right now, but just want to say I can confirm I'm having a similar issue.

On passing transition altitude, I set the altimeter to standard and say Set Standard. The PM's crosscheck when he says his altitude followed by "NOW" is about 300 feet off, which seems to be that he is reading the P3D altitude (as seen by pressing SHIFT-Z) on the local QNH instead of the pressure altitude at 1013 hPa. Local QNH was 1003 on my test flight so 300ft difference makes sense (30ft per hPa).

Using Active Sky as so many others.

Hope you can do something about it.

Mathieu

Edited January 28, 20206 yr by tjeuten

I'm hoping the FS Labs developer will expose the Altimeter value in the future so I can read it directly, but who knows.

At any rate, are you entering the Transition Altitude in the Departure Brief section?

 

5 hours ago, byork said:

I'm hoping the FS Labs developer will expose the Altimeter value in the future so I can read it directly, but who knows.

At any rate, are you entering the Transition Altitude in the Departure Brief section?

 

Yes I did

Just now, tjeuten said:

Yes I did

Is it always off by exactly 300 feet?  Is this plus or minus 300?

 

On 1/28/2020 at 11:18 PM, byork said:

Is it always off by exactly 300 feet?  Is this plus or minus 300?

 

I'll jump in here again. In my case it's always 300 feet. FS2Crew will call an altitude that is 300 ft below the actual altitude. So it won't call, for example, 5000 ft until my altimeter shows 5300 ft. For this reason, I never get the call that I've reached cruising altitude because FS2Crew still sees me as 300 ft under that.

As I mentioned in the OP, I don't think this issue is limited to FS2Crew. I also see this with other add-ons connecting through Simconnect, such as ProATC/X. So I do think that it's FSLabs who will have to figure this one out. I've opened a ticket with them as well.

We really need FS Labs to expose the Altimeters values directly for Active Sky.

I only use default weather, never 3rd party stuff, and never had a problem.