Borderlands Forum

This is a community forum and not official technical support. — If you need official support: Contact Us

The following comments are owned by whoever posted them. We are not responsible for them in any way.

Back to Threads Reply to Thread

Mouse Control Issues

Have any of you found a better work around for http://bugs.winehq.org/show_bug.cgi?id=6971 ?

I've tried the MouseWarpOverride registry setting which fixes the control of the character - you can spin as much as you want. But it makes controlling the menus impossible. What are you guys using?

I suppose this is probably only an issue in the linux version of crossover. If you suffer from it your mouse control will do one of two things. By default you'll run into "invisible" walls where you can't turn any farther in a particular direction. This is because of the way that Borderlands (UT3) reads the mouse. What happens is that the mouse gets to the edge of screen, and Borderlands doesn't read any more movement - it is literally an invisible wall that your mouse hits. This makes fighting in the game incredibly hard.

This is the bug that is causing the issue:
http://bugs.winehq.org/show_bug.cgi?id=6971

There is no real fix on that thread - the real fix is something that doesn't change dinput - but rather fixes the x11 drivers. About half way down the page is the first work around: http://bugs.winehq.org/show_bug.cgi?id=6971#c142 You can set a registry key to "warp" the mouse. The problem with this fix is it doesn't allow you to use your mouse to control the menus in Borderlands (Which is very important to playing the game). So the fighting works, but the menus don't.

One of the most recent commenters added a new workaround patch - http://bugs.winehq.org/show_bug.cgi?id=6971#c269 - I should note that this is still not the real fix. However, it's a great workaround for Borderlands. I applied his patch to a git checkout of wine (from last night), and then built wine. I made a backup copy of the dinput.dll.so that crossover comes with and then copied the new dinput.dll.so that I built in to test it out. I also had to update the registry key and instead of a value of "force" I used "force-box" which enables this work around. It allows you full control during the fighting and allows you to use the menus as well.

It does nothing for the performance issues.

I'm being vague about how I applied all of this - because if you don't know how to do it, then you probably shouldn't be doing it. This is a hack that helps play an unsupported game. It's a particularly nice hack as it doesn't change the way dinput works unless you turn on a specific registry key - which can be done on an app specific basis. I go even one step further and have a separate bottle that borderlands is installed in. I've opened a ticket regarding the issue - http://www.codeweavers.com/support/tickets/browse/?ticket_id=772218 - so the crossover staff knows about it.

I should note a few things.

  1. this is a linux specific issue.
  2. The built-in override for these issues is setting "MouseWarpOverride"="force" in the appropriate registry location, but this doesn't work for Borderlands. It works for most FPS games because the only real controls that require a mouse are the in-game-fighting controls. Borderlands requires extensive use of menus throughout the game. Some can be navigated via the keyboard - but not all of them can. So this hack fixes the fighting controls, but disables many menus. My description above fixes both.

It isn't a linux specific issue actually. I get the same thing. I've just.... adjusted my fighting on how I spin, and if I hit the 'wall' I'll open up the menu and move the mouse to the middle of the screen, and close the menu.

However, it's still annoying. But no, its not specific to linux.

Good to know!

That might raise the priority of getting this work-around in.

Douglas St. Clair wrote:

It isn't a linux specific issue actually. I get the same thing. I've
just.... adjusted my fighting on how I spin, and if I hit the 'wall'
I'll open up the menu and move the mouse to the middle of the
screen, and close the menu.

However, it's still annoying. But no, its not specific to linux.

Have you tried setting the "MouseWrapOverride"="force" to fix the fighting? It works pretty well. I wish there was a way to update the key bindings to allow for full control of the menus from the keyboard. Maybe we should look into that?

Douglas St. Clair wrote:

It isn't a linux specific issue actually. I get the same thing. I've
just.... adjusted my fighting on how I spin, and if I hit the 'wall'
I'll open up the menu and move the mouse to the middle of the
screen, and close the menu.

At least on my system, I noticed that how far you turn is dependent on the speed you move the mouse. So if I hit the edge, a quick spin around will still leave me with some room on the other side. This is with mouse smoothing off.

I use the mouse warp registry hack and and that allows me to spin as much as you want, to quote another poster. But when you mention not being able to keybind the menus, that is untrue. You can't make custom keybinds but the default ones work great. I'm used to using keybindings for menus from other rpgs so I just pushed buttons until menus came up lol.

Character stats: P
Talent trees: K
Map: M
Inventory: I
Quests: L. Spacebar in that menu to cycle between achievements, quests and the other thing.
Online/friends menu: O
Buying/selling/buying back at vendors- left: <, right: >
Scrolling through quest text: Ctrl-up/down arrow key

That's also dependent on what your mouse sensitivity is set to. Higher sensitivity allows you to move more before hitting the "wall."

Anthony Meruelo wrote:

That's also dependent on what your mouse sensitivity is set to.
Higher sensitivity allows you to move more before hitting the
"wall."

A higher in-game sensitivity setting does that. Some people have tried turning up the OS mouse tracking speed, or even the hardware sensitivity on their mouse (for those which support that feature). That has the exact opposite effect.

1 to 10 of 10

CrossOver Forums: the place to discuss running Windows applications on Mac and Linux

CodeWeavers or its third-party tools process personal data (e.g. browsing data or IP addresses) and use cookies or other identifiers, which are necessary for its functioning and required to achieve the purposes illustrated in our Privacy Policy. You accept the use of cookies or other identifiers by clicking the Acknowledge button.
Please Wait...
eyJjb3VudHJ5IjoiVVMiLCJsYW5nIjoiZW4iLCJjYXJ0IjowLCJ0enMiOi02LCJjZG4iOiJodHRwczpcL1wvbWVkaWEuY29kZXdlYXZlcnMuY29tXC9wdWJcL2Nyb3Nzb3Zlclwvd2Vic2l0ZSIsImNkbnRzIjoxNzMxNDM1MjAzLCJjc3JmX3Rva2VuIjoibTR3Q1VKcUpYUFZ5aGJabSIsImdkcHIiOjB9