9 replies to this topic

[Alcom Isst]

I just had a two hour fiasco involving MWO settings and Joystick Deadzone. Apparently, the new UI 2.0 Controller settings effects are separate from the system.cfg settings effects. This seems to include sensitivity and deadzone. Before I make something formal out of this topic, I just want to check if this is true for everyone else.

Edited by Alcom Isst, 04 February 2014 - 02:56 PM.

[Loc Nar]

Analog controls have been broken again. Last 2.0 test they assured those of us with concerns that there would be a third column for analog controls by the time it's implemented and it is not there, and apparently those of you unfortunate enough to rely on the .cfg (does not hold a candle to what you can do with 3rd party software...) for controls are also hosed.

I love how casually they cast aside people's primary controls with zero regard, as if controls are some minor detail or an afterthought.

I am so unimpressed, and so not surprised.

I am in idiot. Controls are fine. Settings can be viewed/altered from the lower right of the screen in the UI.

Edited by Loc Nar, 04 February 2014 - 10:22 PM.

[Evogenesis]

Ever since I did the magneto mod for my saitek I've had no problems with sensitivity or deadzone. Guess I'm going to have to log in and see.

[Aahz HHGD]

Alcom Isst, on 04 February 2014 - 02:54 PM, said:

I just had a two hour fiasco involving MWO settings and Joystick Deadzone. Apparently, the new UI 2.0 Controller settings effects are separate from the system.cfg settings effects. This seems to include sensitivity and deadzone. Before I make something formal out of this topic, I just want to check if this is true for everyone else.

This was my experience as well.
Two hours or better of playing with it and its better but still not right
turning the mech left to right is sluggish and heavy while Torso twist is extremely twitchy and over sensitive

in user config the old settings were:
cl_joystick_sensitivity = 0.75
cl_joystick_gain = 8

They are now:
cl_joystick_sensitivity = 2.4
cl_joystick_gain = 20

this made very little change
but it did help

[MnDragon]

I've had the issue where the cl_joystick_* lines were being unrecognized. None of my user.cfg settings are working ever since the UI 2.0....

[Lightfoot]

I just turned down the sliders for X and Y and lowered the deadzone. Sometimes I need to re-adjust this because it changes from the first launch to be very sluggish, but it settles down after that usually.

[evilC]

Be aware that if the game settings do not work well for you, another option is to change how the joystick reports to the OS.
Suggest maybe setting dz to 0 and sensitivity to the middle setting in MWO, then using software to alter how your stick behaves.
If your stick came with config software, you can use that, else you can use an app I wrote called UJR (See sig).

[Shamous13]

MnDragon, on 05 February 2014 - 05:25 AM, said:

I've had the issue where the cl_joystick_* lines were being unrecognized. None of my user.cfg settings are working ever since the UI 2.0....

Some people have reported their user config not working and it is believed (not confirmed yet) the game looks for "prohibited" settings, and just disables the whole cfg if it finds any.

[MnDragon]

Shamous13, on 07 February 2014 - 06:18 AM, said:

Some people have reported their user config not working and it is believed (not confirmed yet) the game looks for "prohibited" settings, and just disables the whole cfg if it finds any.

the Omicron.txt file seems to be dump log for each session you load and basically goes through everything you do. Each map you play, everytime you go to the mechlab etc. It was where I found the "cl_joystick_* unrecognized command" BS that led me to believe the user.cfg was no longer working. Based on your statement above, I did some experimentation and dropped everything but the cl_fov= line. I didn't get the warning line as I had before when I had the joystick lines in the .cfg. So I would venture to say that this is an accurate statement. If you adjust your user.cfg to only incorporate lines that are still used by the game, (obviously the joystick lines are no longer needed, the UI does the same thing) it should work.

[Hammerhai]

joystick commands have been recognised as errors in user.cfg since CB. So that does not necessarily mean they do not work. However, some commands such as throttle_range = 0 most likely do not work anymore and have been disabled. You would now select "FULL" throttle range in UI to get the same effect

'Fraid it is a case of try and see for yourself atm whether or not commands are functional