ZKiwi

Hi,

Could you please send me your latest mod and include me in your email list.

Many thanks

Ty

@Dazza, 

I'm pretty sure it is the aircraft model as i have found the same issue when using any joystick access to control the prop pitch. I'm currently using a Saitek Throttle quadrant (pre logitech) and it has a similar issue. It just means i have to move the prop pitch slowly so it does not swing so much.

Thanks for the reply. I am thinking the same thing as i have put a support ticket in and nil response also. Now considering just requesting a refund as Alabeo wont provide/confirm any LVAR so the aircraft is not suitable for practicing prior to RL flights. 

When i switch on the left and right alternator only the left hand light goes out and the right hand light remains on. If i turn off the right alternator it shows a change in load on the ampere meter so the alternator is working but the light is not picking this up.

Anyone else get this?

P3D v4

But they advertise AS2012 ( and older versions as well) as able to use Vatsim weather but it doesn't appear to at all. If it does then it is not getting it's weather from the Vatsim servers as there are several airfields in NZ that have Vatsim weather. IF you flight plan a flight between two airfields that have current Vatsim Metars then you should have that weather and not some interpolated weather from stations thousands of miles away. I can't use As2012 for online flying on Vatsim as i often have winds that are close to 180 degrees out and i am landing on opposing runways to other Vatsim traffic. I have relegated AS2012 to a backup hard drive and started using REX2 as it appears to use the correct Vatsim server weather.

I can only speak for the weather in New Zealand from experience but even when using the Vatsim option and on a flightplan it appears the only weather that is actual Vatsim weather is Auckland (NZAA) Wellington (NZWN) and Christchurch (NZCH) and the rest are interpolated from station as far away as South Pole and Pegasus field in Antarctica. This is exactly the same result as downloading the weather from the Hi Fi servers (ie: not using the Vatsim option.) I have submitted a support ticket and have had a message back saying they will look in to it but have not heard anything since that time. At present the only option i have for online flying is to use the FSInn weather which comes directly from the Vatsim servers. This issue has been around since when i first started using Active Sky back with ASX and then all the way through ASA, ASe and now AS2012.

It appears as if there is no change. Even if using Vatsim weather only the main centre weather is accurate and the rest is interpolated. I doubt that the weather is coming from the Vatsim servers at all.

I just planned another flight and the latest Vatsim weather was;NZWP 191754Z 27008KT 40KM FEW018 SCT035 19/16 Q1015 RMK NZAA VATSIM USE ONLYNZHN 191652Z 31005KT 20KM FEW020 14/13 Q1015 RMK VATSIM USE ONLYHowever AS2012 weather was;NZWP 200534Z 12003KT 200V270 9999 SCT049 21/15 Q1013 RMK ADVANCED INTERPOLATIONNZHN 200534Z 05003KT 214V287 9999 SCT026 20/14 Q1005 RMK ADVANCED INTERPOLATIONNot even close. At least Hamilton was using the same runway.I realise the AS2012 weather is more up to date however if flying online on Vatsim then the weather really needs to be the same as controllers and all others are running. If AS2012 sources the weather from the Vatsim server if that option is selected and a flight plan filed then it appears that AS2012 is not working correctly.

It appears the same still happens in AS2012 in New Zealand. The Vatsim data is not loaded at all as far as i can tell.

This issue is even worse in New Zealand with few of the airfields that have valid real world and Vatsim Metars and the ASE and AS2012 weather differs from these Metars considerable. The interpolated weather was so far out that the opposite runway was active in Vatsim to my weather.I tried to plan a flight from NZHN to NZPM in both ASE and AS2012 today and both stations weather was incorrect according to Vatsim. I was hoping that AS2012 may have sorted this but looks like the issue is still here.