Jump to content
Abyss of Dagath: Share Bug Reports and Feedback Here! ×

Controller Sensitivity Issues


paul5473
 Share

Recommended Posts

Hi Guys,

Yesterday i had a weird issue where all the sudden when booting up warframe via steam for the first time in about 3 years it started booting up in a new weird looked like big picture mode. Now everytime i use my controller the sensitivity is so fast up and down i can't play the game anymore, i haven't changed my settings for my controller but have today tried to turn it down as looking up and down is so fast now even with the scroll bar on 0. I want to know if anyone who uses a controller on pc is also having these kinds of issues?

*UPDATE* If you are having this problem you are probably in the steam beta system, opt out and it should fix your problem as i fixed mine.

Edited by paul5473
Link to comment
Share on other sites

I had the same issues when I logged onto today. I updated Steam before logging on, and I'm positive it auto-changed our settings to give us Big Picture mode by default, which is pretty bs if you ask me. I'm not sure how to fix the sensitivity issue, but I disabled big picture mode by going into Steam settings>In-game>Uncheck "Use Big Picture Overlay..." and Settings>Controller>General Controller Settings>Uncheck all the boxes. That at least gets rid of all the big picture mode stuff and the janky controller UI along with it. If anyone could let us know how to fix the sensitivity issue, that would be great. It's literally impossible for me to aim right now.

Link to comment
Share on other sites

1 minute ago, DatDarkOne said:

I use the stand-alone client and haven't loaded the game yet today.  So not sure just yet if it's a Steam issue or all clients one.  I'll respond back after I load into the game today to see.  

Thanks keep us posted.

Link to comment
Share on other sites

I opted out of the Steam beta and that rolled back the May 3rd update which had lots of Steam controller fixes. Many people were giving feedback that it broke ALL non-steam game controller support and defaults

All went back to normal. No problem with defaults.

And on a side note, Big Picture was already off.

 

Almost 3K hours on 2nd XBOX 360 controller (mostly) for WF.

Edited by BoingerMaster
More info
Link to comment
Share on other sites

6 minutes ago, BoingerMaster said:

I opted out of the Steam beta and that rolled back the May 3rd update which had lots of Steam controller fixes. Many people were giving feedback that it broke ALL non-steam game controller support and defaults

All went back to normal. No problem with defaults.

And on a side note, Big Picture was already off.

 

Almost 3K hours on 2nd XBOX 360 controller (mostly) for WF.

Yep opted out of the beta on steam and it fixed my problem

Link to comment
Share on other sites

Can also now confirm opting out of Steam beta updates fixes issues. Steam nearly made WF unbearable, glad to know it wasn't actually a WF issue but a Steam issue. Okay so taking myself out of the steam beta client worked for a day (barely) now my controller issues are back. I log into the game, turn the controller on then immediately my frame starts walking about the orbiter without me pressing any keys or directional pad. If I turn on the controller before logging into the game it's even worse, I get motion sick because my frame stars spinning in circles. I hate feeling like I'm being forced to not use a controller to play the game properly. I've tried the preloaded configurations for the Xbox360 controller for pc and they simply don't work for me, half of the buttons don't do anything. Sure they have a "DE" recommended setup for "steam controller" but that doesn't work for the controller I have. I wish there was a "DE recommended setup" for all available controllers on pc.

Edited by Mortheous
Wonky controls are back
Link to comment
Share on other sites

  • 3 months later...

For anyone still having this problem I first want to state that what is happening is that the steam 'Big Picture' mode is trying to take the mouse/keyboard settings and map them to the controller which causes the joysticks to use the in game mouse sensitivity and not the in-game controller settings. It does this to give controller support to other games that don't have any. So to fix this issue this is what I had to do:

Step One:
disable the Big Picture Overlay mode from being used while having a controller plugged in, to do this go to:
Settings>In-Game> Steam overlay> un-check "Use the Big Picture overlay when using a steam input enabled controller from desktop"

Step two make sure controller support is turned off by going to:
settings>controller> click general controller settings>look to see if controller you have is checked and if so turn it off.

Doing these two steps help restored Warfames controller support and by doing so the controller sensitivity settings were being used once again and not the mouses sensitivity settings. I hope this helps anyone who may still be dealing with this issue.

Link to comment
Share on other sites

  • 1 month later...
On 2018-08-10 at 11:53 AM, YamiKilmore said:

For anyone still having this problem I first want to state that what is happening is that the steam 'Big Picture' mode is trying to take the mouse/keyboard settings and map them to the controller which causes the joysticks to use the in game mouse sensitivity and not the in-game controller settings. It does this to give controller support to other games that don't have any. So to fix this issue this is what I had to do:

Step One:
disable the Big Picture Overlay mode from being used while having a controller plugged in, to do this go to:
Settings>In-Game> Steam overlay> un-check "Use the Big Picture overlay when using a steam input enabled controller from desktop"

Step two make sure controller support is turned off by going to:
settings>controller> click general controller settings>look to see if controller you have is checked and if so turn it off.

Doing these two steps help restored Warfames controller support and by doing so the controller sensitivity settings were being used once again and not the mouses sensitivity settings. I hope this helps anyone who may still be dealing with this issue.

 This was awesome, I’ve been struggling with this for weeks! I’m so thankful find your post thank, you so much!!! 

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
 Share

×
×
  • Create New...