(edited by Leila.7269)
MAC: 64bit via Wine mouse issue
cool, I never thought it would happen. They did say that mac os 64 abi broke windows 64 bit abi. I guess they found a good work around.
https://www.winehq.org/announce/2.0
https://www.winehq.org/pipermail/wine-devel/2014-February/103074.html
edit: i forgot to write about the mouse issues because I was amazed at crossover ability to develop wine over the years
I wonder if winehq db allows mac submissions
https://appdb.winehq.org/objectManager.php?sClass=version&iId=32861
You should report the bug here.
Support the wine community by reporting bugs or buy license from codeweavers
(edited by loseridoit.2756)
cool, I never thought it would happen. They did say that mac os 64 abi broke windows 64 bit abi. I guess they found a good work around.
https://www.winehq.org/announce/2.0
https://www.winehq.org/pipermail/wine-devel/2014-February/103074.html
edit: i forgot to write about the mouse issues because I was amazed at crossover ability to develop wine over the years
I wonder if winehq db allows mac submissions
https://appdb.winehq.org/objectManager.php?sClass=version&iId=32861
You should report the bug here.
Support the wine community by reporting bugs or buy license from codeweavers
Regarding the ABI, essentially the workaround has been to ignore the issue. Turns out a lot of Windows software doesn’t utilise it anyway / calls other APIs that utilise it where Wine’s implementations can simply not make use of that CPU register.
If I recall correctly the bug isn’t actually necessarily one in Wine itself but if memory serves if you’re using Wineskin if you choose to use the Aqua (native Mac) display server rather than X11 that solves this problem. I’ll test when I’ve got a moment.
cool, I never thought it would happen. They did say that mac os 64 abi broke windows 64 bit abi. I guess they found a good work around.
https://www.winehq.org/announce/2.0
https://www.winehq.org/pipermail/wine-devel/2014-February/103074.html
edit: i forgot to write about the mouse issues because I was amazed at crossover ability to develop wine over the years
I wonder if winehq db allows mac submissions
https://appdb.winehq.org/objectManager.php?sClass=version&iId=32861
You should report the bug here.
Support the wine community by reporting bugs or buy license from codeweavers
Regarding the ABI, essentially the workaround has been to ignore the issue. Turns out a lot of Windows software doesn’t utilise it anyway / calls other APIs that utilise it where Wine’s implementations can simply not make use of that CPU register.
If I recall correctly the bug isn’t actually necessarily one in Wine itself but if memory serves if you’re using Wineskin if you choose to use the Aqua (native Mac) display server rather than X11 that solves this problem. I’ll test when I’ve got a moment.
Sometimes, I wish I was better at ASM/C/OS etc so I can understand these problems.
Either way, I wonder why Anet has contracted Transgaming but not codeweavers.
codeweavers has always been better at delivering Windows runtime
So after some tinkering around and further web searches and some testing I concluded it was some bad mouse drives at the OS level that was causing the issue. Oddly It only seemed to occur in Guild Wars that I’d noticed, but none the less.
Meanwhile I’m still working on squeezing better performance out for WvW cause 3-5fps in zerg isn’t ok. Hopefully do some testing tonight when things are populated and see how it looks. I suspect that, in part, Transgaming was using some proprietary drivers to get the performance out the official client – which runs great until it crashes….
For anyone curious I think I’ve seen the 64bit wine client use upwards of near 4.5 gigs of ram and hasn’t fully utilized the vram or gpu processing of the GTX780M 4096 from monitoring via iStats.