Re: [Flightgear-devel] Anyone using a Saitek Cyborg Gold USB Stick successfully with FG ?
Andy Ross [EMAIL PROTECTED] said: Jim Wilson wrote: Was in sound card hell myself a few nights ago, so I can relate. Finally decided my time was worth something and went out to buy an sblive Actually it was an intel chipset on a compaq enterprise type computer. Canned configs we buy at work. Just happens that I telecommute so when something good comes in I can grab it and swap it in here. Apparently 8 bit sound isn't supported. The previous compaq I had took an isa sb32 that I had, but the new boards don't have the isa slots. So I threw in a yamaha pci that I had sitting around. It worked pretty well, better with the alsa driver (a little scratchy though), but there were still problems with some of the oss stuff I run. Anyway, the sblive works flawlessly here, and has good open support. Just seemed like the right thing to do. The new machine is really cool--way fast and tons of disk and ram. Even came with a 32 mb geforce 2 oem'd for compaq in the standard config. One thing odd I noticed: while the frame rate is _much_ faster than the old voodoo, it is choppy when I start flight gear before atlas (windowed dri). If I run atlas first, it is fine. Best, Jim ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Anyone using a Saitek Cyborg Gold USB Stick successfully with FG ?
Victoria Welch [EMAIL PROTECTED] said: Hi All, Just wondering if anyone else uses this stick successfully? It works perfectly here under windoz but after *hours* of changing the .fgfsrc and starting and stopping fg for each change, I am getting a little discouraged. I'm not, but I am using a USB stick (MSSW). Does it show in usbview? If it doesn't then it is your usb hid module config: Modules required: usbcore usb-uhci input hid joydev If it then works in jstest, then all you need to do is make a config file that maps the axes and buttons to functions. Look in the base backage for other examples (Input/Joysticks/) Caveat: In my case I'm running a plib release (not cvs) and therefore the actual config has to be placed in fgfsbase/joysticks.xml. To use the new setup (the default in base package cvs) you will need a current cvs of plib. If you do an old style config (using a plib release like I currently use) in the joysticks.xml you need to make sure the settings are wrapped in these tags: PropertyList js (axis and button configs here) /js /PropertyList Look in the Docs/README.Joystick.html file for more info on configuring joystick bindings. The other and perhaps better alternative is to run plib from CVS if you aren't already and just create a Saitek configuration file in the Inputs/Joysticks directory tree. Once you get something that works well you might want to submit the resulting config so that we can add it to the package. From what I understand Saitek makes very good devices for flight simmers. Best, Jim ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Anyone using a Saitek Cyborg Gold USB Stick successfully with FG ?
Victoria Welch [EMAIL PROTECTED] said: All loaded, I have to load joydev manually, but all are loaded and catting js0 results in changing garbage on the screen. Good sign. If it then works in jstest, then all you need to do is make a config file that maps the axes and buttons to functions. Look in the base backage for other examples (Input/Joysticks/) Nevermind. You've got js_demo (part of flightgear) that basically dose the same thing. Well, at least under windoz the saitek stick has been a joy :-). If I ever figure out what all this means and get it to work I'll sure submit it for inclusion :-). Look at that doc file. If you aren't into learning the xml configuration and just want to see if something will work, just get the plib cvs (plib.sf.net) and more than likely you'd have ailerons and elevators with the default config (Umm...waiting for a real saitek owner to chime in here:)) I didn't think it was possible to be more confused, but I was wrong :-). Been at this hard an long bringing up the new systems and getting a lot of different things to work and I am starting to feel a little burned out. I'm going to get away from it for a few days and see how I feel about it all. That can often be the best approach! Was in sound card hell myself a few nights ago, so I can relate. Finally decided my time was worth something and went out to buy an sblive (no I'm not implying that you need a different stick;)). Trying to use a card from a vendor that won't release either specs or a linux driver was a very bad idea and the motherboard chip was a little too plain vanilla to work well. Wasn't I happy when that sblive kudzu-ed perfectly. Best, Jim ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
