Re: [Flightgear-devel] Current CVS still not compile
Roland Häder wrote: The Phoenix joystick a 4-axis, 4-button gameport joystick (modprobe analog and some more modules for your gameport hardware). I have a SoundBlaster Live! Value here and have connected the joystick to that gameport and to the PS/2 keyboard. My keyboard is connected to the joystick. The joystick himself has around 40 buttons which I could define with a DOS program (the control center program) twice. That means I can place around 80 keys (from the keyboard and 4 buttons provided from joystick) on it + a rudder / throttle control. :) I LOVE those kind... I have the cheaper Firebird, with less buttons, but it is REALLY cool! For people who haven't experienced these wonderful devices, These joysticks have a gameport connector, and a keyboard passthrough. You can program the joystick to send keystrokes. You can even program the buttons to type commonly used sentences, cheat codes, etc. There is an easy to use DOS program to program the joystick. They are large and heavy, well built, and have a firmware microcontroller inside to remember your configuration. Oh yeah, you can also map ANY button to be one of the four buttons reported to the analog port. The design of the Firebird and Phoenix (having an internal keyboard controller) was a brilliant way to get around the limitations of the gameport. (Which, of course, supports four axis and four buttons at maximum.) This allowed for a completely insane number of buttons. I was lucky enough to get mine at Goodwill for somewhere around 3$US. (Pretty good condition, the side switch on the joystick handle sticks, but everything else works great!) --Brandon Bergren ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Current CVS still not compile
> Make a copy of the file, then edit it for your joystick and put it > somewhere FlightGear can find it. Then something like this to your > $HOME/.fgfsrc file: Ok, the attached file is my work. I simply copy and paste the area of the throttle and rename all throttle to rudder. but it doesn't work? :-? I also add the entry to the $HOME/.fgfsrc file. Roland Aileron property-scale /controls/aileron true Elevator property-scale /controls/elevator -1.0 true Throttle property-scale /controls/throttle[0] -1.0 -0.5 property-scale /controls/throttle[1] -1.0 -0.5 Rudder property-scale /controls/rudder[0] -1.0 -0.5 property-scale /controls/rudder[1] -1.0 -0.5 Brakes property-assign /controls/brakes[0] 1.0 property-assign /controls/brakes[1] 1.0 property-assign /controls/brakes[2] 1.0 property-assign /controls/brakes[0] 0.0 property-assign /controls/brakes[1] 0.0 property-assign /controls/brakes[2] 0.0 Elevator trim up true property-adjust /controls/elevator-trim 0.001 Elevator trim down true property-adjust /controls/elevator-trim -0.001
Re: [Flightgear-devel] Current CVS still not compile
> Make a copy of the file, then edit it for your joystick and put it > somewhere FlightGear can find it. Then something like this to your > $HOME/.fgfsrc file: Ok, the attached file is my work. I simply copy and paste the area of the throttle and rename all throttle to rudder. but it doesn't work? :-? I also add the entry to the $HOME/.fgfsrc file. Roland Aileron property-scale /controls/aileron true Elevator property-scale /controls/elevator -1.0 true Throttle property-scale /controls/throttle[0] -1.0 -0.5 property-scale /controls/throttle[1] -1.0 -0.5 Rudder property-scale /controls/rudder[0] -1.0 -0.5 property-scale /controls/rudder[1] -1.0 -0.5 Brakes property-assign /controls/brakes[0] 1.0 property-assign /controls/brakes[1] 1.0 property-assign /controls/brakes[2] 1.0 property-assign /controls/brakes[0] 0.0 property-assign /controls/brakes[1] 0.0 property-assign /controls/brakes[2] 0.0 Elevator trim up true property-adjust /controls/elevator-trim 0.001 Elevator trim down true property-adjust /controls/elevator-trim -0.001
Re: [Flightgear-devel] Current CVS still not compile
Roland Häder writes: > The Phoenix joystick a 4-axis, 4-button gameport joystick (modprobe > analog and some more modules for your gameport hardware). We can autodetect USB joysticks, but the old gameport ones -- that means that you'll have to configure your joystick manually, unfortunately. > /usr/local/lib/FlightGear/Input/Joysticks/Default/joystick.xml and I found > out that it is supporting just 3 axis. But my joystick does have 4 and the > last non-support axis is the rudder axis (no. 3). So what about creating a > joy-4axis.xml file? Make a copy of the file, then edit it for your joystick and put it somewhere FlightGear can find it. Then something like this to your $HOME/.fgfsrc file: --config=/home/david/lib/fgfs/my-joystick.xml That way, the file will always be loaded when FlightGear starts up. All the best, David -- David Megginson, [EMAIL PROTECTED], http://www.megginson.com/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Current CVS still not compile
On Sunday 26 January 2003 20:29, David Megginson wrote: > Roland Häder writes: > > I have also tried this. Remember your joystick.xml is for a 3-axis > > joystick. But I have a 4-axis one here: > > > > Axis 0: default > > Axis 1: default > > Axis 2: throttle > > Axis 3: rudder > > What kind of joystick is it? Does it use USB or the gameport? The Phoenix joystick a 4-axis, 4-button gameport joystick (modprobe analog and some more modules for your gameport hardware). I have a SoundBlaster Live! Value here and have connected the joystick to that gameport and to the PS/2 keyboard. My keyboard is connected to the joystick. The joystick himself has around 40 buttons which I could define with a DOS program (the control center program) twice. That means I can place around 80 keys (from the keyboard and 4 buttons provided from joystick) on it + a rudder / throttle control. :) I have checked out the file /usr/local/lib/FlightGear/Input/Joysticks/Default/joystick.xml and I found out that it is supporting just 3 axis. But my joystick does have 4 and the last non-support axis is the rudder axis (no. 3). So what about creating a joy-4axis.xml file? Chears, Roland ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Current CVS still not compile
Norman Vine writes:
> i.e. the code as written assumes FGEnvironmentMgr
> which is not included when the --with-weathercm option
> is configured
>
> // fgMainInit()
> // TODO: move to environment mgr
> thesky = new SGSky;
> SGPath texture_path(globals->get_fg_root());
> texture_path.append("Textures");
> texture_path.append("Sky");
> for (int i = 0; i < FGEnvironmentMgr::MAX_CLOUD_LAYERS; i++) {
> SGCloudLayer * layer = new SGCloudLayer(texture_path.str());
> thesky->add_cloud_layer(layer);
> }
Thanks for catching that, Norm.
All the best,
David
--
David Megginson, [EMAIL PROTECTED], http://www.megginson.com/
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Current CVS still not compile
Roland Häder writes: > I have also tried this. Remember your joystick.xml is for a 3-axis > joystick. But I have a 4-axis one here: > > Axis 0: default > Axis 1: default > Axis 2: throttle > Axis 3: rudder What kind of joystick is it? Does it use USB or the gameport? All the best, David -- David Megginson, [EMAIL PROTECTED], http://www.megginson.com/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Current CVS still not compile
> Understood it is not on purpose but it is this 'assumption'
> that is the problem
>
> i.e. the code as written assumes FGEnvironmentMgr
> which is not included when the --with-weathercm option
> is configured
>
> // fgMainInit()
> // TODO: move to environment mgr
> thesky = new SGSky;
> SGPath texture_path(globals->get_fg_root());
> texture_path.append("Textures");
> texture_path.append("Sky");
> for (int i = 0; i < FGEnvironmentMgr::MAX_CLOUD_LAYERS; i++) {
> SGCloudLayer * layer = new SGCloudLayer(texture_path.str());
> thesky->add_cloud_layer(layer);
> }
Jupp, that's the exact error I got with enabled weathercm option.
main.cxx: In function `bool fgMainInit(int, char **)':
main.cxx:1689: incomplete type `FGEnvironmentMgr' does not have member
`MAX_CLOUD_LAYERS'
Roland
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Current CVS still not compile
> What happens with jscal -c /dev/js0? Follow the numbers, even if it > seems illogical at first. I did it and here's the result as a jpeg file because I cannot copy and past the values from the terminal program. Roland <>
Re: [Flightgear-devel] Current CVS still not compile
David Megginson writes:
> Norman Vine writes:
>
> > question for those making changes in main()
> > is the --with-weathercm switch is no longer supported ?
>
> I don't know if any of the developers has it in their configuration.
> It's not omitted on purpose.
Understood it is not on purpose but it is this 'assumption'
that is the problem
i.e. the code as written assumes FGEnvironmentMgr
which is not included when the --with-weathercm option
is configured
// fgMainInit()
// TODO: move to environment mgr
thesky = new SGSky;
SGPath texture_path(globals->get_fg_root());
texture_path.append("Textures");
texture_path.append("Sky");
for (int i = 0; i < FGEnvironmentMgr::MAX_CLOUD_LAYERS; i++) {
SGCloudLayer * layer = new SGCloudLayer(texture_path.str());
thesky->add_cloud_layer(layer);
}
Regards
Norman
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Current CVS still not compile
> 1. Your joystick is not calibrated. > I have tried it with jscalibrator. I have calibrated it and started > FlightGear. Then I cannot control the plane. :( I have to rmmod analog and > modprobe analog again. > jscalibrator doesn't seem to like FG...jscalibrator is a GUI calibration program which can be found here: http://wolfpack.twu.net/libjsw/ > Then I have calibrated it with jscal (console program) and started FlightGear > again. But there's no change on it. > What happens with jscal -c /dev/js0? Follow the numbers, even if it seems illogical at first. > Well, the calibration was not completed. I did it again but it takes no > effect. :( > > > 2. You're trying to steer on the ground with the ailerons rather than > > the rudder. > I have also tried this. Remember your joystick.xml is for a 3-axis joystick. > But I have a 4-axis one here: > > Axis 0: default > Axis 1: default > Axis 2: throttle > Axis 3: rudder > > Roland > Matt ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Current CVS still not compile
On Sunday 26 January 2003 19:21, David Megginson wrote: > Roland Häder writes: > > CVS. But now I got an error message while starting it: > > > > X Error of failed request: GLXBadRenderRequest > > Major opcode of failed request: 143 (GLX) > > Minor opcode of failed request: 1 (X_GLXRender) > > Serial number of failed request: 44 > > Current serial number in output stream: 45 > > > > Well, I think that's a prob with the OpenGL system. :( > > I see that problem in Debian whenever apt-get updates my OpenGL > package and overwrites the NVIDIA GLX shared library. If that's your > situation as well, just reinstall the NVIDIA GLX library again. Jupp, that's done here. > 1. Your joystick is not calibrated. I have tried it with jscalibrator. I have calibrated it and started FlightGear. Then I cannot control the plane. :( I have to rmmod analog and modprobe analog again. Then I have calibrated it with jscal (console program) and started FlightGear again. But there's no change on it. Well, the calibration was not completed. I did it again but it takes no effect. :( > 2. You're trying to steer on the ground with the ailerons rather than > the rudder. I have also tried this. Remember your joystick.xml is for a 3-axis joystick. But I have a 4-axis one here: Axis 0: default Axis 1: default Axis 2: throttle Axis 3: rudder Roland ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Current CVS still not compile
Roland Häder writes: > Now I want to start with my Joystick but when I try to roll around > he always drifts to left with default aircraft. :( > > Any ideas? Yes, a few: 1. Your joystick is not calibrated. 2. You're trying to steer on the ground with the ailerons rather than the rudder. 3. The normal propeller effects are catching you by surprise, probably in an excessively low-speed climb, where the nose should pull hard to the left. If you climb at around 80 KIAS, the propeller effects will be fairly mild; at 55 KIAS, right on the edge of a stall, they'll be brutal. All the best, David -- David Megginson, [EMAIL PROTECTED], http://www.megginson.com/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Current CVS still not compile
Roland Häder writes: > CVS. But now I got an error message while starting it: > > X Error of failed request: GLXBadRenderRequest > Major opcode of failed request: 143 (GLX) > Minor opcode of failed request: 1 (X_GLXRender) > Serial number of failed request: 44 > Current serial number in output stream: 45 > > Well, I think that's a prob with the OpenGL system. :( I see that problem in Debian whenever apt-get updates my OpenGL package and overwrites the NVIDIA GLX shared library. If that's your situation as well, just reinstall the NVIDIA GLX library again. All the best, David -- David Megginson, [EMAIL PROTECTED], http://www.megginson.com/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Current CVS still not compile
Norman Vine writes: > question for those making changes in main() > is the --with-weathercm switch is no longer supported ? I don't know if any of the developers has it in their configuration. It's not omitted on purpose. All the best, David -- David Megginson, [EMAIL PROTECTED], http://www.megginson.com/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Current CVS still not compile
> Hi, > > Thanks, I got it compiled and installed. I have also updated the fgfsbase > by CVS. But now I got an error message while starting it: > > X Error of failed request: GLXBadRenderRequest > Major opcode of failed request: 143 (GLX) > Minor opcode of failed request: 1 (X_GLXRender) > Serial number of failed request: 44 > Current serial number in output stream: 45 > > Well, I think that's a prob with the OpenGL system. :( Ok, that's also fixed: mixed-up libraries. Now I want to start with my Joystick but when I try to roll around he always drifts to left with default aircraft. :( Any ideas? Roland ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Current CVS still not compile
On Sunday 26 January 2003 18:06, Norman Vine wrote: > Roland Häder writes: > > My config.sh script looks like this: > > ./configure --with-x --with-weathercm --with-network-olk > > --with-jpeg-factory=yes > > > > main.cxx: In function `bool fgMainInit(int, char **)': > > main.cxx:1689: incomplete type `FGEnvironmentMgr' does not have member > > `MAX_CLOUD_LAYERS' make[2]: *** [main.o] Error 1 > > Try > > % rm config.cache > % ./configure --with-x --with-jpeg-factory=yes > > question for those making changes in main() > is the --with-weathercm switch is no longer supported ? Hi, Thanks, I got it compiled and installed. I have also updated the fgfsbase by CVS. But now I got an error message while starting it: X Error of failed request: GLXBadRenderRequest Major opcode of failed request: 143 (GLX) Minor opcode of failed request: 1 (X_GLXRender) Serial number of failed request: 44 Current serial number in output stream: 45 Well, I think that's a prob with the OpenGL system. :( Roland ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Current CVS still not compile
Roland Häder writes: > > My config.sh script looks like this: > ./configure --with-x --with-weathercm --with-network-olk --with-jpeg-factory=yes > main.cxx: In function `bool fgMainInit(int, char **)': > main.cxx:1689: incomplete type `FGEnvironmentMgr' does not have member >`MAX_CLOUD_LAYERS' > make[2]: *** [main.o] Error 1 Try % rm config.cache % ./configure --with-x --with-jpeg-factory=yes question for those making changes in main() is the --with-weathercm switch is no longer supported ? Norman ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Current CVS still not compile
On Sunday 26 January 2003 17:52, David Megginson wrote: > Roland Häder writes: > > My config.sh script looks like this: > > ./configure --with-x --with-weathercm --with-network-olk > > --with-jpeg-factory=yes > > OK, first take out all of the options and just do > > ./configure Ok, first I'm sorry for these words from me. I think everyone get a bit angry when he reports a problem and no answer comes back. :( Well, let's get back to the show. The jpeg factory is an interesting part for me because screenshot making so I enable it. Maybe someone of you can explain me the different between WeatherCM and FGEnviroment? Or can you give me a hint where I can find informations about it? When there's a special non-sourcecode-creating option I try it. :) Chears, Roland ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
re: [Flightgear-devel] Current CVS still not compile
Roland Häder writes: > My config.sh script looks like this: > ./configure --with-x --with-weathercm --with-network-olk --with-jpeg-factory=yes OK, first take out all of the options and just do ./configure All the best, David -- David Megginson, [EMAIL PROTECTED], http://www.megginson.com/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
