Needless to say there are many reasons to have to go into a menu unfortunately. Maybe I need to go into FSUIPC itself to tweak something or add a new button assignment or some such option. For instance I tend to have to go and reduce my scenery density or autogen sliders at times when getting to a heavily built up area because my frame rates drop too much. The systems you have in place now work extremely well as long as you don't need to go into a menu and change any settings, which for some people is unavoidable I'm sure. As you probably know far better than me winds can very often be as much as 180 degrees out to what they were 1 second ago in FSX and within a few seconds it can be back to where it was again, by which time the complex custom autopilot has tried to correct for the change only for it to be completely wrong again. The reason its become an issue is because the new autopilot systems in the likes of the PMDG MD-11 and Level-D 767 get very messed up when the winds or wind speeds shift suddenly which most of the time result in a stall or overspeed condition. I sorry if this is a really stupid comment/question but I'm no programmer in any sense of the word, but I imagine from your response that it is a major thing I am asking for, and the last thing I want to do is create any more headaches for you Pete :lol: Can you not stop your time keeping when you see the user enter a menu. It does get quite complicated because it is all based on averaging over elapsed time. Perhaps if you tried a more reasonable 1 or 2 knots/degrees per second you might not get such violent effects? After all the idea of smoothing is to smooth changes, but still allow them to happen reasonably timely. Maybe the use of ASA now has somehow induced more distant target for FSUIPC to reach? Certainly if you have smoothing set to 4 seconds for every knot or degree of change i should think it will hardly ever actually catch up with any wind changes. If FSUIPC insisted on smoothing continuation after returns from the menu it would make it very difficult for folks wanting to set weather explicitly or even loading a new flight with its own weather already saved.įSUIPC's wind smoothing (and all the other smoothing actions it did in FSUIPC3 too) have always done this, for 7 or 8 years now. Slam, a huge wind shift causing a 50kt drop in indicated airspeed.įSUIPC cannot differentiate the reason for going into the menu system, it is just told by SimConnect that simulation stopped. I open FSUIPC and immediately exit to FSX. Here is a typical scenario (just tried it again): I'm in cruise with winds apparently stable (i.e. the target weather, not the weather en-route to the target at n knots per second. Effectively when you come back to flying, you get the weather you should have - i.e. So, if you are using FSUIPC's wind smoothing, it doesn't smooth across Menu excursions.
There's no way FSUIPC knows what you are doing in the menus.
LEVEL D 767 FSX SLOW WINDOWS 10 DOWNLOAD
Not FSUIPC no, it isn't really running then, but it doesn't smooth the wind setting it sees set when you exit menus, because you might have been in the menus to download new weather or manually change the weather.
Is FSUIPC somehow buffering up changes that get released instantly when coming back from the addon? This is not much of a problem, but I'm wondering why it occurs.
open FSUIPC or edit PMDG failure options) while in flight, when I return to FSX I always get a big wind shift, resulting in an altitude and/or speed excursion. However, I've noticed that if open an addon (e.g. I have the smoothing set to 4 seconds per knot change which completely eliminates wind shift problems.
0 kommentar(er)
