Re: [Flightgear-devel] Speedbrakes / Spoilers
James Turner wrote: I've been spending as much time as possible over the past few days just flying around (I've had a very long gap where FG wouldn't build and I was busy with other things), but this has raised a small issue which may indicate something about my flying habits... Basically, I have not yet found an aircraft where the speedbrakes or spoilers seem to work, either visually or in terms of slowing the plane down. From looking at data/keyboard.xml, I can see the current bindings are j/k for the spoilers, and Ctrl-B for the speedbrake, but pressing the keys doesn't seem to do anything. So, have I missed something here? In particular, which models should have spoilers and speedbrakes that definitely work, and maybe even animate? I could swear I recall seeing pictures of the Fokker-100 with it's 'distinctive' tail brake assembly deployed. Sorry for jumping in so late, bet here it goes; The Fokker 100 has both speedbrake (Ctrl+B) and Spoiler (Shift+S) support. The model has been redesigned and improved significantly but there seemed to have a typo introduced for the animations. Both the spoiler and speedbrake are supported in the FDM though. Also the F-16 does have working speedbrakes. Erik ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] segfault in SimGear code
sorry, not the *commandline* below causes fg to break but similar
.fgfsrc file...
fgfs --airport=EDHI --aircraft=bo105 --enable-game-mode
#
Again, only a present .fgfsrc with similar content causes a segfault,
the commandline let fg regulary start.
Second hint: following message appeared twice:
Failed to find runway 28R at airport EDHI --aircraft=bo105
--enable-game-mode
Failed to find a good runway for EDHI --aircraft=bo105 --enable-game-mode
gdb session points on
Autopilot/xmlauto.cxx:804 ff
static void update_helper( double dt ) {
// Estimate speed in 5,10 seconds
static SGPropertyNode *vel = fgGetNode( /velocities/airspeed-kt,
true );
static SGPropertyNode *lookahead5
= fgGetNode( /autopilot/internal/lookahead-5-sec-airspeed-kt,
true );
static SGPropertyNode *lookahead10
= fgGetNode( /autopilot/internal/lookahead-10-sec-airspeed-kt,
true );
static double average = 0.0; // average/filtered prediction
static double v_last = 0.0; // last velocity
double v = vel-getDoubleValue(); = segfault
obvisously the last thread has no longer access to valid property nodes.
Regards
Ron
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Introducing super.diff
As FlightGear keeps adding new key definitions, it becomes increasingly difficult to maintain local key bindings. When you finally found a free and appropriate key, you can be sure that the next day someone will use the exact same key for an important feature of his aircraft. This doesn't overwrite your definition, of course, but your definition masks the official binding. So, once again, you are in search of a free key. But these times are over ... http://members.aon.at/mfranz/flightgear/super.html s. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] SG and FG build breaks on mac os x.3 (10.3)
[EMAIL PROTECTED] wrote: Various mac os x specific build breaks with Saturday 5 february 2005 cvs source. Flightgear: The src/input Makefile needs: base_LIBS = -framework IOKit -framework CoreFoundation to successfully build fgjs and js_demo on mac os x.3 (10.3) This should be fixed in CVS (make sure you run autogen.sh and configure again). also: /utils/modeller g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I/Users/ima/Desktop/FlightGear/fgdev9.8/include -g -O2 -D_REENTRANT -c -o normalmap.o `test -f 'normalmap.cxx' || echo './'`normalmap.cxx normalmap.cxx: In function `int main(int, char**)': normalmap.cxx:82: error: `err_str' undeclared (first use this function) You have to make sure you are using the latest version of SimGear (and have it's header files installed). There where some definitions added to the SGTexture class. SimGear: g++ -DHAVE_CONFIG_H -I. -I. -I../../simgear -I../.. -DGLX_GLXEXT_PROTOTYPES -I/Users/ima/Desktop/FlightGear/fgdev9.8/include -g -O2 -D_REENTRANT -c -o RenderTexture.o `test -f 'RenderTexture.cpp' || echo './'`RenderTexture.cpp I think I've fixed this one also in CVS now. Erik ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Mac joysticks
James Turner wrote: I finally managed to get my FlightGear behaving itself last week - there are a few issues I want to investigate before I bring them up here, but one affected me almost immediately - the input code as it stands right now means Mac joysticks tend not to be recognised. There are two issues: firstly, when support was added in the XML joystick definitions for platform specific axis / button identifiers, a case was added for 'mac' as well as 'unix' and 'windows' - but most (none?) of the joystick files actually use this tag. Now, one option is to go around adding 'mac' tags, but at least for my SideWinder, the OS-X axis / button assignments match the Unix ones. I would be prepared to bet a small sum of money that most of the time, the assignments are going to match ... but of course I can't be sure until Mac users with some of the existing joysticks test this. (Knowing what happens with the logitech and thrustmaster sticks would be interesting) I've committed a patch that adds mac support for all joysticks that had UNIX definitions. Erik ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Introducing super.diff
Superman wrote: As FlightGear keeps adding new key definitions, it becomes increasingly difficult to maintain local key bindings. When you finally found a free and appropriate key, you can be sure that the next day someone will use the exact same key for an important feature of his aircraft. This doesn't overwrite your definition, of course, but your definition masks the official binding. So, once again, you are in search of a free key. But these times are over ... http://members.aon.at/mfranz/flightgear/super.html The only problem with this is that it encourages people to use key combinations which are then unavailable to people running without SDL. -- Jon Stockill [EMAIL PROTECTED] ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Speedbrakes / Spoilers
Ampere K. Hardraade wrote: For commercial airliners at least, it will make more sense to map the reverse to Ctrl+PgDown. The reason being is that the throttles are mapped to PgUp and PgDown, and thrust-reverse is part of the throttles. Erik Hofman wrote: The Fokker 100 has both speedbrake (Ctrl+B) and Spoiler (Shift+S) support. The model has been redesigned and improved significantly but there seemed to have a typo introduced for the animations. Is it a tall order to kindly request aircraft modellers to coordinate on a consistent key mapping ? Especially after reading Melchior's listing of the actual key-mappings I definitely think the user should _not_ be burdened with such a confusion. Thanks for listening, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: Introducing super.diff
* Jon Stockill -- Friday 11 February 2005 17:36: Superman wrote: http://members.aon.at/mfranz/flightgear/super.html The only problem with this is that it encourages people to use key combinations which are then unavailable to people running without SDL. This wasn't posted for submission, but for people who have the same problem that I have. And if someone is submitting an aircraft using key numbers =1000, well, bad luck. Their aircraft won't fully work then for all, and sooner or later they'll notice. Or not. I don't care. Oh, and of course the map.pdf generator will bark if it sees such a key number. m. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Speedbrakes / Spoilers
Martin Spott wrote: The Fokker 100 has both speedbrake (Ctrl+B) and Spoiler (Shift+S) support. The model has been redesigned and improved significantly but there seemed to have a typo introduced for the animations. Is it a tall order to kindly request aircraft modellers to coordinate on a consistent key mapping ? Especially after reading Melchior's listing of the actual key-mappings I definitely think the user should _not_ be burdened with such a confusion. I agree. Although I do think the spoilers of the Fokker 100 are employed automatically on touchdown, but I'm not yet certain about that. Erik ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Speedbrakes / Spoilers
Erik Hofman wrote: I agree. Although I do think the spoilers of the Fokker 100 are employed automatically on touchdown, but I'm not yet certain about that. You're absolutely correct, Erik. I don't ask people to force-match their aicrcraft model on a common standard where the _real_ aircraft is different. Where real aircraft _are_ different they actually should be handled different in FlightGear as well. It's just that people will believe we're mad when we put two or three different keybindings for a thing as simple as a speed brake into FlightGear. Typical users, no matter if they are real pilots and expect a realistic sim or if they are just 'gamers', won't spend the effort to notice that these different aircraft with their respective key-bindings stem from different authors with different preferences. They will take the short-cut and call the current situation a mess :-) To be honest, I myself would call this a mess as well, although I know that these models have evolved from different sources Cheers, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: Speedbrakes / Spoilers
* Martin Spott -- Friday 11 February 2005 07:14: [...] Tried to answer directly, but your mail server is rejecting my message. I can't be bothered to write everything again. No, there's no license on map.tex/map.pdf. You can treat it as Public Domain. (No, I'm not a spammer.) m. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Qt 4 will be GPLed for all supported systems
Hi, On Montag 07 Februar 2005 19:51, Christian Mayer wrote: I've just read at the Heise Newsticker, that Trolltech is planning to release the next version of Qt for all systems (including M$ Windows) under it's dual license. = We can start to use it!! :) Great Mathias -- Mathias Fröhlich, email: [EMAIL PROTECTED] ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] segfault in SimGear code
On Fri, 11 Feb 2005 16:14:15 +0100 Ron Lange wrote: sorry, not the *commandline* below causes fg to break but similar .fgfsrc file... fgfs --airport=EDHI --aircraft=bo105 --enable-game-mode # Again, only a present .fgfsrc with similar content causes a segfault, the commandline let fg regulary start. Second hint: following message appeared twice: Failed to find runway 28R at airport EDHI --aircraft=bo105 --enable-game-mode Failed to find a good runway for EDHI --aircraft=bo105 --enable-game-mode Could you make sure that there is only one option per line in the .fgfsrc file ? It looks like the parser is trying to set the airport from the string EDHI --aircraft=bo105 --enable-game-mode... -- Jorge Van Hemelryck ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] segfault in SimGear code
Jorge Van Hemelryck wrote: Could you make sure that there is only one option per line in the .fgfsrc file ? It looks like the parser is trying to set the airport from the string EDHI --aircraft=bo105 --enable-game-mode... Aaah, your comment reminds me that the parser is unable to parse multiple options per line from the ~/.fgfsrc file - although I always had the impression that the parser simply ignores the following flags (it still would be nice if the parser could cope with multiple flags), Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] segfault in SimGear code
Hm...hmmm...since putting one flag per line in .fgfsrc wasn't satisfying (not starting from EDHI nor with the bo-105...) I put all flags in one row. Then everything goes as desired but the game mode...after adding enabel-game-mode the segfault appeared. Regards Ron Martin Spott schrieb: Jorge Van Hemelryck wrote: Could you make sure that there is only one option per line in the .fgfsrc file ? It looks like the parser is trying to set the airport from the string EDHI --aircraft=bo105 --enable-game-mode... Aaah, your comment reminds me that the parser is unable to parse multiple options per line from the ~/.fgfsrc file - although I always had the impression that the parser simply ignores the following flags (it still would be nice if the parser could cope with multiple flags), Martin. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
