ardypilot wrote:Being able to change the weather variables and time of day in real time is pretty neat too
ardypilot wrote:One thing I had noticed is that when I run the extended desktop feature on Windows 10 to use my laptop screen as a second screen for the moving map, my FPS jumped from in the 60’s to in the 90’s! Does Windows 10 have the ability to combine both CPU’s to drive the software on the primary machine, or am I seeing a misleading combined value of two computers worth of frames displayed on one screen?
ardypilot wrote:I’d also be interested to know if anyone else is experiencing overly sensitive control surfaces? In particular, elevator and rudder at slow speeds seem to be far more effective than they should be based of basic principles of flight. I’m running a Logitech Extreme 3D Pro joystick with the following sensitivity (significantly decreased from default):
Adamski wrote:Have you tried the freeware Unreal Weather - Live METAR mod? It may save you some money!
FlyingKiwi wrote:.You can see it in your screenshot of your sensitivities the way the input curves suddenly go almost vertical
ardypilot wrote:FlyingKiwi wrote:.You can see it in your screenshot of your sensitivities the way the input curves suddenly go almost vertical
Hey Leo- that makes sense. Given that logic, I think I might have FSUIPC set incorrectly, exaggerating the perceived sensitivity problem rather than solving it. If you wouldn't mind posting a screen grab of your FS20 sensitivity settings page for reference, that would be much appreciated.
FlyingKiwi wrote: I don't think the issue is the sensitivity so much as the scaling ... this is what, I think, causes the problems with the controls being massively over-sensitive at low airspeed - because the flight model correctly represents that much larger control inputs are needed at low airspeed due to reduced dynamic airflow over the aircraft surfaces, but that causes you to enter the realm of sudden acceleration of the control value which causes sudden 'spikes' in control inputs and leads to oscillations.
Adamski wrote:However - I'm wondering whether the axis sensitivity values in MSFS are still processed even when they're not assigned - it's hard to tell.
ardypilot wrote:I have recently invested in purpose-built PC for FS2020
Aharon wrote:Care to share with us what is your computer configuration please that successfully handles MS2020 as seen in your AMAZING screenshots!!
Naki wrote:Yes you need a small Japan update in the content manager. I’ve just installed it.
Adamski wrote:@ardypilot - thanks for the FSUIPC tip - I'll give that a try. It may help a little, but I really think it's the "ground effect" that's the problem, as sensitivity is generally OK at other altitudes.
ardypilot wrote:A thought just crossed my mind- I think I still have auto rudder enabled which might be responsible for the horrible yawing close to the ground on final approach and in the first few seconds airborne. I haven't read up too much on the flight model options under the general settings menu but note that mine has been set to 'Modern' this whole time. I think my next port of call before I go meddling with .ini files might be to have an experiment with the 'Legacy' preset and have a play with the P-Factor slider too...
Lindstrim wrote:Too bad you can’t claim that at work
Users browsing this forum: No registered users and 4 guests