Hello all,I just upgraded from AS2004.5 to ASVE. Very nice job!I am having one problem that I also had in AS2004. That is, I will have a pretty good tailwind showing on my nav display, but my groundspeed will be less than my TAS. The tailwind affects the groundspeed as if it were a headwind. I've attached a picture for better clarification.Most of the time it shows correctly, but sometimes I get this.Any help is appreciated!Thanks,Christianhttp://forums.avsim.net/user_files/133540.jpg

Hi,Thanks for the update!Can you try with a default plane and panel?What does the Shift/Z readout show for the winds?Hope this helps,JimActiveSky Sales and Supporthttp://www.hifisim.com/images/asv_dev_team.jpg http://www.hifisim.com/images/asv_proud_supporter.jpg

hi,I have the same problem,; also with headwind I got GS>TAS. I can't figure out why this (often) happens.Could it have something to do with FSUIPC ?hoping to find help here,greats Patrick

Hi,Does the Shift/Z readout pretty much match what ASV is giving?Hope this helps,JimActiveSky Sales and Supporthttp://www.hifisim.com/images/asv_dev_team.jpg http://www.hifisim.com/images/asv_proud_supporter.jpg

I want to add that I'm also getting some very strange wind behavior with ASVE since I upgraded to FSUIPC 3.51. I had a direct headwind of 98 knots, but with a true airspeed of 450 my ground speed was 398 knots, not right. With FSUIPC 3.50 everything was find. With FS weather themes the numbers came out right.I'm about to do a test flight with FS real world weather to see what that does. I'll report back in a few.

Hello again,I have had similar problems. I know in FSUIPC 3.51 there was a comment in the release notes that said it had fixed some issues regarding head/tailwind and groundspeed. I'm still having some interesting issues...not sure if it's ASVE or an FSUIPC issue, probably the latter.The first issue is the same as before. As pictured below, I had nearly a direct crosswind, but my groundspeed showed a 45 knot tailwind. I did Shift-Z and it showed the wind to be the same as on the ND 263/62. But, it eventually worked out and showed correctly...about every 5 seconds the groundspeed would decrease until it was correct.The second issue is with the FMC, so probably a question for PMDG, but I'll post it anyway. The wind/TAS/GS on the ND looks correct (tailwind), but the FMC shows a 2 knot headwind.Anyway, these problems are strange! Any advice is appreciated. I will also ask around the PMDG and FSUIPC forums.Thanks,Christian

Ok, I've done a bit more testing and the descrepancy on the ND of the PMDG 737 concerning wind,TAS, and GS is only when running ASVE and FSUIPC 3.51.FSUIPC 3.51 with FS real world weather, or an FS weather theme shows the correct TAS vs. GS based on the winds.FSUIPC 3.50 with ASVE, FS real world weather, or an FS weather theme shows correct TAS vs. GS based on the winds.

Hi Dave,Thanks for the info on your testing. I think I will use 3.50 for now, as it seems to be correct.Thanks,Christian

Hi All,But we also know that both FSUIPC 3.51 and ASV were tested before Pete released it and we also know that Pete has not found any code errors. Once again we would like to know what the Shift/Z reads in FS04.Also, we will suggest that you try a default plane with a default panel and see what happens.Hope this helps,JimActiveSky Sales and Supporthttp://www.hifisim.com/images/asv_dev_team.jpg http://www.hifisim.com/images/asv_proud_supporter.jpg

Hi Jim;Ok just complete the test you suggested. Used the default 737-400 cruising at FL320 with ASVE weather.heading: 259wind: 259 at 46ktstrue airspeed: 436ktsground speed: 467ktsStill not correct.

Jim,I've just loaded up a saved flight at FL360 enroute to KSEA from KDFW flying the PMDG 747-400 with ASV (running an offline sequence) and FSUIPC 3.51 (registered) and the windspeed/direction that I get with shift-Z are exactly the same as what I get on the display in front of me, showing a headwind of 23KT at 309 with a current aircraft heading of 290. The display also reads a groundspeed of 494 with a TAS of 491 suggesting a 3KT tailwind. The FMC progress page reads a wind of 328/23 (true heading I presume) giving me a 21KT headwind with a 9KT side component. So the wind numbers all appear to be consistent, but GS and TAS show something different.When I jump into the default 747 I get the same windspeed and direction with shift-Z and a groundspeed indicated on the GPS of 490KT so I assume I'm experiemcing the same problem in both the default and PMDG 747s. I've also noted these problems with FSUIPC 3.50 before I upgradedIs this at all linked to the problem with the ASV variable winds and temps at high altitudes causing problems, something that I'm also experiencing, because I note that as the plane slows down/overspeeds when the wind/temps jump around, TAS and IAS vary while GS remains relatively constant.Hope this helpsDavid Smith.

Besides the GS/TAS problem,I also experienced at different occasions a shift in speed ( about 120 kts) and in VS (from 2000 to more than 11000 ft/sec)and this in approx a sec or 2.my config : PMDG 737 / ASVE / FSUIPC 3.51I just wonder if these problems have the same cause and if other flightsimmers had the same ?thanks, Patrick Dochy

Hi Christian, all,I have started some testing on this and opened up a dialog with Pete Dowson. Will report back with some findings and hopefully a quick solution! :)Best,

Hi Damian and others;I've also been corresponding with Pete about this and it appears that a solution, maybe several, has been found. Check out the thread on the same topic in the Pete's support forum, which can be found from his site.Basically, it appears that ASVE was attempting to get around a long-standing bug in FSUIPC which was fixed in 3.5.1 and thus broke ASVE's work around. Pete has released an interim update, 3.5.1.1, which has an option to turn on or off the reverse wind sensing near the aircraft. With it off, ASVE works fine.The other solution appears to be to turn off ASVE's 'direct wind control' setting.Damian, I'd love to hear if you can confirm any of this. Hope this helps.

Hi Damian,Thanks for the quick response and determination for helping find where the problem truly lies. Seems to me that Direct Wind Control is causing the error, but I like to leave that option on for more accurate winds aloft.For now, I will use 3.5.1.1 with the appropriate .ini entry.Thanks,Christian