airbusjoerg

That is correct but after setting all up and using the latest FSUIPC and AS2012-version the problem still persists that a 5 knot wind is taken as "calm". As JD explained above, this is normal - no one except he knew - and if you dont know such things you'll drive yourself crazy in search for the problem.

Okay, thanks. I was in the AS2012 forum and in the FSUIPC forum like "folks, there is an bug... there is wind with 5 knots and RC only says calm" - everything messed around and no solution was found. Until now, when you said, that is quite normal. :-) Next time I should ask you first... :-)

When the tower issues the landing clearance it says "winds xx from yy - cleared to land". Does RC take this wind from the destination airport or simple from the actual aircraft position? (I had the effect that there was a wind 120/4 shown on ND down to the airport but the tower gave me a "winds calm".) Sorry, forgot to say: FSX, AS2012, latest FSUIPC, DWC

"Fiddeling" is no good, one should read the manual, think about and test different settings careful and step by step. Thats the way I do it. In that case it couldnt work because - as we know now - there was a small error in FSUIPC.

What is about your AS2012 setting "Force ATC Wind Lock" ? Do you have it enabled?

Ok, thanks. Will also try the revised DLL from Pete on saturday morning.Will also check if refresh the weather helps.The only strange thing is the AS2012-Freq : 122.00 should give the actual weather and 122.02 the arrival. No idea why it don't work for you...? This, for example, worked in my system.

@Norman:did you use 122.00 or 122.02 for ActiveSky at departure?Also which refreshs did you, Refresh AI? Did you load the route into AS2012?Which version of FSUIPC did you use?

Seems, the incorrect RC-ATIS could work, if one use the BETA SP1 and FSUIPC 4.80 - not newer! With FSUIPC-versions after 4.80 it doesn't work. I dropped a short post at FSUIPC support forum.If the RC-ATIS works with the DWC mode, then the origin problem of this post were solved.

Did someone tell this to Peter Dowson? I posted it into the FSUIPC-forum to make sure, he is aware of.

Do you use the latest Beta SP1 ? (I don't use it, because the word "beta" is a bad word if you drive a commercial simulator :-) )You said, it worked +/- for you. How big are the +/- - for example regarding QNH?

According to ActiveSky 2012 User's Guide, page 8, part "Direct Weather Control":"FS ATIS will not report the actual surface conditions that will be depicted. In order to receive actual surface conditions, the AS2012 ATIS/Flightwatch Voice features should be used."Since RadarContact does not communicate direct with AS2012 (it takes the weather from FSX), it is in my opinion not possible, that the RC ATIS is correct. You are a miracle. I did more than 50 flights and I can tell you, that the RC ATIS does every time differ to the AS2012-surface conditions and according to the manual this is quite normal.Can everybody clear those up?

Thank you. Is there any idea WHY it is more ore less worse on different systems?I tried to use it because I use RadarContact too and in DWC the ATIS / QNH are always wrong (I know 122.00 / 122.02 - but that does not remove the problem that the ATC says the wrong QNH and winds on TO). I also noticed that in DWC - even if you press "refresh AI", the other aircrafts often use other/opposite runways.In a semi professional environment like our (www.cockpit-simulation.de) - with partly very professional "guests" - this is not what I have dreamed of - altough AC2012 is still the best avail.So I thought the standard mode would fix the problems - and it is - but then it stutters. Because of that, a last "mean" question: when it is known that the standard mode is unusable because of the stottering why it is implemented then?

I use AS2012 in a network configuration with FSX / Win7.FSX always has about 36 FPS, so also in DWC mode. Yesterday I tried the Standard Mode and there was something strange: the FSX showed stable 36 FPS to me, but the whole animation system of the FSX stuttered in 1s-intervalls. I've seen this never before, it was no performance issue. Switching back to DWC mode, it was gone.I was able to reproduce it again and again on different airports - switching over to Standard mode and it was there, switching back to DWC, it was gone. The FSX showed 30-36 FPS over the time in all modes, it seems, the stuttering had nothing to do with FPS.So what could it be? With this behavior the standard mode is useless.Best regardsJörgwww.cockpit-simulation.de

Thank you!I've found another thing: key assignment via FSUIPC - will try this first but hit should work...

Hi folks,we would like to integrate RC4 into our "home cockpit". However since I would like to do all the stuff from within the cockpit I bought 2 numeric keypads (USB) which I placed into the cockpit.It seems, I'm not able to use this numeric keypads. I'm able to assign the numeric keys in the options menu (it shows the same values as the ordinary number keys), but later "in action" RC simply ignores it - it only react to the ordinary number keys (tested num lock on/off). Testing the numeric keypads with textedit - the hardware itself works fine.Is there any way to get this, because I don't want to jump out of the cockpit to hit a key on my computer keyboard for every radio message... :-(Best regardsJörgwww.cockpit-simulation.de