At first I thought these problems were the result of the newest FSUIPC, but I found that un-checking AdvDisplay in the Modules menu causes the problems to cease. With AdvDisplay checked, each time I change view, visibility defaults to my max setting (graduated in FSUIPC from 0 to 15000 Ft with max at 70 miles) and then in the space of one second or less, it lowers to the minimum I have set for that flight. Values also remain unstable. If I set 10 miles minimum at ground level then start flight, min value will change to 20 or even 30 just during taxi. Max visibility Altitude in the weather menu is also unstable, changing from 0 to 10,000 or 100,000 Ft at random. These problems continue even with all visibility settings un-checked in FSUIPC. Has anyone else encountered these problems ?Thank you,John M

might be worth emailing peter dowson about this

>With AdvDisplay checked, each time I change view, >visibility defaults to my max setting (graduated in FSUIPC >from 0 to 15000 Ft with max at 70 miles) and then in the >space of one second or less, it lowers to the minimum I have >set for that flight.I noticed the same yesterday. Didn't connect it with AdvDisp, though. Time to mail Peter, I think.

Sometimes, if I'm changing some values within FSUIPC (2.94/2.95) and click ok or cancel, external weather settings won't send to FS anymore.You can see wind or ONH changes within weather programs like FSMeteo or wxRE, but these values could not reach the sim - after activating FSUIPC's control desktop.Who writes Peter? ;)

Thank you guys. I have been corresponding with Peter for the last day or two. I did not realize that the AdvDisplay module was his department and not an RC creation. I must commend this fellow Peter for his attention and persistence in trying to solve this problem for me. Like Simon Evans, Peter can come off a bit gruff in his emails, which I just attribute to a certain European writing style. Probably not that way in person whatsoever.Microsoft should be paying this chap a hefty commision for all the incredible interfaces he has created for them and us.He had actually been wrestling with the info I provided him until 6 PM my time, which turns out to be 3 AM his time ! He finally retired for the night promising to attack it the next day. -That is dedication. I will share the results of his research. I have also noticed that the RC folks have responded to several inquiries from myself (an RC novice) almost instantly, no matter what time of day or night. I am not a computer guy so I appreciate this kind of dedication.Take care,John

It's also interesting to note that not only visibility is affected. You can also note wind speed changes when switching back and forth from windows with and without advdisplay. I sent a mail to peter about this and he told me there was no way advdisplay could be affecting weather (visibility and wind speed)

Well it looks as if RC3 will have to wait for a new system. To solve my visibility problems I have had to revert back to FSUIPC 2.94 which of course means I can't run RC3(no voices). After removing AdvDisplay I still had problems. Visibility maximums varied wildly and at random during flights. One view would be 20 miles, then switching to spot view would be 60 miles. After a minute I would pause the sim and check the weather menu and it would be at, say 30 miles. After reverting to the FSUIPC 2.94, visibility problems finally stopped. I tried Nvidea tweakers and all sorts of other remedies but only the older FSUIPC seems to have solved these weird problems. I really enjoyed RC3 for the brief time I was able to use it, but it was just not meant to be. I will keep the CD handy for use on a future PC. If anyone can explain how FSUIPC 2.94 could possibly work with RC3 that would be fantastic, but for now I will have to drop back 10 yards and punt.Take care,John M.

Hi John,It's been awhile but I recall having the first problem you mention when I first installed RC (when changing windows visibility would briefly go to max, and then drop back down). I did not experience the other problems you mention.At the time, as I recall, my problem went away after I deleted the old FSUIPC.ini file and started off fresh with the new FSIPC version. Not sure if this will help you but I just thought I'd mention it.Best regards,Vic

Thanks Vic, but I did try that several times with no luck.Take care,John