Jump to content

- - - - -

Freelook Doesn't Work


31 replies to this topic

#21 Spheroid

    Member

  • PipPipPipPipPipPipPipPipPipPip
  • Veteran Founder
  • Veteran Founder
  • 5,060 posts
  • LocationSouthern Wisconsin

Posted 24 February 2018 - 01:42 PM

The default keymap of MWO always causes problems in either freelook or arm lock situations.

My recommendation is you set armlock as a toggle bound to the left shift key and free look bound to the left ctrl key with arm lock checkbox set to off. Once you can confirm that the setup functions you can alter the keys as you see fit.

I guarantee you it is a simple configuration problem not a true bug.

Edited by Spheroid, 24 February 2018 - 01:44 PM.


#22 Punished Venom Prawn

    Member

  • Pip
  • The Hungry
  • The Hungry
  • 18 posts

Posted 24 February 2018 - 04:39 PM

Quick update: Standalone client didn't fix anything.

View PostSpheroid, on 24 February 2018 - 01:42 PM, said:

The default keymap of MWO always causes problems in either freelook or arm lock situations.

My recommendation is you set armlock as a toggle bound to the left shift key and free look bound to the left ctrl key with arm lock checkbox set to off. Once you can confirm that the setup functions you can alter the keys as you see fit.

I guarantee you it is a simple configuration problem not a true bug.


I've been using this exact setup, except armlock toggle on left alt instead of shift. Next time I'm in game I'll try binding to shift but unless there's some really weird keyboard stuff going on I don't think it'll change anything.

Edited by Lazy Prawn, 24 February 2018 - 04:49 PM.


#23 Koniving

    Welcoming Committee

  • PipPipPipPipPipPipPipPipPipPipPipPipPip
  • The Guide
  • The Guide
  • 23,384 posts

Posted 24 February 2018 - 04:57 PM

That won't. Did support get in touch with you? They probably won't be able to until Monday. Also did you try the hardware thread? I know it isn't as well seen as it used to be, but the people that linger there know their stuff.

#24 Punished Venom Prawn

    Member

  • Pip
  • The Hungry
  • The Hungry
  • 18 posts

Posted 24 February 2018 - 05:29 PM

Still waiting on support, heading to hardware now. Latest info: Tried uninstalling controller drivers, didn't fix it.

So I reinstalled my controller and tried to use freelook with the stick, and it acts the same way as the mouse.

#25 Punished Venom Prawn

    Member

  • Pip
  • The Hungry
  • The Hungry
  • 18 posts

Posted 02 March 2018 - 02:48 AM

Final Update: I give up. Hardware forum didn't seem to have any ideas, support did its best but whatever the problem is it must be something in my relic of a computer. I just don't have the time to keep troubleshooting it. Thanks for the help guys.

If I ever accidentally stumble into what caused it I'll be sure to track you down, Koniving.

#26 Koniving

    Welcoming Committee

  • PipPipPipPipPipPipPipPipPipPipPipPipPip
  • The Guide
  • The Guide
  • 23,384 posts

Posted 02 March 2018 - 07:29 AM

Sorry to hear it. In recreating it (which is too convoluted to practically use it and requires too many hands or in my case some hands and feet on multiple peripherals), some of what you tried should have fixed it. So I haven't got any idea. It really is a shame.

On a side note, I'm certain the problem is specific to your computer so if you stumble upon another computer you'll be cured of this affliction.

Still jealous though, would love an easy to toggle method of doing this, but as of right now the only practical way is through Track IR/ VR headset and even then, having my head tilted off from perfectly center means my crosshair would be completely useless (the problem that track IR users point out is if you tilt your head or position it off center, you're not shooting at the crosshair as you see it.. because the crosshair is a flat object in 3D space intended to only be seen from a single position.

#27 Dragonporn

    Member

  • PipPipPipPipPipPipPip
  • Ace Of Spades
  • 657 posts

Posted 02 March 2018 - 12:06 PM

Several times I had problems with some keys not functioning properly whenever I rebound them. Game restart or setting keybind to default and rebinding again solved all these issues every time.

I don't have any VR software, my Arm-lock is bound to L-Alt, Freelook to L-Ctrl, L-Shift to MASC, all keys set to hold and nothing to toggle.

Strange issue you got there OP, hope you'll find a solution.

#28 Smaa

    Rookie

  • Veteran Founder
  • Veteran Founder
  • 2 posts

Posted 11 February 2019 - 04:07 PM

Hi guys,

Well it’s a year later and I’m trying to figure out the same issue. The free arm movement was always an enigma to me, nevertheless something which I can see huge tactical advantage in mastering, especially in brawls and poking. The thing that has had me stumped from the beginning is that the square targeting reticule for the arms is not fixed to the centre of the screen. Considering that mechs use head tracking tech the same as attack helicopters do, you would think that the torso movement would ‘follow’ the arm movement, which follows the head movement. The sensitivity and movement speed and hence reaction times are many times better using the arms than the torso which makes sense as the torso has more inertia to overcome. In light of this, it would make more sense for the devs to map free look to ‘joystick 0’ x/y input, and the torso to ‘joystick 1’ x/y input; joystick 1 being the main

My original

#29 Koniving

    Welcoming Committee

  • PipPipPipPipPipPipPipPipPipPipPipPipPip
  • The Guide
  • The Guide
  • 23,384 posts

Posted 11 February 2019 - 04:28 PM

View PostSmaa, on 11 February 2019 - 04:07 PM, said:

Hi guys,

Well it’s a year later and I’m trying to figure out the same issue. The free arm movement was always an enigma to me, nevertheless something which I can see huge tactical advantage in mastering, especially in brawls and poking. The thing that has had me stumped from the beginning is that the square targeting reticule for the arms is not fixed to the centre of the screen. Considering that mechs use head tracking tech the same as attack helicopters do, you would think that the torso movement would ‘follow’ the arm movement, which follows the head movement. The sensitivity and movement speed and hence reaction times are many times better using the arms than the torso which makes sense as the torso has more inertia to overcome. In light of this, it would make more sense for the devs to map free look to ‘joystick 0’ x/y input, and the torso to ‘joystick 1’ x/y input; joystick 1 being the main

My original


The circle is fixed to the center of the screen, though with minor exceptions on when the body is swingjg to catch up (you can imagine turning in a car, your body is being pulled in the other direction).
So long as the torso can still move if free look is not pressed it will remain centered. If free look is pressed and arms are not locked it also remains centered.

The behavior you experienced as Venom is abnormal and I believe you may have just shared the culprit.
You have a joystick configuration, with or without headtracking. If it is with headtracking installed you will get the unusual behavior you experience. Free look is just a button toggle for the native mouse. Press it and you can turn your pilot's head using the same control as aiming. If however you remapped it to headtracking... it won't work for the mouse. If you changed the default control chances are it could be the reason for the unusual behavior. The joystick support here is terribly bad and the support for head track / VR is even worse as it isn't unusual for players to be unable to undo certain changes after trying to get it to run with those two.

If not using the headset I suggest mapping Free look's look around and the torso arm aiming to the same pair of axis. While you won't e able to do them separately, they should at least finally work for you. Thinks assuming you still have te same issue.

As for the proporition.... the problem with that is if you were in said helicopter and the helicopter followed the head movement.... you'd defeat the point of being able to aim by head movement as the entire helicopter would turn with your head. The circle or square as you put it for the arms will lead faster than the body as you described because the arms don't have to move upwards of most of the mech's weight. If you lock the arms though, for some reason, torso movement actually becomes even slower..

Nobody would love to have the head and arms under separate controls more than me. I'd love tobe able to separate the arms even and control the two arms and the body as 3 entities...and still be able to look in a fourth direction while doing it. But... trying to separate them breaks the controls in a bad way.


Edited by Koniving, 11 February 2019 - 04:39 PM.


#30 Smaa

    Rookie

  • Veteran Founder
  • Veteran Founder
  • 2 posts

Posted 11 February 2019 - 05:03 PM

Sorry, I had to post without finishing and turn my phone off as I was going into an ultrasound/x-ray theatre. I’ll continue my post here:

Joystick 1 being the main joystick, used for torso movement, and joystick 0 being the thumb toggle on top which would be used for freelook.

View PostKoniving, on 11 February 2019 - 04:28 PM, said:

“The circle is fixed to the center of the screen, though with minor exceptions on when the body is swingjg to catch up”


The exact problem is that the circle does NOT stay in the centre of the screen while the arms are moving (at least for me). I need the circle to stay in the middle, not the cockpit. As it stands, when I move my mouse or joystick to the right, the circle moves to the right of the screen and the view is locked forward in the cockpit, which then follows the mouse and arms travel direction to eventually make the circle in the centre again. What should happen with arm lock disabled is that the circle stays in the centre as I move my mouse to the right, and the cockpit view trails behind from the left of the screen so that my torso mounts and cockpit eventually return to the centre of the screen, once my circular targeting reticule has stopped moving.

Hope this clears things up, if you have a way to rectify this apparent error it will be much appreciated!

Edited by Smaa, 11 February 2019 - 05:06 PM.


#31 Tarl Cabot

    Member

  • PipPipPipPipPipPipPipPipPipPip
  • Tai-sho
  • Tai-sho
  • 7,654 posts
  • LocationImperial City, Luthien - Draconis Combine

Posted 11 February 2019 - 06:04 PM

There are three different looks/crosshairs

Torso - for torso mounted weapons Uses the actual crosshairs

Arm mounted weapons. Uses the circle portion of the crosshair setup. Arm locked on/engaged, arms sticks with torso movement.


Freelook (arm locked engaged/on) - the eyes of the pilot viewing the interior of the cockpit without any concern of where the cross hairs are located when arm lock is engaged.

Freelook (arm lock disengaged/off) arm mounted weapons will follow it until arms have reached its max limit. Torso will NOT follow once arms have reach their limit.

Arm mounted weapons + Arm lock engaged - movement is restricted to torso movement only. Torso is not affected by Freelook, nor will Torso movement affect mech movement/direction, ie legs will not turn when torso has reached its max limit.

With that I will simply bow out as this game is terrible with joystick controls, workable but not near what it needs to be.

Edited by Tarl Cabot, 11 February 2019 - 06:07 PM.


#32 Szebike

    Rookie

  • Heishi
  • 2 posts

Posted 28 February 2019 - 10:31 PM

Hi, for me do the same...i don't know what happend the game.
i reinstall it delete it still the same. Only my mech hand move when i hold the key down.





1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users