Taxiing too direct

[kosta]

Hello,

this is an itch I had with a350 from almost beginning and was actually hoping someone would report it...

Does anyone think that taxiing with a350 is way too direct? It feels like driving a kart... and observing the wheel turning/reacting to the joystick movement, I think it's way too direct.

That said... I am no real world pilot, this is only my opinion based on what I've seen with other top-tier addons, and it seems realistic that all hydralics and mechanics between the tiller and the gear have some delay and smoother movement. 

Anyway, looking for some opinions, and I really think this should be addressed as soon as possible.

[Speedbird193]

Yes, it has the ground physics of Mario Kart. Zero inertia on the nose wheel.

[turkintheus]

Yes the hydraulics in real life don't react that quick to tiller inputs

Edited March 17 by turkintheus
Grammar

[Tecika]

does anyone knows how to fix the taxi problem ?

[sunake]

You guys tried lowering the sensitivity? I don't remember what they're called but the top 2 sliders for me are both set to -0.3 or -0.4

[kosta]

Oh don’t come me with sensitivities. This is straight bad modelling.

and yeah… my whole setup is via SPAD.next, sensitivities per profile and aircraft, and I have my €1000 Hotas well tuned. 
 

Ini should fix this to behave naturally. 

[sunake]

Wow. Okay boss man. 

[kosta]

On the serious note… this is often the most called out “fix”, while almost never being a solution. My curve is indeed softened. 

Edited March 17 by kosta

[unairspace]

YES

[Speedbird193]

Yup, major nuisance! I appreciate WASM stability was the main focus for the initial patches but here are my main issues with the A350 right now that I really would like to see patched soon:

• Nose wheel steering sensitivity, lack of inertia and random uncommanded inputs (I use a hardware tiller).
• Beyond ATC auto tune of radios broken.
• Flight dynamics feel wrong and way too sensitive - I flew into EGLL the other day in the -1000, wind was VRB02 and I was being thrown around like a paper plane with constant bobbing to the left/right when hand flying. This is still a 200T aircraft at time of landing and a 2kt wind should not require any manual correction, this isn't a Piper in 30kt gust conditions.
• Uncommanded pitch down/sometimes up after rotation and initial climb (usually between 100 and 300ft AGL).
• No option to define a default panel state (at least let us pick one from the default options, not even asking for a custom one at this stage!).
• Refresh rates on the displays are often very low and stuttery. I always have a minimum of 60 FPS and the displays seem to refresh at 5 FPS or something like that.
• I would love to see 8x sim rate added.

Edited March 18 by Speedbird193

[Eddie]

35 minutes ago, Speedbird193 said:

Yup, major nuisance! I appreciate WASM stability was the main focus for the initial patches but here are my main issues with the A350 right now that I really would like to see patched soon:

• Nose wheel steering sensitivity, lack of inertia and random uncommanded inputs (I use a hardware tiller).
• Beyond ATC auto tune of radios broken.
• Flight dynamics feel wrong and way too sensitive - I flew into EGLL the other day in the -1000, wind was VRB02 and I was being thrown around like a paper plane with constant bobbing to the left/right when hand flying. This is still a 200T aircraft at time of landing and a 2kt wind should not require any manual correction, this isn't a Piper in 30kt gust conditions.
• Uncommanded pitch down/sometimes up after rotation and initial climb (usually between 100 and 300ft AGL).
• No option to define a default panel state (at least let us pick one from the default options, not even asking for a custom one at this stage!).
• Refresh rates on the displays are often very low and stuttery. I always have a minimum of 60 FPS and the displays seem to refresh at 5 FPS or something like that.
• I would love to see 8x sim rate added.

Hello,

Regarding the steering as well as flight dynamics: We will continue to finetune these according to meritable feedback we receieve. These two topics have been heavily discussed and we have assured the community that we did not come up with random numbers to formulate how the aircraft behaves; this is based on realworld data with many type-rated A350 pilots approving of the handling. Nonetheless, like mentioned, this is an ongoing topic of discussion that isn't abandoned and perhaps with some more fine tuning we can reach a result that "feels" just right. 

As for the other points, radio auto tuning proved to need slightly more effort than anticipated but a fix is in the works! We are also working on both default as well as custom panel states; cannot promise when that'll be ready but it's coming 🙂
Increasing the refresh rates of the displays is 1) Not faithful to the real world counterpart 2) A way to decrease performance overall. It is a compromise and a realism factor we value and will most likely not change.
And lastly, 8X isn't out of the question but not something planned as of right now, but again, not out of the question.

Thank you! 

[FelixM]

I have tried different sensitivities and that doesnt change much (Iam using a Virpil, heavy springs and default cams). Also tried my old Airbus thrustmaster, same thing.  The plane feels extremely light in the air. At lower speeds (approach) the roll axis in particular feels really loose. I find it extremely hard to hold the plane steady (at only 4kts wind). I know you cant exactly compare Fenix to Inibuilds, but on the Fenix I have the feeling to fly a big plane. I think the Ini A350 simply needs more inertia. That has already been mentioned above taxiing is like driving a small plastic car. I mean it is just patch 4, Iam sure there will be more to come to address those things.

 

Best regards,

Felix

[ThorCoolguy]

Eddie, I've posted elsewhere about input lag issues being the likely culprit for a lot of the handling complaints. I documented the lag with video, demonstrating that there is at least a .5 second delay between control input and the *beginning* of control surface movement.

 

It could very well be the case that the flight model is 100% perfect and your testers love it - but if your testers are *not* experiencing the input lag bug, but a user is, that user is not wrong that something is way off. Your 100% perfect flight model is working 1/2 second behind the pilot. This is going to cause oscillations like crazy, which is what so many of the handling complaints report.