Jump to content

- - - - -

Controls, Config And Console?

controls joystick cfg config console commands

14 replies to this topic

#1 KulaGGin

    Member

  • Pip
  • 12 posts
  • Google+: Link
  • LocationUkraine

Posted 29 December 2013 - 01:59 AM

Hey guys. I just signed up on mwomercs.com, downloaded and installed the game. I've even played few minutes. My first impression of the game:"OMG WTF. This game will become my favorite. Definitely".

I used to play in different fps and aviasims like Battlefield or WarThunder on different platforms: PC, PS3, XBOX360 etc.

First of all I want to set up my joystick. Of course in the menu there are no any way to set up your joystick qualitatively. But I've found some old topics about joysticks and config files(user.cfg) where guys explain how to set up joysticks. I've found another interesting files [redacted]. There are a lot of interesting stuff. But I need to have full list of commands. I've found few commands on the forum like cl_joystick_deadzone but this is not enough. Where I can find full list of the commands?

Console. Every time I change something in my user.cfg, I need to restart my game. Is there any way to load my config from the game? Is there console like in Counter-Strike or something?

I noticed that you can set settings via user.cfg:
cl_joystick_deadzone = 0.15
And you can do this via [redacted]

Is there any difference between methods? Maybe I'm able to set some setting using only [redacted] and some using only user.cfg. Or maybe I can set any settings in any file. What do you think?

Anything else I should know to play this game comfortably?

P.S. And yeah, my english is pretty bad so take it easy.

Edited by Egomane, 18 May 2014 - 08:34 AM.
Please do not touch those files


#2 Hammerhai

    Member

  • PipPipPipPipPipPipPipPip
  • Bad Company
  • Bad Company
  • 1,001 posts

Posted 29 December 2013 - 03:20 AM

You should not modify [redacted]. Viterbi said in a post a long time ago it is now verboten. Stick to user.cfg

Also remember that some commands throw errors in omicron.log but are actually necessary and still work. Pretty much all cl_joystick commands do that. You will need to do your axis inversion partly in the user.cfg (Throttle) and partly in options in the client. (I think Joystick y axis) Kludge, but that is how it is.

Increasing cl_joystick_gain increases movement of the reticle for larger movements, increasing cl_joystick_sensitivity DECREASES sensitivity for small movements of the joystick. You will have to restart to test new settings, sorry, no console for us end users.

And be aware you have chosen hard mode by playing joystick. PGI control scheme is abominable, and favours mouse and always will. See this thread http://mwomercs.com/...ls-demystified/

Good luck

PLEASE read this thread.

http://mwomercs.com/...joystick-users/

Edited by Egomane, 18 May 2014 - 08:35 AM.
removed file name


#3 Arnold J Rimmer

    Member

  • PipPipPipPipPipPipPip
  • Civil Servant
  • Civil Servant
  • 892 posts

Posted 29 December 2013 - 03:24 AM

First: welcome!

If you decide to stay with joysticks, though, try this thread. It might help you (but might take a bit of setting up).

Hammerhai covered the meat of it, so I'll answer your last question.

I'd recommend disabling 'Start in 3rd person' in Options, bottom left. At least after you've become used to moving your legs separately from your torso. Then also disable Arm Lock and Throttle Decay. I find the game much easier to control this way - so might you! Your situational awareness and ease of control actually increase by confining yourself to a metal box and giving you more things to keep track of.

PS - your English is better than that of many native speakers. It's certainly better than my Ukrainian or Russian!

#4 Redshift2k5

    Welcoming Committee

  • PipPipPipPipPipPipPipPipPipPipPip
  • Stone Cold
  • Stone Cold
  • 11,975 posts
  • LocationNewfoundland

Posted 29 December 2013 - 05:54 AM

I can't speak about joysticks, but I do want to add my .02 c-bills regardig being a rookie player.

I have two links in my sig. Follow them, collect 8 free days of premium time, activate that time in the mechlab, and use it to multiply your 'cadet bonus', a free bonus you receive for each of your first 25 matches. This will give you even more easy to put towards your first mech(s).

Use the Smurfy database to read about mech hardpoints, engine sizes, etc. Red about weapon systems. Read about modules & equipment. Read about heat penalties. Use the smurfy mechlab function to experiment with mech builds and view a mech's hardpoints.

And don't be afraid to ask questions from the helpful crew here in the new player help area ;)

#5 KulaGGin

    Member

  • Pip
  • 12 posts
  • Google+: Link
  • LocationUkraine

Posted 29 December 2013 - 06:47 AM

What is the maximum cl_joystick_gain? There are no difference between 100 and 10. It looks like maximum mechwarrior gain is between 6 and 8. Or maximum gain is unique for different mechwarriors?

#6 Hammerhai

    Member

  • PipPipPipPipPipPipPipPip
  • Bad Company
  • Bad Company
  • 1,001 posts

Posted 29 December 2013 - 11:00 AM

From about 13 onwards you should have very quick mouse like movement with smallish joystick deflections. And no, it is not different for different mechs. Note that there is a tradeoff between speed and accuracy at smaller deflections, you pretty much cannot have both. A value of 100 should, if it is accepted, be unplayable. Period.

First thing to check: Is the user.cfg in the Mechwarrior Online main folder?
Is it named correctly? It is easy to save it as user.cfg.txt which will not work. In notepad make sure to choose the save option "all files" rather than text (.txt) and enter user.cfg as the name.

Here is my user.cfg. Anything with a semicolon in front is "commented out" and has no effect. Lot of junk in here but I am too lazy to clean house. You may or may not want to comment out the throttle range command, as it puts the stop zone in the middle-ish, so you push forward to accelerate and pull back to slow down


;=================================================================================
; control settings / fov / sensitivity
;cl_sensitivity = 0.25
cl_fov = 81 ; maximum without distortion
; cl_fov = 70 ;experimental
;cl_sensitivityController = 0.1
;i_mouse_accel_max = 100
;i_mouse_smooth = 1
;i_mouse_accel=0

cl_joystick_gain = 8 ;cl_joystick_gain = 13; cl_joystick_gain = 5
cl_joystick_sensitivity = 1.10
;cl_joystick_sensitivity = 1.25 ;setting was 0.7/1.05/1.14
cl_joystick_throttle_range = 0
cl_joystick_invert_throttle = 1
;cl_joystick_invert_pitch = 1
; cl_joystick_invert_yaw = 0
; cl_joystick_invert_turn = 0
; i_joystick_deadzone = 0.25 the syntax may be incorrect
i_joystick_buffered = 0 ;supposed to increase sensitivity

;default high settings
;Mouse Options(disables mouse smoothing and acceleration). Now done in client.
;i_mouse_smooth = 0
;i_mouse_accel=0
;set mouse speed (0.1 with windows 6 setting for mouse speed and 1200 dpi gives reasonable 4 inch torso ;twist range with a mouse. Depending on your windows pointer speed etc you can adjust this value as ;desired to obtain the correct sensitivity you want)
;cl_sensitivity = 0.1



r_TexturesStreaming = 0 ;used to be used to cache textures in graphics card memory rather than fetched from hard drive. May not work anymore.
;=================================================================================
;ObjectDetail

;Sound
;s_FormatSampleRate = 48000
;s_MPEGDecoders = 32
;s_Obstruction = 1
;s_ObstructionAccuracy = 1
;s_ObstructionUpdate = 0.1
;s_ReverbType = 1
;s_SoundMoodsDSP = 1
;s_VariationLimiter = 1
;s_MaxChannels=64
;s_PrecacheData = 1
;s_PriorityThreshold = 1
;=================================================================================
;must be last

Edited by Hammerhai, 29 December 2013 - 11:07 AM.


#7 KulaGGin

    Member

  • Pip
  • 12 posts
  • Google+: Link
  • LocationUkraine

Posted 30 December 2013 - 11:20 AM

View PostHammerhai, on 29 December 2013 - 11:00 AM, said:

From about 13 onwards you should have very quick mouse like movement with smallish joystick deflections.

Say that again please.

View PostHammerhai, on 29 December 2013 - 11:00 AM, said:

And no, it is not different for different mechs. Note that there is a tradeoff between speed and accuracy at smaller deflections, you pretty much cannot have both. A value of 100 should, if it is accepted, be unplayable. Period.


Yeah, but if you will set too big joystick gain you will have deadzones near the edges. And you will get less precision. And if you will set too small joystick gain you will have too slow torso twist. So you have to set correct joystick gain to get maximum(maximum speed of torso twist/presicion).


View PostHammerhai, on 29 December 2013 - 11:00 AM, said:

First thing to check: Is the user.cfg in the Mechwarrior Online main folder?
Is it named correctly? It is easy to save it as user.cfg.txt which will not work. In notepad make sure to choose the save option "all files" rather than text (.txt) and enter user.cfg as the name.

My user.cfg work correctly. When I said there are no difference between cl_joystick_gain 10 and 100 I meaned that maximum speed is equal. gain 100 unplayable because you getting maximum gain when you move your joystick by 6-8%(6-8 gain)

Is there any command list like in cs?
Here is example for cs: go
http://www.gamerconf...obal-offensive/

#8 KulaGGin

    Member

  • Pip
  • 12 posts
  • Google+: Link
  • LocationUkraine

Posted 31 December 2013 - 04:41 AM

Thanks guys. You helped me a lot.

View PostHammerhai, on 29 December 2013 - 03:20 AM, said:


Yep. Very interesting deep topic.

View PostHammerhai, on 29 December 2013 - 03:20 AM, said:

PLEASE read this thread.

http://mwomercs.com/...joystick-users/

Ok. Now I'm using these settings:
cl_fov = 89
cl_joystick_gain = 7
cl_joystick_sensitivity = 2
cl_joystick_throttle_range = 0.07
cl_joystick_invert_throttle = 1
cl_joystick_invert_pitch = 1
cl_joystick_invert_yaw = 0
cl_joystick_invert_turn = 0
i_joystick_deadzone = 0.5
cl_joystick_deadzone = 0.5
i_joystick_buffered = 0

cl_joystick_gain. I noticed that different mechs move(I mean turn around/torso twist) at different speed. For example maximum gain for HGN-7333C© is like ~4. And maximum gain for SDR-5K© is like ~7.

cl_joystick_deadzone. Don't be confused by my joystick deadzones. I use unusual joystick setup(windows and game recognize my joystick as XBOX360 Gamepad). And deadzone works only for analog turn axis. I'd like to use dxtweak, vjoy, ujr, xodec project or other joystick remappers to set deadzones for axes but I can't unbind any axes on my joystick. Even with these settings:
Posted Image

My mech continues to respond to joystick. This is funny but even if I unplug my joystick, start the game, play with mouse a bit and only after that plug in my joy, my mech starts to respond to joystick even in this situation. But I saw somewhere on the forums people saying you should plug in joystick first and only after that launch Mechwarriors(it's true for most games). And of course my mech responds to joystick(XBOX 360 GAMEPAD) when I have like 5 virtual joysticks in control panel and some of this joysticks is set as default one(so my gamepad is not default one).

I've even tried to edit GameData.pak(unbind joy axes in defaultProfile.xml) and I've put defaultProfile.xml in Mechwarriors online/Game/Libs/Config/ . But nothing happened.

So I can't unbind throttle, analog turn, torso twist and pitch. This functions always bind to my joy axes: X,Y,U,Z... And I can't set deadzones for throttle, torso twist and pitch. cl_joystick_deadzone works only for analog turn. That's why I set deadzone to 0.5...

What binds do you use on your joysticks? You can left some functions on keyboard but some functions just needed on joystick.

#9 SpiralFace

    Member

  • PipPipPipPipPipPipPipPip
  • The Devoted
  • The Devoted
  • 1,151 posts
  • LocationAlshain

Posted 31 December 2013 - 05:35 AM

keep in mind, despite the fact that there is support for these things doesn't mean that they are "optimized" for this style of play.

Personal gripe of mine is that turning is still binary. So you can ONLY have it at full speed turn, or completely off. This makes playing lights on joystick setups near unplayable.

I'm hoping that long term they can appease the "simulator" crowd a bit more with advanced controls to help with input, but it doesn't seem like its going to be on the docket for QUITE some time.

#10 Napoleon_Blownapart

    Member

  • PipPipPipPipPipPipPipPip
  • Shredder
  • Shredder
  • 1,173 posts

Posted 31 December 2013 - 11:34 AM

you should mention the type of joystick, some are plug and play where youd have to change cfg files and some might use its own software profiles...

#11 KulaGGin

    Member

  • Pip
  • 12 posts
  • Google+: Link
  • LocationUkraine

Posted 31 December 2013 - 04:28 PM

View PostGorantir, on 31 December 2013 - 11:34 AM, said:

you should mention the type of joystick, some are plug and play where youd have to change cfg files and some might use its own software profiles...

My joy is plug&play. Yeah, If I was using some Logitech Joy, I would try to set deadzones using Logitech Gaming Software...

#12 shotokan5

    Member

  • PipPipPipPipPipPipPip
  • Legendary Founder
  • Legendary Founder
  • 550 posts
  • Google+: Link
  • Locationvirginia

Posted 01 January 2014 - 08:26 AM

So many have done a lot of work on the joystick problem and should be commended.

The sad fact is that from the beginning of this game joysticks were supposed to work.
Someone at PGI found out that the software that was supposed to do it was not their.

Their answer was to make it a low priority project to put in the coding that would make
it work as in the other MechWarrior games. After over a year, they have not bothered
to do this. A few days after a year of trying everything and being told that it is not important
as a new mech you pay for, enough is enough. When enough people with joystick's complain
that it is not right, then perhaps they will do as promised and write and put in the which will make
it work.

Until that point comes I will no longer be playing this game. Their is no true fix for the joystick
as of yet. Not till enough people demand it now. Not when selling you merchandise is more
important. I is not surprising how many flaws have been fixed when enough people standup
and complained. From my days as a founder I have heard the same tune in every problem report.
I say to PGI fix it now or goodbye.

#13 Hammerhai

    Member

  • PipPipPipPipPipPipPipPip
  • Bad Company
  • Bad Company
  • 1,001 posts

Posted 02 January 2014 - 04:24 AM

Assuming you use ujr the answer is quite easy: Double click one of the analog axes you want to reassign under "OPTIONS" IN THE CLIENT, click the box called manual control in the UJR main window and operate the axis in the state column to have MWO pick it up instead of the joystick. Should be self explantory for UJR. Once assigned MWO indeed follows the joystick it "knows" in preference to any others. Note that assigning a joystick anywhere else other than the analog axes in the lower right hand corner leads to strange behaviour and does not work.

What you are seeing in game is that an assault mech such as the Highlander will not turn as quickly as a Jenner or Spider. This is behaving as intended. If you go to smurfy at http://mwo.smurfy-net.de/mechlab and look under mech and weapon stats you will notice different mechs behave very differently, esp in torso twist and turning. It also depends on the size of the engine fitted to the mech, smaller engines = slower movement all round, not just speed.

Translating my comment about gain of 13 to about 15 for you: Simple: Do not go higher than that.

I used to run my Dragon with a gain of 13 and a sensitivity of 1.4. The effect of the calculations that MWO does mean that it is the ratio between gain and sensitivity that gives you a controllable sweet spot, rather than any old random numbers. Call it the "gearing" between gain and sensitivity. So it seems to me that if you have control at 2/7 then the results would feel the same at 4/14. I never tested this thoroughly though. IMHO and with a grain of salt and all that.

And yes, the effect of gain is to lose resolution towards the edges of the joystick response curve, since it would be calculated on a cubed function, or at least a squared value. So don't go too high.

Those of you puzzled: Imagine that the "Steps" a joystick takes get too large because of the maths involved, leaving "Gaps" which are noticeable and lead to lack of smooth control.

Edited by Hammerhai, 02 January 2014 - 08:23 AM.


#14 Hammerhai

    Member

  • PipPipPipPipPipPipPipPip
  • Bad Company
  • Bad Company
  • 1,001 posts

Posted 02 January 2014 - 04:34 AM

And no, there is no documentation apart from what you have already. PGI never bothered with that

#15 Hammerhai

    Member

  • PipPipPipPipPipPipPipPip
  • Bad Company
  • Bad Company
  • 1,001 posts

Posted 03 January 2014 - 03:28 AM

Note that UJR now uses the "Quickbind" function which semi automates the process of binding an axis. Download the latest version and try it out.





1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users