Force Feedback Support in FlightGear: Difference between revisions

From FlightGear wiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 1: Line 1:
{{Stub}}
{{Stub}}
== Motivation ==
{{FGCquote
|1= can FG have force vibration for flight sticks please (maybe as an option on the wiard)
|2= {{cite web
  | url    = http://forum.flightgear.org/viewtopic.php?p=192237#p192237
  | title  = <nowiki> vibration</nowiki>
  | author = <nowiki>pilot</nowiki>
  | date  = Oct 22nd, 2013
  }}
}}


{{FGCquote
{{FGCquote

Revision as of 15:26, 29 December 2015

This article is a stub. You can help the wiki by expanding it.

Motivation

Cquote1.png can FG have force vibration for flight sticks please (maybe as an option on the wiard)
— pilot (Oct 22nd, 2013).  vibration.
(powered by Instant-Cquotes)
Cquote2.png
Cquote1.png Anyone seeing this yet? http://sourceforge.net/p/hapticsforfg/code/HEAD/tree/ It would be very interesting to have Force Feedback on FG,since I don't know any sim in development having FF.
— Poomklao Teerawattanaprapha (Dec 29th, 2015). [Flightgear-devel] Feature commit request:Force feedback.
(powered by Instant-Cquotes)
Cquote2.png

Status

Cquote1.png For the last few days I have coded force feedback support for FlightGear. It currently works, I have implemented control surface loading (for jsbsim), pilot g forces and stick shaker.

Currently the system is so that I have external app which uses SDL 1.3 to handle the ff effects, so it should be portable quite easily. That program communicates with FG through telnet, and some nasal/xml magic on FG does the rest. Here's a screenshot of the configuration options (from which most do not yet work, but you get the idea):

(see the linked image) I will support: multiple devices, autocenter, control surface forces, pilot g forces and stick shaker at least. And all effects can be disabled, or disabled/enabled on some devices, and also axes should be configurable.

Now, the problem is that telnet interface is way too slow, the forces are updated once every 1 or 2 seconds, which is awfull. But I still don't know beforehand which properties to pull, so generic I/O is not good either. Does anyone have any ideas on how to solve this?
— Zan (Dec 19th, 2011).  .
(powered by Instant-Cquotes)
Cquote2.png