Mouse still not working properly on OS X with 1.4

clocknova · Post by **clocknova** » Thu Mar 08, 2012 9:56 am

This has been an ongoing issue with all of the 1.4 releases. In several games, notably Oblivion, Fallout 3, Fallout:NV, and Far Cry, the mouse will not function properly. On main menus, the mouse will be stuck in one quadrant of the screen, as if what the mouse thinks the screen boundaries are is not aligned with the actual boundaries.

In game, the mouse swings wildly all over the screen, making actual gameplay impossible.

I'm running this with the latest Wineskin, Mac OS 10.7.

jjmckenzie · Post by **jjmckenzie** » Thu Mar 08, 2012 10:04 am

On Thu, Mar 8, 2012 at 7:56 AM, clocknova <[email protected]> wrote:

This has been an ongoing issue with all of the 1.4 releases. In several games, notably Oblivion, Fallout 3,
Fallout:NV, and Far Cry, the mouse will not function properly. On main menus, the mouse will be stuck in one
quadrant of the screen, as if what the mouse thinks the screen boundaries are is not aligned with the actual
boundaries.

In game, the mouse swings wildly all over the screen, making actual gameplay impossible.

I'm running this with the latest Wineskin, Mac OS 10.7.

One. Try this with 'plain vanilla' Wine. Even though doh123,
Wineskin's producer states he does not make changes, it is the
project's policy not to suppor third party software.

Two. Please try installing Wine with either MacPorts or Fink. If this
problem still occurs, then please capture a logging file using the
process in the Wine FAQ, located at
http://wiki.winehq.org/FAQ#run_from_terminal and
http://wiki.winehq.org/FAQ#get_log

Thank you.

James

paulthetall · Post by **paulthetall** » Thu Mar 08, 2012 10:08 am

I am with i am preaching this for a longer time. It heavily gets worse from 1.4 rc4. in 1.4 RC3 in most of the games it still worked fine. it is on Mac Osx version Snowleopard and Lion and probably also in Leopard. I made a bugreport for testdrive unlimited as an example here: http://bugs.winehq.org/show_bug.cgi?id=29932

Please help. Linux users probably don't experience this. So please help the Mac users enjoying their games in wine

doh123 · Post by **doh123** » Thu Mar 08, 2012 11:50 am

This isn't specifically a Wine bug I don't think.

I can reproduce it with normal Wine and XQuartz, and it only happens after Xinput2 changes for mouse control in Wine, but I think the problem may be in XQuartz and not in Wine... its easy to work around the bug in XQuartz, you just launch XQuartz and make sure its fully working, then start Wine.. don't start Wine and have it launch XQuartz directly. WineskinX11 is made off XQuartz, and it starts fresh every time for the wrapper in Wineskin so the bug is seen on every launch. Basically the bug is that the X mouse cursor and the Mac OS X cursor are not lined up on the screen, they are in slightly different spots.

qparis · Post by **qparis** » Thu Mar 08, 2012 12:11 pm

I have the same problem. It appeared exactly since wine 1.3.17

Consequently, it's the only problem remaining for OSX users to play for example skyrim. Other games like Fallout 3 and Wacraft III are also affected.

If someone has any idea to fix this problem, I would be very interested

Post by **dimesio** » Thu Mar 08, 2012 12:23 pm

qparis wrote: If someone has any idea to fix this problem, I would be very interested

Someone running the regression test that was requested in http://bugs.winehq.org/show_bug.cgi?id=29932 would be a start.

clocknova · Post by **clocknova** » Thu Mar 08, 2012 12:25 pm

Well, I'm glad you guys know the problem exists. Hopefully we can at least find a workaround soon. Thanks.

qparis · Post by **qparis** » Thu Mar 08, 2012 12:38 pm

@ dimesio, I'll try to do the regresion testing.

clocknova · Post by **clocknova** » Thu Mar 08, 2012 3:05 pm

doh123 wrote:This isn't specifically a Wine bug I don't think.

I can reproduce it with normal Wine and XQuartz, and it only happens after Xinput2 changes for mouse control in Wine, but I think the problem may be in XQuartz and not in Wine... its easy to work around the bug in XQuartz, you just launch XQuartz and make sure its fully working, then start Wine.

Is there any way to work around the problem while using Wineskin? Starting XQuartz first does nothing for Wineskin.

paulthetall · Post by **paulthetall** » Thu Mar 08, 2012 3:30 pm

doh123 wrote:This isn't specifically a Wine bug I don't think.

I can reproduce it with normal Wine and XQuartz, and it only happens after Xinput2 changes for mouse control in Wine, but I think the problem may be in XQuartz and not in Wine... its easy to work around the bug in XQuartz, you just launch XQuartz and make sure its fully working, then start Wine.. don't start Wine and have it launch XQuartz directly. WineskinX11 is made off XQuartz, and it starts fresh every time for the wrapper in Wineskin so the bug is seen on every launch. Basically the bug is that the X mouse cursor and the Mac OS X cursor are not lined up on the screen, they are in slightly different spots.

Thats not entirly true, I tested it also in Crossover 11 which has 1.4 and has the same mousebug in testdrive. It is also in other games. Besides that Issue does not appear in 1.4 RC3 but only above that version (RC4/5/6)

qparis · Post by **qparis** » Thu Mar 08, 2012 3:33 pm

I do not have the games here to run the regresion test. I will do it this week-end for Fallout 3

clocknova · Post by **clocknova** » Thu Mar 08, 2012 3:36 pm

paulthetall wrote:Thats not entirly true, I tested it also in Crossover 11 which has 1.4 and has the same mousebug in testdrive. It is also in other games. Besides that Issue does not appear in 1.4 RC3 but only above that version (RC4/5/6)

I get this issue in all 1.4 release candidates. In fact, for the last several releases of 1.3, with Oblivion I get no mouse cursor at all. I think 1.3.18 was the last version I could use.

qparis · Post by **qparis** » Thu Mar 08, 2012 3:55 pm

clocknova wrote:
paulthetall wrote:Thats not entirly true, I tested it also in Crossover 11 which has 1.4 and has the same mousebug in testdrive. It is also in other games. Besides that Issue does not appear in 1.4 RC3 but only above that version (RC4/5/6)
I get this issue in all 1.4 release candidates. In fact, for the last several releases of 1.3, with Oblivion I get no mouse cursor at all. I think 1.3.18 was the last version I could use.

Wasn't it 1.3.16 ?

clocknova · Post by **clocknova** » Thu Mar 08, 2012 4:02 pm

qparis wrote:Wasn't it 1.3.16 ?

Just tried it. 1.3.18 seems to work normally with my Oblivion wrapper. No cursor at all in 1.3.19.

paulthetall · Post by **paulthetall** » Thu Mar 08, 2012 4:16 pm

clocknova wrote:
qparis wrote:Wasn't it 1.3.16 ?
Just tried it. 1.3.18 seems to work normally with my Oblivion wrapper. No cursor at all in 1.3.19.

correct but after 1.3.24 things got fixed again, but after that 1.3.26 sound was rubisch.

Hartmut Figge · Post by **Hartmut Figge** » Thu Mar 08, 2012 4:29 pm

paulthetall:

clocknova wrote:

Just tried it. 1.3.18 seems to work normally with my Oblivion
wrapper. No cursor at all in 1.3.19.
correct but after 1.3.24 things got fixed again, but after that
1.3.26 sound was rubisch.

Mhm. I just tried Oblivion with some old savegames. No problems with
either cursor or sound.

hafi@i5_64 ~ $ wine --version
wine-1.4-rc6

Hartmut
--
Usenet-ABC-Wiki http://www.usenet-abc.de/wiki/
Von Usern fuer User

clocknova · Post by **clocknova** » Thu Mar 08, 2012 4:29 pm

paulthetall wrote:correct but after 1.3.24 things got fixed again, but after that 1.3.26 sound was rubisch.

No mouse cursor in Oblivion wrapper with 1.3.25 or 1.3.37

Post by **dimesio** » Thu Mar 08, 2012 7:20 pm

paulthetall wrote: Thats not entirly true, I tested it also in Crossover 11 which has 1.4 and has the same mousebug in testdrive.

Report it to Codeweavers.

paulthetall · Post by **paulthetall** » Fri Mar 09, 2012 8:35 am

dimesio wrote:
paulthetall wrote: Thats not entirly true, I tested it also in Crossover 11 which has 1.4 and has the same mousebug in testdrive.
Report it to Codeweavers.

Already done that. I catched in the conversation with them that on the Mac mousinput does not go back to xinput when it sees that xinput2 is not supported.

doh123 · Post by **doh123** » Fri Mar 09, 2012 9:19 am

paulthetall wrote:
dimesio wrote:
paulthetall wrote: Thats not entirly true, I tested it also in Crossover 11 which has 1.4 and has the same mousebug in testdrive.
Report it to Codeweavers.
Already done that. I catched in the conversation with them that on the Mac mousinput does not go back to xinput when it sees that xinput2 is not supported.

that could be part of the problem. While XQuartz does have Xinput2 support, its not fully supported because there are certain functions that the information just isn't available to it... so in some cases it would need to fall back to Xinput

cluthz · Post by **cluthz** » Sat Mar 10, 2012 1:30 pm

I do believe it's the same issue that limits 360 degs movement in very many games like Mass Effect 1,2 and 3.

Mouse "escapes" window or is confined to an area in the full screen program
http://bugs.winehq.org/show_bug.cgi?id=6971

This is still present on the latest wine builds on Mac Osx

paulthetall · Post by **paulthetall** » Sat Mar 10, 2012 2:37 pm

cluthz wrote:I do believe it's the same issue that limits 360 degs movement in very many games like Mass Effect 1,2 and 3.

Mouse "escapes" window or is confined to an area in the full screen program
http://bugs.winehq.org/show_bug.cgi?id=6971

This is still present on the latest wine builds on Mac Osx

nope its not. Its seperate. Masseffect had always on the Mac problems, but was in the same misery as for linux until 1.3.23 or something, there it was fixed for Linux. Trouble stayed untill now. However the wine patches did work for the Mac in an old Wine version. Think the 1.1.43 or something, so....not every game can be put on this. As far as I discovered is that things broke on 1.4 RC4 while on RC3 the mouseinput worked in test Drive Unlimited.

doh123 · Post by **doh123** » Sat Mar 10, 2012 7:24 pm

Aren't those the games that want relative mouse movement? I thought Xinput2 implemented that so Wine went to Xinput2. Sadly Xinput2 on the Mac does NOT implement that because the information isn't available. It runs on top of Quartz, and Quartz does not do that at all as far as I know.

vitamin · Post by **vitamin** » Sun Mar 11, 2012 11:53 pm

doh123 wrote:Aren't those the games that want relative mouse movement? I thought Xinput2 implemented that so Wine went to Xinput2. Sadly Xinput2 on the Mac does NOT implement that because the information isn't available. It runs on top of Quartz, and Quartz does not do that at all as far as I know.

Most games always use relative mouse inputs. They don't care were the cursor is now. They need to know how far user moved the controller.

With that said, Wine needs relative actuator changes (how far user moved mouse not where the cursor is now). And XQuartz only provides absolute coordinates.

As far as workarounds for bug 6971, I think AJ broke most of them. And what more-less used to work before doesn't work now.

clocknova · Post by **clocknova** » Mon Mar 12, 2012 8:38 am

Thanoulas over at The Porting Team managed to create a working 1.4 engine wrapper for Fallout: NV by building a custom engine --without-xinput2.