Hello.
I had Mass Effect working really well awhile ago with wine 1.2. Somehow the particular prefix I used for it got deleted, and I've forgotten the magic combination I used to get it running. I was using the mouse patch from http://bugs2.winehq.org/attachment.cgi?id=25097 and had set MouseWarpOverride to force-box in the registry, as well as using winetricks to install dotnet 20, vcrun2005, physx and msxml3.
The problem I'm having is that the game graphics are painfully slow, even on the main menu, and mouse click events are often not picked up. The easiest way around this seems to be by using winetricks to install dinput8 and setting it to native. However, with this mouse movement is restricted, as in bug 6971 or bug 16822. I'm really not sure how to proceed. I've tried wine 1.3.7, 1.3.8 and 1.2 again, and I've had no luck with any of them or any combination of dinput8, the mouse patch or anything else.
I'm using ubuntu maverick 64 bit, amd 6000+ dual core cpu, a gtx260 nvidia card, and 4 gigs of ram. Thanks for any help.
Obviously, I've re-compiled wine from source each time, and I'm using this particular patch because it seems to work with mass effect 1, and it applies cleanly to all my particular versions of wine. Also using proprietary nvidia drivers.
Mass Effect and dinput8
-
- Level 5
- Posts: 336
- Joined: Mon Nov 24, 2008 8:10 am
The only patch you should really need is this one:
http://bugs.winehq.org/attachment.cgi?id=29313
No need for registry hacks then nor will you need native dinput8.
http://bugs.winehq.org/attachment.cgi?id=29313
No need for registry hacks then nor will you need native dinput8.
For mass effect 1, the issue isn't so much the mouse movment (bug 6971), the bug is really bad performance and mouse clicks not registering properly without dinput8 being enabled. I don't have the slightest idea why this would be, but there it is. This happens under a stock 64 bit kernel in ubuntu maverick, but not with a low latency kernel I installed.vitamin wrote:What exactly doesn't it fix? There are no other options of fixing bug 6971.thorin wrote:that patch alone didn't fix my issue with dinput8.