majorursa

I was thinking along the same lines recently, but especcially with regard to weather. FS in combo with ActiveSky (and FSUIPC of course) would be an excellent way to visualize the conditions at a destination and make the rather dry METAR data more tangible. Again not reliable but an aid to reduce the number of surprises. Ursa.. PS. Thanks for 3.30

That would be excellent. Again, if it'd mean adding extra complexity please feel free to leave it out. It was maybe the coincidence of meeting this weathertype while being very FSUIPC-aware at that point in time. Maybe in another two weeks I would have dismissed the anomaly as just 'one of those things'. Anyway, I hope you'll see it as a compliment. Ursa..

Yes, that would be fine, or only switching it on when the plane is off the ground. I think the number of complaints might be reasonable, about the same number that 'complained' about the visiblitly being 38km at startup when 5000 is in the METAR :-). Yes, it mostly is. Problem is that the situations sometimes changes drastically while preparing, meaning an IFR departure when just before I could see the mountainline at the horizon. As I said, no big issue; more of a 'let you know'. I'll experiment with the smoothing-timer. Thanks for answering; I'm really gratefull for all your efforts. Ursa..

Hi Pete, I load AktiveSky after FS is loaded completely and I'm in the cockpit. At that point FS (and FSUIPC) have already initlialized some kind of default weather. When AS injects its first update the visibility smoothing (10% in 30secs in my case) kicks in so that the actual reported weather will be only completely accomplished after some minutes have passed. It is just a minor issue of course but I wondered if it was possible to make FSUIPC recognize this situation in a furure release and pass the first update directly before setting the smoothing tempo. Or is this to complicated? Ursa..

Yes, it mostly is obvious. However, the mixture of upper- and lower-limits and priority of settings makes this a bit hard to understand, I think. Once the picture is clear it is hard to see what was so difficult before, and hence hard to explain again to the next person :-). Ah, some randomness also, I love that. Is this lineair randomness or is the weight towards the upper-limit? Thanks again, where woudl we be without you, Ursa..

and together would mean that the FSUIPC setting overrides only if it is smaller than the METAR. Is is safe to say that always the smaller number prevails? It's almost obvious now but somehow I didn't get this from the docu. Thanks Pete, for the answer; from other posts I noticed what an incredibly patient man you must be :-). Ursa..

Hi all, I searched really hard for an answer on the forum and in de docu but it is still unclear to me how the parts fit together. The simplest question is: if I select all *** vis-toggles and fill in values, what happens to the visibility that eg. AS2004 injects from a METAR? So suppose METAR says a vis of 7000 and according to my settings there should be an vis.limit of 50 nm. Will there be a visibility layer and if so how thick is it. Is there somewhere I can check these values? I have some other questions too but they may need rephrasing after I understand the answer to this question. I would be very gratefull for some light on this. Ursa..