Barbs Posted May 9, 2011 Report Share Posted May 9, 2011 Hi Pete, Hope you had a great weekend at your daughter's. :) I have a problem that I've had for a few months but have only now noticed it may be something to do with FSUIPC. It has to do with the wind gauge on some of my addon aircraft not displaying the current wind conditions. In fact it appears that the gauge is "freezing" or not updating when the wind conditions change. This will have the following effects.... 1. When on instruments the aircraft appears to be tracking incorrectly for it's given heading (eg. tracking to right of heading when indicated winds give a cross-wind from the right). 2. When visual around an airfield the aircraft attitude required to maintain a xwind approach is contrary to the indicated wind conditions. Example: Today I was flying a right downwind to runway 16R at Sydney Intl in the Wilco A330. Winds on the ND were indicating 130deg/15kts and I was heading 340deg. The track indication was showing as about 347deg (or to the wrong side for the given wind reading). Now here's where it gets interesting. The VATSIM METAR and the Wx being injected from ASE was for winds at 220deg/24kts (which more appropriately explains the tracking indication). Also on final for runway 16R I had to account for a xwind from the right (220/24 again matching the METAR) when the indication was still giving a xwind from the left. So why do I think this has something to do with FSUIPC? Well I discovered today that by opening the FSUIPC window and closing it again, the wind gauge returns to where it should be. Then after several miles of flying it starts to disagree again, so I bring up the FSUIPC window again and it returns to normal. Boring stuff: FSUIPC is a registered version. Version 184.108.40.206 FSX SP2 Win7 64 bit. FSUIPC weather is disabled. Weather supplied by ASE. Happens with both Wilco A330 and another 737 that I'm beta testing. These are the only two aircraft I fly in FSX that have a wind gauge. If it was a problem with the addon I would have thought it would happen on one and not the other. Any ideas??? Greg Link to comment Share on other sites More sharing options...
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!Register a new account
Already have an account? Sign in here.Sign In Now