Hum, Strange.
Those wine tests look just fine. They seem to be implying that it is
finding your joystick and able to read its buttons and such. That would
lead me to believe that the games would also be able to find it.
Could you maybe provide me a +dinput log of you starting up one of these
On Fri, May 22, 2009 at 4:54 AM, Mike Kronenberg
wrote:
> On 22.05.2009, at 05:05, Nathan Gray wrote:
>
>> On Thu, May 21, 2009 at 10:45 AM, Aric Stewart
>> wrote:
>>>
>>> Well the Mac OS X Joystick code will only work on Leopard.
>>> So you will have to build and run it on Leopard box using xco
On Thu, May 21, 2009 at 10:45 AM, Aric Stewart wrote:
>
> If you are good there then try building the winetests for dinput and run
> them with your joystick plugged in. You should get some status traces about
> your joystick (finding the name and status of the various axes and buttons)
Ok, I buil
On 22.05.2009, at 05:05, Nathan Gray wrote:
On Thu, May 21, 2009 at 10:45 AM, Aric Stewart
wrote:
Well the Mac OS X Joystick code will only work on Leopard.
So you will have to build and run it on Leopard box using xcode3.
I'm certainly running on Leopard, but I can't say how Mike built it
On Thu, May 21, 2009 at 10:45 AM, Aric Stewart wrote:
> Well the Mac OS X Joystick code will only work on Leopard.
> So you will have to build and run it on Leopard box using xcode3.
I'm certainly running on Leopard, but I can't say how Mike built it.
> If you are good there then try building t
Well the Mac OS X Joystick code will only work on Leopard.
So you will have to build and run it on Leopard box using xcode3.
If you are good there then try building the winetests for dinput and run
them with your joystick plugged in. You should get some status traces
about your joystick (findi
