Jump to content

Xojira

PC Member
  • Posts

    131
  • Joined

  • Last visited

Posts posted by Xojira

  1. On 2020-09-25 at 1:37 PM, -FrutyX- said:

    Yea, I mean .... nobody can expect to play "modern" games with only DX10, so I don't think that's a big deal.

    I am very excited when devs say "Optimizations", there are many devs that completely don't care about optimizations in their games, all they care about are skins, batlepass stuff and any other ways how to make money, meanwhile their games are running terribly, yet they still make money, sad.

    Optimizations always first !

    GIRHUu9.jpg

    You haven't played warframe in a long time have you.

    • Like 5
  2. @[DE]Jengerer
    I did reboot and launched Warframe without starting Steam. Same results.
    I should have stated this stated earlier(It slipped my mind) I didn't do a standalone install. I am using the steam installation without using steam(creating a shortcut the Warframe launcher itself). If doing standalone download might work, then I will give that a try.

    https://imgur.com/YcH92cF

     

     

  3. 8 minutes ago, SpikeBlack said:

    Have to admit since the Deadlock Protocol update my controller has been weird, the sensitivity was 10x what it should be. The look default of 50 was previously fine but I had to put it down to 5 just so that the screen didn't go into a wild spin whenever I touched the right stick. I recalibrated the controller in windows and steam just to confirm it was working and tried other games where it's functioning normally.

    Other problems I had are:

    • The X and B buttons didn't function in the Corpus Crystal but did in all other menus and in game, had to resort to the mouse.
    • The mini map wouldn't open with the standard mapping i.e. the black button to the bottom left of the xbox symbol.
    • I could revive using the X button had to resort to pressing X on the keyboard.

    Deleting all the config files fixed it for me so thanks for that tip, saved me a support case. It's almost as if the steam controller config was set as the default overriding the existing settings as when using the "Steam / warframe / manage / configure controller" the button to display the in game map was unmapped in all options. I haven't changed the controller config since I started playing over a year ago.

    The only other thing that I can think of is that the code reading the config file has changed resulting in the problem - i.e. it doesn't read all the way through and quits leaving the config messed up. Or new settings have been added which caused it to default.

    As I said prior to the deadlock update last week my controller was fine. 

    My controller is the original xbox one for pc version.

    That sensitivity issue is same thing I experience in steam, but for standalone the sensitivity is normal.
    Yeah controller support was perfect before Deadlock went live.

  4. I run standalone,and have been since the melee update 2.999 as it made some nasty changes to controller support. I stopped using warframe from Steam as camera is VERY sensitive and any changes I make to the controller bindings is ignored.

    Whether Standalone, Steam, Or Steam big picture the results are the same.

  5. It's Xbox 360 controller, I am in the process of submitting that ticket. Ticket has been submitted.
    Well more accurately it's a PS2 Controller via USB, I am using a program that makes windows, steam, and warframe see it as a 360 controller.

    I just tried with Xbox One controller via Bluetooth, same result.

×
×
  • Create New...