Ok, here is the deal:We tried and this is not "fixable" - here is why (I'm paraphrasing from the explanation I got from Vangelis):The S-turns happen because of the way FS calculates forces being applied to the airplane while in ASE's DWC mode (any other weather addon doing what ASE does to modify the wind would cause the same thing). When the plane is LNAV (or NAV in the case of the MD-11), we calculate the lateral flightpath on the basis of track, which is true heading+wind correction angle. DWC mode imparts tons of tiny but sharp variations in the wind to control it - it's essentially "slapping" the airplane a bunch of times per second. This creates a force gradient (rate of change basically) that the autopilot senses as a change in the actual vs the target track. It tries to remedy this sensed difference with the ailerons, which produces the S turns and rolls. We cannot just filter this out because there are legitimate instances where the plane would need to respond to such a gradient that would look identical to what you see when in DWC mode.The only way to fly in DWC mode is going to be while using the standard FSX and FSUIPC tweaks to disable the turbulence effects on the airplane and setting the FSX rate of change slider to 25% - that stops the "slapping" effect and the forces on the airplane.

Ok, here is the deal:We tried and this is not "fixable" - here is why (I'm paraphrasing from the explanation I got from Vangelis):The S-turns happen because of the way FS calculates forces being applied to the airplane while in ASE's DWC mode (any other weather addon doing what ASE does to modify the wind would cause the same thing). When the plane is LNAV (or NAV in the case of the MD-11), we calculate the lateral flightpath on the basis of track, which is true heading+wind correction angle. DWC mode imparts tons of tiny but sharp variations in the wind to control it - it's essentially "slapping" the airplane a bunch of times per second. This creates a force gradient (rate of change basically) that the autopilot senses as a change in the actual vs the target track. It tries to remedy this sensed difference with the ailerons, which produces the S turns and rolls. We cannot just filter this out because there are legitimate instances where the plane would need to respond to such a gradient that would look identical to what you see when in DWC mode.The only way to fly in DWC mode is going to be while using the standard FSX and FSUIPC tweaks to disable the turbulence effects on the airplane and setting the FSX rate of change slider to 25% - that stops the "slapping" effect and the forces on the airplane.

Ryan,I fly mostly the MD11 and 747X with the tweaks I posted above, and works to a degree where "S" turns are elliminated and turbulence effecks are restored to a realistic value. ( to a value that would satisfy most) and it has. How it effects the dynamics of the aircraft technically is beyond my expertise, but to me it produces a realistic experience. The values I posted above been tested with the NGX ? Or should they be ignored. Sudden wind shifts are also tamed, and flying in standard mode is not an option due to screen flickering on updates. CheersJulian

Julian,I'll have to try your settings...

Julian,I'll have to try your settings...

Thanks Ryan, might be worth a shot. However, supposing the aerodynamics of the NGX may give different results, if the do let me know and I can tweak some more. (After release )

Ok, here is the deal:...

Thank you Ryan.Cheers!

I've been using Smooth Cloud mode for a long time now in conjunction with FSUIPC for wind smoothing and turbulence supression and it seems to work like a charm.I'm not sure if there is any advantage to using DFW mode vs. using Smooth Cloud Transitions in ASE? I can't use Standard mode due to the screen flickers/flashes and the fact that using Standard mode sometimes results in FPS dropping to the single digits at times.Sean Campbell

I've been using Smooth Cloud mode for a long time now in conjunction with FSUIPC for wind smoothing and turbulence supression and it seems to work like a charm.I'm not sure if there is any advantage to using DFW mode vs. using Smooth Cloud Transitions in ASE? I can't use Standard mode due to the screen flickers/flashes and the fact that using Standard mode sometimes results in FPS dropping to the single digits at times.Sean Campbell

Hi Sean, that mode is more for GA flying, not the big metal.

Julian,I'll have to try your settings...

That's true, those settings work, the very other thing is, that in my case I have absolutely no s-turns when FSUIPC is not installed. To me it looks that there's some kind of conflict between data sent ASE and FSUIPC's weather "options". With above settings you can set dynamic weather to 100%, turn on turbulence effect etc, everything works like a charm :)

I did the tweaks that ASE manual suggests in the FSX.cfg and FSUIPC.ini file and also use FSUIPC wind smoothing and have no problems with S-turns, even with turbulence effects enabled in FSX. Some times the gusts show up at cruise but it is easily solved by disabling wind effects in FSUIPC, waiting 5 seconds until the gusts stop and then reenabling wind effects. This issue doesn't happen frequently, though.

I did the tweaks that ASE manual suggests in the FSX.cfg and FSUIPC.ini file and also use FSUIPC wind smoothing and have no problems with S-turns, even with turbulence effects enabled in FSX. Some times the gusts show up at cruise but it is easily solved by disabling wind effects in FSUIPC, waiting 5 seconds until the gusts stop and then reenabling wind effects. This issue doesn't happen frequently, though.

ASE's manual tweaks are just walkaround, use above settings and you won't have to do anything else, keeping all the ASE's functionality like gusts, windshear and turbulences.

And to this I will remind everyone that every system is different and every plane is different, so please use what works best for you.

And to this I will remind everyone that every system is different and every plane is different, so please use what works best for you.

I agree, however I would like to know the answer to below.

Hi Sean, that mode is more for GA flying, not the big metal.

Why is it better for GA and not flying airliners? I would change to DWC if its better for flying airliners, but I would like to know why its better first. Also, doesn't using DWC mess with the arrival winds sometimes? Currently for me using Smooth Clouds seems to depict the arrival winds and condidtion pretty much spot on 99% of the time.Sean Campbell

And to this I will remind everyone that every system is different and every plane is different, so please use what works best for you.

I didn't know DWC was system specific Jim ? And the PMDG aircraft flight dynamics would be the same on everybody's system in regards to getting buffeted by sudden wind shifts ? Would they not ? CheersJulian

Hi,No, DWC is not system specific, BUT all the different combinations of FSX, FSUIPC, ASE, the plane(s) in question, the phase of the moon, the time of day and the color of your socks all make things hard to generalize. (JK about those last 3 things)Remember also that I was mostly responding to GG's post about the ASE manual's suggestions being walk-arounds, which they are not!

I've been using Smooth Cloud mode for a long time now in conjunction with FSUIPC for wind smoothing and turbulence supression and it seems to work like a charm.I'm not sure if there is any advantage to using DFW mode vs. using Smooth Cloud Transitions in ASE? Sean Campbell

Sean, I fly only jets on medium/short hauls lately because I bought the iFLY 737 FSX, but before that it was all long hauls in the PMDG 747/MD-11, and my choice is to use DWC for one simple reason: you get accurate, as predicted, consistent aloft wind direction and speed throughout the cruise regime. When I used to use Smooth Cloud, I would always get winds that would shift direction/speed causing the autopilot to lose speed and/or altitude in its attempt to reconfigure itself for the sudden speed/direction change, and this would throw off my cruise/climb/descent performance as I would use more fuel than I had predicted (although I did use FSUIPC to smooth winds so that these changes were slow, but they still were a nuisance). And at times, I would lose winds altogether, and was forced to restart ASE. The need for accurate winds aloft is most important for long or medium haul jet cruise performance, and not so important for GA flying. DWC has some disadvantages, namely AI aircraft on the ground or at lower warmer altitudes will display contrails and ATIS reports are unreliable at cruise altitude. I carefully weighed both the pros and cons, and found that I would prefer the wind aloft reliability, even if that introduced visual anomalies such as contrails on the ground or global weather depiction everywhere I fly. And I can overcome the ATIS issue by tuning the radio to 122.02 to get the arrival ATIS anywhere I want (which in a way simulates ACARS reports of ATIS that the big boys use when in cruise far away from the destination airfield, but you have to be sure you have arrival/destination airport info in the ASE flight plan). As I see it, smooth cloud is great if you value visual depiction accuracy above all else, which makes perfect sense in slower GA aircraft. But when I'm flying the big jets, my attention is pretty much focused on heads down IFR operations and keeping track of fuel burn/flight progress, and I seldom leave the VC cockpit to take in the visuals outside. It's a trade off I'm comfortable with, and for a very long time I was against DWC because of the cosmetic quirks, but I ultimately decided that the wind shifts at altitude were too much for me and have been with DWC for the past few months. One last note, 95% of the time the arrival winds at destination are as predicted by ASE, but on two recent flights in the iFLY I had arrival winds (below 1000 feet) that were the reciprocal of expected winds, leading to a tailwind condition that suddenly shifted to the correct winds right at flare. I must admit those were unpleasant to witness, but hopefully they were a fluke, and they only happened two times so far.