I believe that the controls are generally too sensitive particularly in slow flight conditions to the point of it being unrealistic. A linear sensitivity mechanism would help but I feel like they need to modify the dynamic to account for more / less air flowing around control surfaces. And yes, lack of resistance on joysticks also doesn’t help things. That was the first major difference I noticed when I started flight training.
I have set the curve back to almost linear and reduced the effectiveness as per my post above, and in my case it made a very positive difference.
It’s up to each individual I guess.
Cheers
Posting my mistake here in case anyone else made the same error - I noticed there were two input boxes for each assignment so for each axis, I assigned the + and the - to each respective box. This resulted in extreme sensitivity past the half-way mark of each axis.
However by deleting the second box assignment and only assigning one way in the first assignment box, my issue was resolved.
Yes reference the slow flight condition, if you look at a some videos can see how much more you have to move the controls to be effective. Do the same in the sim (with the small GA aircraft, I haven’t played with the larger aircraft) while watching the yoke or stick movement and it’s noticeable smaller.
Thanks for that, I’ve just adjusted the 152 and now it seem to control a lot better to me. I went for 0.3 elevator, 0.7 aileron and 0.6 rudder. Now the yoke actually moves back when you rotate and flare more like the real thing rather than just moving a fraction. Maybe not completely accurate, but closer than the default.
I am a real first time user and read a bunch of things and I am also facing a extreme sensitivity. I have tried and played with some settings, but hardly no effect. I have tried to do the first flight-training to learn about contols, but as soon as I come to control it by my own I cannot get the plane under control. It is rapidly going down or stalling. Very very difficult to handle. I am using a Logitech Force 3d pro.
I have played with FSX in the past and this was far easier to get in control (also needs a lot of trying but I have has success) . At this moment I am a bit disappointed.
Maybe someons can help me with first practise.
Set your sensitivities to linear and try the settings I just mentioned above, then if you want to turn the sensitivity a little down from there adjust the sensitivity curve
Probably many don’t know, you need first to adjust it on the Windows
-
Type the word control in the windows search field on the taskbar. Click the control app icon. Find Printers and Devices and click it. Find your controller, right click it and go to properties. There should be a settings tab at the top. There should be a calibrate button at the bottom. Follow the instructions.
-
Second adjust in MSFS sensitivity
This doesn’t do much about the built in curve
No, so I leave the curve alone.
The issue I was having was that it was simply too sensitive across the full range.
Applying a logarithmic curve just made it worse IMHO.
So a linear reduction worked for me.
No I mean, the curve that you have no control of, beneath the sensitivity curves. There’s no possible way for me to have linear response regardless of what I do, and I haven’t found the code in the actual config files of the sim where the ■■■■ curves are preset which is killing me. I don’t understand, why I can control aircraft just fine with my joystick in xplane, and now all of a sudden people are popping up left and right saying that my extreme 3d pro doesn’t have enough travel. I’m seriously hoping this is addressed on tuesday.
Sorry I’m confused. Can you post a screenshot.
I would try a different controller just to see if isn’t some issue with the potentiometer in your joystick.
Also, I wouldn’t be focusing so much on what the graphic image of the aircraft controller is doing and I would focus more on how the plane actually responds to control inputs.
What you might be seeing is the sims way of deliberately introducing lag to make a large plane “feel” big. This lag might be making the graphic display of the controller look odd, but it’s only an image.
I’ve updated the original post with the information we have atm. Thank you all for adding solutions and information to this issue.
Unfortunately the problem you have will happen with all controllers that have a slider/knock with a deifnate startt end point. If the AP, or any other thing “moves” the trim, there is no way for the simulator to move the knob/sider to a new position, nor does it have any way of “setting” the knob or moving a slider to an initial value or AP adjusted position (like on a real plane, see trim and sliders moving by computer control), as the controller would need to be far more complex with motors and actuators which woudl be expensive as well as requiring special drivers/plugins to control them, as they will not be standard, so you will have to set them at the start, or when the AP changes the trim or thrust, you will have this issue, and baring expensive hardware, there really is not much you can do, espcially thrusters, you just need to be aware.
There may be a few solutions for trim though, a “continous wheeling” clicky wheel, similar to a mouse wheel, is best in this situation, however, i dont see many such wheels on joysticks, but if you have a spare mouse, maybe you can plug that in, and map its mouse wheel for trim, and its left/right buttons for something?
Well, I guess a solution (on the developer’s side) would be to read the state of the hardware slider and set the in-game knob to the according position.
You’d then still have to adjust your slider before takeoff, but at least there wouldn’t be any “jumpy” behavior, right?
I like the idea of a second mouse. I am sure I have several lying round. Not sure how Windows behaves when I plug one in! (not in Windows ATM or I would try and find out)
Your problem may be, that you have assigned aileron left/right and elevator up/down instead assigning them to each own axises.
But if you have, then ignore this.
-eelis-
yes, but as i said above that would be fine for aircraft that do not have an automated controllers that can be overridden or controlled by the FMS, or AP, but that breaks down the moment you have such things on an aircraft, such as the A320. the computer woudl update the throttle trim, or any other position (just like on a real plane - look at videos showing the trim wheel and throttles moving on their own) however, your joystick is still on whatever position you last set it, so when you manually move any of these, your movement will overide any position the autopilot had it in, and it will “jump” to the new position. Sadly there is really nothing you can do about it, norr is there anythign the devs can do about it either, its a limitation of the controls you are using, in that they are positional based, rather than movement based, sometimes knwon as absolute, as opposed to relative, and unless your controllers can have actualtors/motors to move the sliders/dials, that how it will always be. The only solution for the dials (trim etc) is to have a controller with a continous movement (ie like a mouse wheel rather than a old school volume knob). This is why Modern hifi’s have volume knobs that can be continously turned, so that the voolume cna be adjusted by remote as wella s by the dial, and there is no need for a momtor to “move the dial” when the volume is adjusted by remove, as the wheel only measures movement, not position.
AS for why they the trim/pitch/throttle are not set to the actual controller values at startup, there is a reason for that, but its very complicated, and down to the way calibration works on windows (i think from version 8 or 10). But essentialy calibration is no longer an manual task that needs to be done via the control panel, but instead its automatically down as you use the joystick, the drivers calculate the maximum extents, and calibrates itself, also there is usually smart calibration on the joystick itself, especially USB ones due to reasons that are too long for here.
but until the full extents are known, any value “read” as a position cannot be trusted by the software/drivers/etc. Ineed the axis coudl even be faulty, and may not move. So many reasons why on initial start the actual position of the throttle is not set to the physical stick, until a movement is registered.
This is why, when i am started up sitting on a runway, or at a parking spot, i move all controls to maximum and minimum, to a) calibrate them, b) tell the system i am using them.
Ironically this is somethign you shoudl do in a real plane too! (move all controls to full extents to test they work correctly, whilst still on the ground, engine off and not moving)
EDIT: Apologies for poor spelling, sadly i am dyslexic, i hope you can read what I typed.