I wanted to release the windows and mac os early ports force feedback on
the 1st (two days ago), but haven’t been able to. Release is delayed
but will hopefully be done before the end of the project. Currently
both the mac os x and the windows implementations are mostly finished
but each has it’s own issues:
Mac OS X: As I said before, I don’t have access to the hardware
needed to test it, so I’m dependent on testers. It shouldn’t take too
much work to polish.
Windows: Implementation is mostly done, just need to polish some
issues because it appears DirectInput pretty much forces you to
designate a window to use force feedback, complicating things quite a
bit. Since ideally the force feedback system is independent of
window(s), this will bring issues.
Linux: Minor improvements and bug fixes. Pretty much the same since
0.1 release.
When the windows and mac os x ports are finished, I will do the 0.5
release and then just polish until GSoC is over. Like always you are
free to try the force feedback branch located at: http://svn.libsdl.org/branches/gsoc2008_force_feedback
If you want to help out testing the Mac OS X port, please get in contact
with me via e-mail or on irc.
Edgar
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
I haven’t actually tested the new haptic stuff, but I’ve looked at the API a
little, and I have a question. Some controllers, like the XBox controller,
has two separate motors that can be controlled separately. How does the API
handle that? Do you get back a single SDL_Haptic device for the controller,
or one for each motor, or what?–
View this message in context: http://www.nabble.com/Haptic-Subsystem-Update-tp18803113p18815933.html
Sent from the SDL mailing list archive at Nabble.com.
Instead of controlling each motor individually you have something called
effect types which are implemented by the driver being used. In the
case of the XBox controller which is a simple gampad device with two
motors (small and big one), you would have something called "Periodic"
effects. These allow you to do a repetitive wave in time. The settings
of the effect would determine how the motors are used, you do not have
to worry about this.
You only get one SDL_Haptic device per physical device (unless for some
reason it broadcasts itself as two different physical devices).
Currently only the Linux port is known to be working fully. I’m working
hard on the other ones, but they’re much more complicated.
Edgar
BradDaBug wrote:
I haven’t actually tested the new haptic stuff, but I’ve looked at the API a
little, and I have a question. Some controllers, like the XBox controller,
has two separate motors that can be controlled separately. How does the API
handle that? Do you get back a single SDL_Haptic device for the controller,
or one for each motor, or what?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)