lfmgtc59 wrote in Thu Aug 27, 2015 2:36 pm:I think I will run this on an XP system, but have a Win 7 64 bit system available.
my experience with a Saitek X-52 saw that it was better supported under Win XP, the software itself "SST" did not run well on Windows 7. and the latest drivers dated back to 2007... but you have X-55 which is newer(i assume), so you might want to try compatibility yourself.
lfmgtc59 wrote in Thu Aug 27, 2015 2:36 pm:1. Am I correct in my understanding that the profile (stored as "pr0") created by the X55 setup software should not, or cannot be used in Flightgear, and that it will require a custom XML file to utilize the Joystick & Throttle?
pr0 files are loaded by
SST (Saitek Smart Technology), you can bind buttons/axis to act as keystrokes, example you can bind Button 1 to keystroke 'g' (this will trigger landing gear), but Flight Gear will read both keystroke 'g' and whatever is assigned to Button 1 in the XML file.
input devices like joysticks usually run with a default xml if there was not a corresponding xml. currently there is no X-55 xml file shipped with Flight Gear.
lfmgtc59 wrote in Thu Aug 27, 2015 2:36 pm:2. If so, I am assuming that the XML is called from the Flightgear App and will locate, identify, and configure the X55 and pedals from within the Flightgear App ignoring the native X55 & pedal profiles, and does this include the setup of the axis for ailerons, elevator, and rudder - curves & dead space etc. that is accessed through the setup software?
yes, you can assign curves and deadzone in Flight Gear, but it is limited to applying a square function to the input curve. if there was capability to adjust curves from the joystick software you use that instead and keep the xml clean from applying any filtering to the input. but you have to use Flight Gear to assign a joystick axis to a control surface.
lfmgtc59 wrote in Thu Aug 27, 2015 2:36 pm:3. Will each type of plane (single / multi engine, prop vs jet etc.) require a separate XML file for correct operation or may all these be successfully merged into a single XML file?
yes you can, but that will involve using the (scripting?) language of Nasal, with the SST software you can do the same to do modes, but i'm afraid that will be limited, you cannot swap axis in SST, but only change keystroke binds. for example you cannot turn one of the dual throttles to a mixture lever control, but you can do that from an XML.
lfmgtc59 wrote in Thu Aug 27, 2015 2:36 pm:Finally, I've seen the XML files for some of this in the various forums, but am wondering is there something out there that outlines this setup or process, where each file goes to make this all work correctly.
http://wiki.flightgear.org/Writing_Joystick_Code:_Part_1you can also check the Input/Joysticks file in Flight Gear directory to check for examples