re: [Flightgear-devel] Current CVS still not compile

2003-01-26 Thread David Megginson
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.c

Re: [Flightgear-devel] Current CVS still not compile

2003-01-26 Thread Roland Häder
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 s

Re: [Flightgear-devel] Current CVS still not compile

2003-01-26 Thread Norman Vine
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' >

Re: [Flightgear-devel] Current CVS still not compile

2003-01-26 Thread Roland Häder
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 t

Re: [Flightgear-devel] Current CVS still not compile

2003-01-26 Thread Roland Häder
> 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) >

Re: [Flightgear-devel] Current CVS still not compile

2003-01-26 Thread David Megginson
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://w

Re: [Flightgear-devel] Current CVS still not compile

2003-01-26 Thread David Megginson
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

Re: [Flightgear-devel] Current CVS still not compile

2003-01-26 Thread David Megginson
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.

Re: [Flightgear-devel] Current CVS still not compile

2003-01-26 Thread Roland Häder
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_GLXRend

Re: [Flightgear-devel] Current CVS still not compile

2003-01-26 Thread Matthew Johnson
> 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 w

Re: [Flightgear-devel] Current CVS still not compile

2003-01-26 Thread Norman Vine
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 b

Re: [Flightgear-devel] Current CVS still not compile

2003-01-26 Thread Roland Häder
> 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

2003-01-26 Thread Roland Häder
> 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; >

Re: [Flightgear-devel] Current CVS still not compile

2003-01-26 Thread David Megginson
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, D

Re: [Flightgear-devel] Current CVS still not compile

2003-01-26 Thread David Megginson
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()); >

Re: [Flightgear-devel] Current CVS still not compile

2003-01-26 Thread Roland Häder
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

Re: [Flightgear-devel] Current CVS still not compile

2003-01-26 Thread David Megginson
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.

Re: [Flightgear-devel] Current CVS still not compile

2003-01-26 Thread Roland Häder
> 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

Re: [Flightgear-devel] Current CVS still not compile

2003-01-30 Thread Roland Häder
> 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

Re: [Flightgear-devel] Current CVS still not compile

2003-01-31 Thread Brandon Bergren
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 joy