The reason for this is because of the XInput API, which is used for providing support for the XBox 360 controller and which is not available for Windows 2000. The 360 controller will work via the standard Quake joystick code, but it's functionality is quite poor.
Would anybody cry if I removed the 360 code? Because otherwise it works quite beautifully on Windows 2000. In other words, which is more important: controller support or Windows 2000 support?
Update: I went with plan C, which was to dynamically load the required XInput DLL and entrypoints (there's only 2 of them) at startup, which gives both 360 support and Windows 2000 support.
Now to see if I can get this baby to run on Windows 98...
Update 2: When I say "run on Windows 98" of course I mean it as an intellectual exercise moreso than anything else. It would be nice to have it of course, but it's not something I would otherwise break the engine for...
Sunday, March 21, 2010
DirectQ doesn't work on Windows 2000
Posted by
mhquake
at
1:04 AM
Subscribe to:
Post Comments (Atom)
3 comments:
I say scrap the XBOX Controller Support. Who cares about a piece of Console rubbish that should stay where it belongs -- on a CONSOLE. Operating System compatibility is more important, IMHO.
I love the fact that there is controller support. I wouldnt cry if it was gone because I dont use it.. but it is one of the reasons I picked up DQ in the first place. I'm looking for that mod that the controller makes perfect.
All in all I'm quite happy to see the controller support there every time im looking through the menu.
Ah, well, nice to see you could find a workaround, 'Tony'; you are the Iron Man of Quake!
Post a Comment