Xbox controller conflict

[Shadow]

I've been away from this sim for a while and just now bought the DLCs and started playing again.
I noticed when I look around using the Xbox controller I need to hold down the left stick and move the right stick. But when I do that while I'm in an excavator I'm also operating the vehicle. It appears holding down the left stick doesnt matter for the excavator controls. So when I want to look up I'm also raising the first boom (rightstickdown).
I dont remember having this issue when the game was new.
Of the top of my head the thing that has changed on my pc since the release of this games is that I've upgraded from Win7pro to Win10pro x64.
Any ideas?

[Shadow]

Can a develeoper please verify this bug?

-Hold the left stick down (in) while in a forklift.
-Move the right stick up or down.
-Observe that the fork is raising and lowering while your view camera pan up and down.

Desired result: When left stick is held in (view modifier), then right stick should only pan the view camera and not pass input to other functions.

I dont remember if I had this issue with when I used Win7 but I have reproduced this on two machines running Windows 10 and Xbox360 controller for PC.

[Chacal]

You can reassign the view modifier to a different button or axis in the key assignments menu.

[Shadow]

I was looking for that. Do you know what its called?

[Chacal]

I'm at work now, but from memory you open the menu (Escape key), click on Options, then Key Assignments. Scroll down until you find View Modifier, it should have Left Shift in the primary key. You should be able to change that by clicking on it and choosing a different key. Or better, assign another key or controller axis as secondary.

[Shadow]

The view modifier binding is not listed in the key bindings page. However I can manually edit the XML and bind it to a different key or button, but this does not change the issue that when I move the right stick it still works as the primary function assigned to the current vehicle I'm in.
Can one of the devs please acknowledge this bug?

[dumB0]

Thanks for your reports. I just tested it and I can verify this issue. I'll see what I can do to fix this!

[dumB0]

I think I found the problem. The fix should be shipped with the next update.
Thanks

[Shadow]

Thanks for the reply and solution, Kipaboy.
Looking forward to it :)

[Shadow]

I can verify that it is now fixed in 1.3.1. Thanks :)