http://bugs.winehq.org/show_bug.cgi?id=6971
--- Comment #281 from Xavier Vachon <xvachon(a)gmail.com> 2009-12-06 20:49:16 ---
(In reply to comment #280)
> Ok, even though I can't claim to understand quite how the two patches works,
> I've created a new version of the patch
> http://bugs.winehq.org/attachment.cgi?id=21554 that should work on 1.1.34.
>
> It incorporates elements from both patches, but I don't think that it will
> reproduce the behaviour of the force-box patch (someone with a better
> understanding would need to take a look!) - it would be nice if we could
> combine the two.
>
> Tested patch and confirmed behaviour from 21554 patch restored - I now have a
> working mouse in Mass Effect! :)
>
> Under /home/$USERNAME/.wine/user.reg, following settings did not reproduce the
> restricted mouse movement, so guessing it now ignores "force-box":
>
> [Software\\Wine\\DirectInput] 1258814435
> "MouseWarpOverride"="force-box"
> "BoxPixels"="10"
>
> Basic howto (as root) - you can see I've made the patch against the bz2 file
> from sourceforge rather than from git:
>
> wget http://downloads.sourceforge.net/project/wine/Source/wine-1.1.34.tar.bz2
> tar xjvf wine-1.1.34.tar.bz2
> cd wine-1.1.34
> wget http://bugs.winehq.org/attachment.cgi?id=25097 -O mousewarp-1.1.34.patch
> #Download other patches you may want at this point
> patch -p1 < mousewarp-1.1.34.patch
> autoreconf
> ./configure
> make depend && make
> make install
>
> To run Mass Effect from Steam, I use:
> WINEFORCEMOUSEWARP=yes wine "C:\Program Files\Steam\steam.exe"
>
> Then I start it up from the My Games list.
>
> Hope this helps someone. Apologies for not being clearer, it's late and I need
> sleep! ;)
I tested the patch with Assassin's Creed. If I play full screen I have not
experienced problems so far, but if I play in windowed mode the mouse still
escapes during gameplay. I run the game with :
env WINEDEBUG=-all WINEFORCEMOUSEWARP=yes wine "AssassinsCreed_Launcher.exe"
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=6971
--- Comment #280 from Rob Whalley <mail(a)robwhalley.co.uk> 2009-12-06 20:07:13 ---
Ok, even though I can't claim to understand quite how the two patches works,
I've created a new version of the patch
http://bugs.winehq.org/attachment.cgi?id=21554 that should work on 1.1.34.
It incorporates elements from both patches, but I don't think that it will
reproduce the behaviour of the force-box patch (someone with a better
understanding would need to take a look!) - it would be nice if we could
combine the two.
Tested patch and confirmed behaviour from 21554 patch restored - I now have a
working mouse in Mass Effect! :)
Under /home/$USERNAME/.wine/user.reg, following settings did not reproduce the
restricted mouse movement, so guessing it now ignores "force-box":
[Software\\Wine\\DirectInput] 1258814435
"MouseWarpOverride"="force-box"
"BoxPixels"="10"
Basic howto (as root) - you can see I've made the patch against the bz2 file
from sourceforge rather than from git:
wget http://downloads.sourceforge.net/project/wine/Source/wine-1.1.34.tar.bz2
tar xjvf wine-1.1.34.tar.bz2
cd wine-1.1.34
wget http://bugs.winehq.org/attachment.cgi?id=25097 -O mousewarp-1.1.34.patch
#Download other patches you may want at this point
patch -p1 < mousewarp-1.1.34.patch
autoreconf
./configure
make depend && make
make install
To run Mass Effect from Steam, I use:
WINEFORCEMOUSEWARP=yes wine "C:\Program Files\Steam\steam.exe"
Then I start it up from the My Games list.
Hope this helps someone. Apologies for not being clearer, it's late and I need
sleep! ;)
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=20937
Summary: (WoW) A model in Grizzly Hills causes a WINE (not a
WoW) crash.
Product: Wine
Version: unspecified
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: vistro(a)vistro.net
I don't know what model it is, but whatever it is, when it appears on screen,
WINE (Not WoW) crashes. I get a windows style error.
The model is present in Grizzly Hills. I will add to this list whenever it
crashes.
coordinates where the crash occurs:
19.4 59.4 (facing away from Conquest Hold)
Looking towards the above location while in the air above conquest hold
The graveyard cloesest to Conquest Hold.
That means that the model that causes the crash is present in these locations.
It could be an herb, mining node, or vegetation. I know it's not an animal.
This really sucks.
There are two ways to fix this:
1. Keep logging on and hold down a left or right button to move your character
a little before the crash occurs. If you are lucky, you will only waste 10
minutes doing this.
2. Log on to a Windows machine and hearth your character.
This bug happens on Ubuntu version 9.04 AND 9.10. It happens on EVERY WINE
version that is available in synaptic. I have tried clearing my cache. I have
done it on other computers.
If you want, I can run WoW in a terminal to determine the problem. Please help
me out here!
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=20918
Summary: Many valgrind warnings in advapi32/crypt tests in
test_incorrect_api_usage()
Product: Wine
Version: 1.1.33
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: crypt32
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: dank(a)kegel.com
http://kegel.com/wine/valgrind/logs/2009-12-03-17.17/vg-advapi32_crypt.txt
has a dozen or so invalid read and memory leak warnings.
I'm going to suppress the invalid read errors on the theory that
they are intended and benign. If this is so, please close this bug
as invalid.
(As usual, the suppression name will contain the number of this bug
so people wondering what it's for can find the bug report and any discussion.)
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=201
Austin English <austinenglish(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Blocks| |20924
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=6971
Rob Whalley <mail(a)robwhalley.co.uk> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mail(a)robwhalley.co.uk
--- Comment #278 from Rob Whalley <mail(a)robwhalley.co.uk> 2009-12-06 18:17:14 ---
Just some feedback: I was using the patch from
http://bugs.winehq.org/attachment.cgi?id=21554 on 1.1.33 to get mouse working
on Mass Effect (via Steam). This was working well.
As Xavier notes above, this patch no longer works with 1.1.34. I have
successfully built Wine 1.1.34 with the newer warp-force-box.patch, however it
does not work for Mass Effect. When you try and use the mouse it snaps
immediately back to the centre of the screen, even with different box sizes
specified in the registry.
I did consider trying to modify the older 21554 patch but am afraid it's way
over my head :(
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=8221
Niko Sandschneider <nsandschn(a)gmx.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |nsandschn(a)gmx.de
--- Comment #9 from Niko Sandschneider <nsandschn(a)gmx.de> 2009-12-06 18:01:51 ---
Still present in wine 1.1.34
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=7961
Niko Sandschneider <nsandschn(a)gmx.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |nsandschn(a)gmx.de
--- Comment #13 from Niko Sandschneider <nsandschn(a)gmx.de> 2009-12-06 17:40:10 ---
Still present in wine 1.1.34
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=6971
Warren Dumortier <nwarrenfl(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |nwarrenfl(a)gmail.com
--- Comment #277 from Warren Dumortier <nwarrenfl(a)gmail.com> 2009-12-06 16:47:37 ---
Does the 'force-box' option allow to use the menus using the mouse or is it
just an alternative to 'force'? What is the difference then?
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.