RE: [Flightgear-devel] Citation pitch down divergence. Fixed?
Josh Babcock Lee Elliott wrote: On Thursday 10 Nov 2005 20:20, Andy Ross wrote: After some prodding from Curt, I finally spent a few hours yesterday tracking down the pitch down discontinuity in the Citation. Well, I didn't find a discontinuity. I can now graph the lift curve from a Surface (a real one, part of the real aircraft, not an isolated test instance) and verify that it's valid and correct looking through the entire AoA regime. But I think I *did* find the problem: it seems that I, er, misdocumented the incidence and twist parameters in the YASim configuration. The README.yasim file states that these numbers are positive for positive AoA (i.e. a positive incidence on a wing generates extra lift, and a negative twist causes the wing tips to stall after the root). But the code was interpreting the number as a rotation about the YASim Y axis, which points out the left wing and therefore is positive *down*. Oops. The reason the citation exhibited this especially is just luck: the file lists an incidence of 3.0 (which is relatively high, and the inversion bug therefore puts the wing 3 degrees closer to a negative stall) the solver happens to generate a nose-down cruise configuration of about 1.5 degrees, and the elevator authority is actually quite high (which causes higher pitch rates under autopilot control). So the bottom line is that Curt was right: it *was* the negative AoA stall (probably the tail's, not the wing's) happening too soon. :) I'm a little leery of changing this in code this close to a release -- the risk of breaking working aircraft is too high. For the short term, this can be fixed in the Citation-II.xml file by simply negating the incidence and twist values on the wing. I did this and tried the autopilot in a maximum speed cruise at low level (which should produce the highest nose-down AoA) without any odd behavior. Curt, can you try that and see if it appears to fix the handling issues? Likewise, anyone with a YASim aircraft that makes use of incidence or twist values is encouraged to try the same modification and report any problems. We can go back after the release and fix the code and all the aircraft files. Andy I'll try to check the ones I've done over the weekend. The one that concerns me most is the B-52F. The wing incidence is set to 6 and the twist to -4 and I'm starting to wonder how it manages to fly at all. Nose down. The fuselage is about 5 deg down when in level flight. I got some good info on the B-52F from someone who flew around 3000 hrs in that model and around 6000 hrs total in all models, apart from the A/B, and it was flying to within around 10 kts or so of what it should have been doing and was climbing at about the right rate. The negative incidence issue might also explain some odd values I was forced to put into the B29 config to make it fly well. I'll try an updated version later. Vivian ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FlightGear v0.0.9-pre3
Curtis L. Olson wrote: Just a quick announcement that I rolled up v0.9.9-pre3 tonight. I had screwed up and missed a file in the base package, and then some other changes got snuck into simgear/flightgear so I figured I might as well roll out another try. There's one thing I really like to see solved preferably before 0.9.9 (but it is a must for 1.0) and that's the sun/moon azimuth calculation code to be replaced. Erik ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FlightGear v0.0.9-pre3
On Fri, 2005-11-11 at 09:09, Erik Hofman wrote: Curtis L. Olson wrote: Just a quick announcement that I rolled up v0.9.9-pre3 tonight. I had screwed up and missed a file in the base package, and then some other changes got snuck into simgear/flightgear so I figured I might as well roll out another try. Hot damn! I haven't even got pre2 to run yet! Curt: if you've not done it yourself yet, the file data/Huds/Instruments/Default/runwayinstr.xml has duff permissions. There's one thing I really like to see solved preferably before 0.9.9 (but it is a must for 1.0) and that's the sun/moon azimuth calculation code to be replaced. That's certainly not getting in before 0.9.9! Turns out to be wy more tricky than it looked. It would seem that the entire handling of sun/moon azimuth/altitude as it's done now in flightgear needs replacing, with the alt/az calculations themselves done in Simgear. Everything else to do with the ephemeris happens in Simgear. To some extent, I'd argue that the whole ephemeris thing needs splitting out from Simgear into Ephemlib or something. After all, there are quite a few planetarium programs out there, each with its own unique ephemeris calculations. It would make sense to try and draw them together. There's little incentive for anyone writing an astronomical program to want to use Simgear for the ephemeris calculations because it comes with so much flightsim-related baggage. But that's for another day, another year. Steve ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] Joystick issues with throttleAxis()
[mailto:[EMAIL PROTECTED] On Behalf Of Ralf Gerlich snip I was just thinking of a more general way of solving the calibration issues than putting it into the configuration files. Regards, Ralf snip I have used systems (PS, PS2, the driver for my Saitek joystick under Windows) which appear to monitor the highest and lowest values that have been seen from a given axis, and assume that these are the extremes of the axis. Obviously when you first start it up, everything is very jittery, but you just need to move all the axes to each extreme and the calibration is set. In fact the PS/PS2 instructions say to move both analogue sticks in circles before using them, I guess this is to effect the calibration. Would it be possible to use this approach for FG? Richard This e-mail has been scanned for Bede Scientific Instruments for all viruses by Star Internet. The service is powered by MessageLabs. For more information on a proactive anti-virus service working around the clock, around the globe, visit: http://www.star.net.uk ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Which aircraft to include in v0.9.9?
On Friday 11 November 2005 01:43, Georg Vollnhals wrote: There was a review/test of FlightGear in linux user, November 2005, a very popular German linux magazin. Although they gave FlightGear 4 full pages, scenery on their cover CD and a lot of very usable hints aimed to flightsim beginners they complained about missing panels, missing instruments, missing Transponder (and a lot of other things like bad flightmodel ((due to missing stall characteristics)), missing structural damage, missing red and white-blackout, missing higher-level ATC, missing colleason detection ((they might have proved it with the ... objects)). Their last recommendation was not what we would like to see and we could say simply ignore it but a *lot* of linux user are reading this magazin and potentially flightsim interested people get the wrong impression by this review. :-( Here is the online version of this review: http://www.linux-user.de/ausgabe/2005/11/070-flightgear/ Best Regards, Oliver C. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Joystick issues with throttleAxis()
Richard Bytheway wrote: I have used systems (PS, PS2, the driver for my Saitek joystick under Windows) which appear to monitor the highest and lowest values that have been seen from a given axis, and assume that these are the extremes of the axis. Obviously when you first start it up, everything is very jittery, but you just need to move all the axes to each extreme and the calibration is set. In fact the PS/PS2 instructions say to move both analogue sticks in circles before using them, I guess this is to effect the calibration. Would it be possible to use this approach for FG? One could argue that moving all controls is an essential part of the pre-flight checks, so why not using that for calibration? Just makes the sim even more realistic ;) Nine ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Which aircraft to include in v0.9.9?
Oliver, Thank you for finding this online, I was very interested in reading it when Georg mentioned it (thanks to Georg also)! Here is the online version of this review: http://www.linux-user.de/ausgabe/2005/11/070-flightgear/ Best Regards, Oliver C. If someone needs translation into another language, you might try to translate the web page using google translation. http:// www.google.com/language_tools?hl=en The english language version is here: http://translate.google.com/translate?u=http%3A%2F%2Fwww.linux- user.de%2Fausgabe%2F2005%2F11%2F070-flightgear%2Flangpair=de% 7Cenhl=ensafe=offie=UTF-8oe=UTF-8prev=%2Flanguage_tools Best regards, Ima ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FlightGear v0.0.9-pre3
Steve Hosgood wrote: That's certainly not getting in before 0.9.9! Turns out to be wy more tricky than it looked. It would seem that the entire handling of sun/moon azimuth/altitude as it's done now in flightgear needs replacing, with the alt/az calculations themselves done in Simgear. Ok, now I tried the brute force method, eliminate every function which isn't really needed or which is supplied by SimGear already. I got a version that doesn't use any of the offending code with one small glitch; the azimuth is offset by 90 degrees. Erik ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Which aircraft to include in v0.9.9?
Ima Sudonim wrote: http://translate.google.com/translate?u=http%3A%2F%2Fwww.linux- user.de%2Fausgabe%2F2005%2F11%2F070-flightgear%2Flangpair=de% 7Cenhl=ensafe=offie=UTF-8oe=UTF-8prev=%2Flanguage_tools Oh yeah: flies are still an expensive pleasure :-) 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] FlightGear v0.0.9-pre3 xglobe licence issue
2005/11/11, Erik Hofman [EMAIL PROTECTED]: There's one thing I really like to see solved preferably before 0.9.9 (but it is a must for 1.0) and that's the sun/moon azimuth calculation code to be replaced. If you are talking about code from xglobe ( src/Time/sunpos.cxx, moonpos.cxx) , which licence is quite problematic, I hope it would be solved as soon as possible. This licence issue causes that FG is not included in box SuSE Linux. If fixed, it can be distributed within next SuSE release. Is it a problem to substitute the code with this http://home.cs.tum.edu/~roalter/libAstronomy/ ? Regards Ladislav Michnovic. Erik ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FlightGear v0.0.9-pre3
Steve Hosgood wrote: Curt: if you've not done it yourself yet, the file data/Huds/Instruments/Default/runwayinstr.xml has duff permissions. The following files probably *shouldn't* be there: Aircraft/A-10/.#A-10cl-set.xml.1.6 Aircraft/c172/Models/.#c172p.ac.1.1 Aircraft/c172/Panels/.#default.xml.1.3 Aircraft/c172/Panels/.#c172-panel.xml.1.8 Aircraft/c172/Panels/.#c172-panel.xml.1.4 Models/Trees/.#deciduous-tree.ac.1.3 Scenery/Terrain/w130n30/w123n37/.#KSFO.btg.gz.1.2 -- Jon Stockill [EMAIL PROTECTED] ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] plib update: gui themes pink input fields, PUSTRING_MAX
Those using the alternative dark GUI theme may want to update plib/cvs. All packagers should IMHO do that in any case. This fixes two problems: - The maximum length of entries in the property viewer was changed from 80 to 256. The old value affected a few longer entries, like the METAR string. - The combobox and selectbox input field color can be changed, which makes them Yeukky Yellow[TM] in the alternative gui style, rather than Yeukky Pink. Not in yesterday's update, but another reason to update, especially for creators of binary 0.9.9 packages. This was added after the last stable plib release 0.8.4: - bitmap fonts (alternative gui style) don't disappear if their reference point is moved out of the view (x 0). There have no problems been reported for plib cvs/head. m. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Which aircraft to include in v0.9.9?
Martin Spott wrote: Ima Sudonim wrote: http://translate.google.com/translate?u=http%3A%2F%2Fwww.linux- user.de%2Fausgabe%2F2005%2F11%2F070-flightgear%2Flangpair=de% 7Cenhl=ensafe=offie=UTF-8oe=UTF-8prev=%2Flanguage_tools Oh yeah: flies are still an expensive pleasure :-) Martin. Damn right. Do you know how much money it costs to upgrade a fly from annoying to pleasurable? A lot, let me tell you! Josh ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Which aircraft to include in v0.9.9?
Ima Sudonim wrote: http://translate.google.com/translate?u=http%3A%2F%2Fwww.linux- user.de%2Fausgabe%2F2005%2F11%2F070-flightgear%2Flangpair=de% 7Cenhl=ensafe=offie=UTF-8oe=UTF-8prev=%2Flanguage_tools Oh yeah: flies are still an expensive pleasure :-) Martin. Martin, I agree, flies are still and expensive pleasure.. but delicious! 8-) I also liked the fact that google can't seem to translate Flugsimulationen, which as a non-German speaker, I can only assume means flight simulation or nuclear reactor, one of the two! grin Isn't machine translation wonderful? BabbleFish and Systran (used by Mac OS X Sherlock) is similar to google from examples I've seen. ImTranslator.com isn't too bad, but it's only free for less than 1000 words. 8-( I have a friend that used to send things to my wife and me translated from English using some online translation tool into the language we speak at home. Unfortunately, we usually couldn't understand his translations, until he actually explained what he was trying to say. But english is an ESPECIALLY ambiguous language, and machine translation (MT) gender, case endings and noun phrase/verb agreement were almost never right even on the translations that were at least semantically similar. Compared to what MT was just a few years ago, they didn't seem to do a bad job in most parts. But then again, I don't speak German! 8-) Best regards, Ima Sorry for the broken link, try: http://translate.google.com/translate?u=http://www.linux-user.de/ ausgabe/2005/11/070-flightgear/langpair=de% enhl=ensafe=offie=UTF-8oe=UTF-8prev=%2Flanguage_tools if my email program doesn't mess with it! I. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FlightGear v0.0.9-pre3 xglobe licence issue
Ladislav Michnovic( wrote: 2005/11/11, Erik Hofman [EMAIL PROTECTED]: There's one thing I really like to see solved preferably before 0.9.9 (but it is a must for 1.0) and that's the sun/moon azimuth calculation code to be replaced. If you are talking about code from xglobe ( src/Time/sunpos.cxx, moonpos.cxx) , which licence is quite problematic, I hope it would be solved as soon as possible. Yes, that's the code. I now have a fully working version without any of the affected code, just a routine which was written by Curtis anyhow. How should we proceed at this point; add it prior to 0.9.9, or add it for 1.0 and provide a patch for 0.9.9? Erik ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Which aircraft to include in v0.9.9?
Josh Babcock wrote: Martin Spott wrote: Oh yeah: flies are still an expensive pleasure :-) Damn right. Do you know how much money it costs to upgrade a fly from annoying to pleasurable? Yes, I do, but my system is not that expensive. You need a money purse and good visual judgement That's much more fun than a simple fly flap :-) 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
Re: [Flightgear-devel] plib update: gui themes pink input fields,
Melchior FRANZ wrote: Not in yesterday's update, but another reason to update, especially for creators of binary 0.9.9 packages. This was added after the last stable plib release 0.8.4: This is not the only reason why it makes sense to have a new PLIB release. FreeBSD portability fixes for example were ignored for the 1.8.4 and, as Steve Baker wrote a day after the release: Once we've gotten the thing to the point where it's basically releasable, doing a new version is a 10 minute job - and version numbers are a very cheap commodity. Who's going to push him to a 1.8.5 release !? ;-) 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: FlightGear v0.0.9-pre3 xglobe licence issue
* Erik Hofman -- Friday 11 November 2005 14:07: How should we proceed at this point; add it prior to 0.9.9, or add it for 1.0 and provide a patch for 0.9.9? I'm strongly in favor of 0.9.9. If it takes us as long to get 1.0.0 out as it took us for 0.9.9, then there will be several releases of Linux distributions during its lifetime. Risking that fgfs won't be included in any of these releases is not a good idea. (Similar problem on BSD?) Also getting the label unfree for a whole year isn't exactly desirable. If download statistics on the fgfs homepage show many more Windows downloads than Linux, then this is probably because Linux distribution do usually come with fgfs already. Don't give this up lightly. m. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: FlightGear v0.0.9-pre3 xglobe licence issue
Melchior FRANZ wrote: I'm strongly in favor of 0.9.9. If it takes us as long to get 1.0.0 out as it took us for 0.9.9, then there will be several releases of Linux distributions during its lifetime. Risking that fgfs won't be included in any of these releases is not a good idea. (Similar problem on BSD?) Also getting the label unfree for a whole year isn't exactly desirable. This is the reason why I proposed to release a patch: http://www.a1.nl/~ehofman/fgfs/download/sunpos.diff Distributors can decide to patch FlightGear or not when including it in their distribution. Erik ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FlightGear v0.0.9-pre3 xglobe licence issue
On Fri, 2005-11-11 at 13:07, Erik Hofman wrote: Ladislav Michnovic( wrote: 2005/11/11, Erik Hofman [EMAIL PROTECTED]: There's one thing I really like to see solved preferably before 0.9.9 (but it is a must for 1.0) and that's the sun/moon azimuth calculation code to be replaced. If you are talking about code from xglobe ( src/Time/sunpos.cxx, moonpos.cxx) , which licence is quite problematic, I hope it would be solved as soon as possible. Yes, that's the code. I now have a fully working version without any of the affected code, just a routine which was written by Curtis anyhow. Well, Erik, you've done *far* better than I did in less time. I got lost in the mass of 3D vector stuff that was working out how to light the scene and shift the skyglobe based on knowledge (from Xearth) of what point on earth had the sun directly overhead! I got as far as replacing the Xearth stuff with a simple get the sun's alt and azim for a given place on earth routine, but couldn't untangle the rest. I shall go hang my head in shame somewhere quiet Steve ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FlightGear v0.0.9-pre3
On Fri, 2005-11-11 at 12:29, Jon Stockill wrote: Steve Hosgood wrote: Curt: if you've not done it yourself yet, the file data/Huds/Instruments/Default/runwayinstr.xml has duff permissions. The following files probably *shouldn't* be there: And the following file probably should (considering that otherwise you get a complaint message on the screen when using the default aircraft): data/Aircraft/c172r/Models/c172-dpm.ac Steve. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FlightGear v0.0.9-pre3 xglobe licence issue
Steve Hosgood wrote: I shall go hang my head in shame somewhere quiet There's no reason for that, I didn't manage to get around it at first either. I think I have a lucky day today to discover how simple it could be done. Let me emphasize that I really appreciate it that you took the time to look after it. Erik ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FlightGear v0.9.9-pre2
On Thu, 2005-11-10 at 19:05, Dave Culp wrote: Aside from the already mentioned glitch about the missing cloudlayers.xml file, I was able to build 0.9.9-pre2 without any problems on my linux box. I just moved on to 0.9.9.pre3 No (real) problems now. Thanks to all who looked at my 'strace' listing. Steve ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FlightGear v0.0.9-pre3
Steve Hosgood wrote: And the following file probably should (considering that otherwise you get a complaint message on the screen when using the default aircraft): data/Aircraft/c172r/Models/c172-dpm.ac I've fixed this in the code to use the default included c172p instead. Erik ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FlightGear v0.0.9-pre3 xglobe licence issue
Erik Hofman wrote: Yes, that's the code. I now have a fully working version without any of the affected code, just a routine which was written by Curtis anyhow. How should we proceed at this point; add it prior to 0.9.9, or add it for 1.0 and provide a patch for 0.9.9? Erik, If you could run the clock forward a year or two or five or 10 and verify that the new code matches the results of the existing code within acceptable tolerences, then I think I'd be ok with sneaking it into v0.9.9 Curt. -- Curtis Olsonhttp://www.flightgear.org/~curt HumanFIRST Program http://www.humanfirst.umn.edu/ FlightGear Project http://www.flightgear.org Unique text:2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Fedora Core RPMs for 0.9.9-pre3
If anyone wants to test 0.9.9-pre3 on Fedora Core 2,3 or 4 but can't compile it for themselves, please help yourselves to my RPMs: ftp://tallyho.bc.nu/pub/steve/flightgear/0.9.9-pre3/RPMS/i386/FlightGear-0.9.9.pre3-0.FC.i386.rpm ftp://tallyho.bc.nu/pub/steve/flightgear/0.9.9-pre3/RPMS/i386/openal-20050209-0.FC2.i386.rpm Ignore the 'FC2' suffix on the openal package: it should be fine for FC2 onwards. You don't need the 'devel' RPMs unless you plan building the SRPMS for flightgear. If you do, they are in the directory: ftp://tallyho.bc.nu/pub/steve/flightgear/0.9.9-pre3/SRPMS/ (of course). Scenery RPMs (for the UK, Ireland and Faroe Islands) coming soon using the scheme I used for 0.9.8. Not to everyone's taste I know, but convenient if you like keeping your software under RPM's control. Steve. PS: If pre4 isn't coming out tomorrow morning :-), could someone mirror these RPMs somewhere please. They're currently hosted on rather a puny machine on a slow WAN. Thanks in advance. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: plib update: gui themes pink input fields, PUSTRING_MAX
* Melchior FRANZ -- Friday 11 November 2005 13:38: There have no problems been reported for plib cvs/head. I take that back. There was also some network code committed to the net/ directory that crashes fgfs. I assume that this will be reverted very soon. :-( m. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Possible bug in yasim (not sure though?)
Hi All, I have compiled and installed pre3 and noticed that I was not able to load the b1900d (my preferred plane), as FlightGear would load until the terrian appears and the splash screen starts to dissolve. At this point, flightgear is in a loop with some high pitched beeps. (That would normall stop). Loaded the beech99.. Same result... I asked Masser to check there... The Harrier loads correctly. I tried the harrier and was greeted with the harrier sitting on the runway. I tried running flightgear within strace and but that didn't reveal anything particularly interesting or out of the ordinary. Apart from a lot of lines like the following. (Spaces removed for readability.) read(5, 0x7f8ee290, 32) = -1 EAGAIN (Resource temporarily unavailable) All the above external models would load when choosing another fdm such as ufo or magic carpet. Any advice of what I could do next as I have ran out of debugging ideas? System: AMD64 3200+ 1 GB Memory GeForce 6600GT w/ 128MB George Patterson ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: FlightGear v0.0.9-pre3 xglobe licence issue
2005/11/11, Erik Hofman [EMAIL PROTECTED]: This is the reason why I proposed to release a patch: http://www.a1.nl/~ehofman/fgfs/download/sunpos.diff Great work. Thanks, but there is still moonpos.cxx which needs to be replaced. Erik I'd also prefer to have this new code in 0.9.9. Regards Ladislav. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FlightGear v0.0.9-pre3 xglobe licence issue
Curtis L. Olson wrote: If you could run the clock forward a year or two or five or 10 and verify that the new code matches the results of the existing code within acceptable tolerences, then I think I'd be ok with sneaking it into v0.9.9 Both 1970 and 2025 seem to work properly. Erik ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: FlightGear v0.0.9-pre3 xglobe licence issue
Ladislav Michnovič wrote: 2005/11/11, Erik Hofman [EMAIL PROTECTED]: This is the reason why I proposed to release a patch: http://www.a1.nl/~ehofman/fgfs/download/sunpos.diff Great work. Thanks, but there is still moonpos.cxx which needs to be replaced. I've removed moonpos.[ch]xx for this release. The only disadvantage is that the moon doesn't color yellow when near the horizon. It's hardly noticeable but it will be added for 1.0 (with updated GPL compatible code). Erik ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] 0.9.9 scenery?
The main fgfs website only lists scenery for 0.9.8 Is world scenery for 0.9.9 waiting for a stable, offical 0.9.9 release first? Steve ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] OT: A380 arrived in EDHI (Hamburg-Finkenwerder)
Hi everybody! Last tuesday, the A380 serial number 2 (F-WXXL) came to the airbus site in Hamburg to get a new painting and the interior. They will also do the evacuation test and some others here. This is the first A380 that came to Hamburg for a full-stop after a short fly-by visit some weeks ago. Once they start production and delivery of the A380, there will be a couple of landings a week here in Hamburg, before they get delivered to the airlines. It is a very nice place to spot the aircrafts there. The airport is located close to the river Elbe and for about half of the runway a dike protecting against flooding from high water in the Elbe runs parallel to the runway giving you a 7m (20ft) elevation to the runway surface. You can stand so close, one can almost touch the wing-tips passing in front of you. An aerial foto of EDHI is here http://www.eddh.de/info/landeinfo-ergebnisb.php?ueicao=EDHI but it is a few years old. In the meantime, the bay located in the center of the picture was filled and there are hangars for the A380 production now and the runway has been extended to the lower right corner of the picture, almost touching the water. I took some fotos of the A380 landing on tuesday and put them here http://www.t3r.de/fg/a380/ I also put 2 movies there for those with a fast internet-link, they are 37MB and 60MB. Hope you like this little story and the pics. Cheers, Torsten ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FlightGear Review (was: Which aircraft to include in v0.9.9?)
If someone needs translation into another language, you might try to translate the web page using google translation. http:// www.google.com/language_tools?hl=en The english language version is here: http://translate.google.com/translate?u=http%3A%2F%2Fwww.linux- user.de%2Fausgabe%2F2005%2F11%2F070-flightgear%2Flangpair=de% 7Cenhl=ensafe=offie=UTF-8oe=UTF-8prev=%2Flanguage_tools Google somehow only translated the first part into a very crude translation. So here is a better one (hand crafted ;-), other German speakers can probably correct me if I am wrong somewhere): Flying With FlightGear High Above -- UFO's over San Franscisco? With the free flight simulator FlightGear you leave this earth -- if needed in an UFO. Validate your free ticket here. Kristian Kißling, Jörg Luther --- README This article instructs you on the usage of the free flight simulator FlightGear and highlights its strong and weak points compared to its commercial competitors. Despite the so called low fare airlines, flying is an expensive hobby. This is even more true for piloting a plane yourself. A (hobby [sic!]) pilots training costs thousands of Euros, a visit in a professional full flight simulator comes at 200 to 300 Euro. No surprise, a lot of flight enthusiasts turn their PC into a cockpit: But even for flight sims for your own living room you have to spend 20 to 30 Euro -- extensions like additional models or detailed scenery excluded. This sums to a nice amount over time. On the other hand you can get the free flight simulator FlightGear platform independent and at no cost (Figure 1). Technically not in the same league like current commercial competitors, it is steadily developed further and with lots of features seems to be close to reality. FIGURE 1 ((1)) A Cessna passing the Golden Gate Bridge of San Francisco in the free flight simulator Flightgear. Check-in A slightly outdated version of FlightGear is installed for Suse via Yast and via Apt for Debian. For the newest release you have to compile the source code yourself [1]. For Mandrake 10.2, Fedora Core 3 and the newest version 5.10 of Ubuntu packets exist for the current release 0.9.8 of FlightGear. The packets may be found here [2]. To install FlightGear, you will need a 3D driver for your graphics card, since you will surely spare the bucking (TF not sure it's the right translation) without it. Install FlightGear via the respective packet manager. The console plays an important role: unlike other flight simulators you define parameters of the program before the start. With different options you determine for example the start position, the type of aircraft or the local time at the departure location. A typical start line is: fgfs --enable-fullscreen --aircraft=ufo --airport-id=KJFK --start-date-lat=2005:09:09:12:00:00 --enable-auto-coordination Now have a look to the single options: --enable-fullscreen turns on the fullscreen mode, for --aircraft you choose the UFO, departure aerodrome is John-F.-Kennedy airport (JFK) near New York. --- UFO: One of the less realistic aircraft in FlightGear. The UFO is fast, never crashes and provides a handy way to explore the scenery. Every airport worldwide possesses an ICAO code, which you can query at this website [3]. ICAO: ICAO stands for International Civil Aviation Organisation, which assigns airport codes to international airports. Your first flight does not start at JFK though: FlightGear by default only starts in the vicinity of San Franscisco. Other regions of the world can be downloaded from the FlightGear Website [4]: How to install such addons you can read in the box Extending FlightGear. = Extending FlightGear The FlightGear world is divided into 10x10 degrees quadrants. In the basic version you only get one such tile around Los Angeles, the rest of the world consists of water. With the right extension files [4], you get scenery for the rest of the world too. FIGURE 2 ((2)) If you like to fly to a new airport or region, first you must download and install the right scenery tiles. The download of so called scenery tiles causes tremendous download volumes: A single tile comes at around 80MB; flightgear.org provides the whole world scenery on 3 DVD for purchase. We have put the Middle European region onto the attached CD. The region consists of the four tiles from 0°E 50°N (e000n50.tgz) to 10°E 40°N (e010n40.tgz). Not only Germany but also Benelux, Denmark, the south of Scandinavia, large parts of France and Italy as well as the Balcan area come into your reach. To install the scenery, copy the archives from the CD depending on your distribution into the Scenery or Scenery/Terrain subdirectories and unpack with the command tar -xvzf e0*. In a similar manner proceed with other downloaded FlightGear scenery
Re: [Flightgear-devel] 0.9.9 scenery?
Steve Hosgood wrote: The main fgfs website only lists scenery for 0.9.8 Is world scenery for 0.9.9 waiting for a stable, offical 0.9.9 release first? There is a current world scenery rebuild in progress. We are currently hung up on a data processing glitch that is being worked on. The scenery and the source release can and will happen independently. Rebuilding the world (and trying to fix bugs and improve the result at the same time) is a massive undertaking. The new world will be based on SRTM v2 data supplimented with USGS DEM data to fill in the voids where possible, i.e. in the usa. The grand canyon and rhode island will be much better. These places glitched out in SRTM and portions never got properly mapped. I also did a complete overhaul of the airport surface generation scheme and tossed the old nurbs approach because the nurbs++ code is not maintained and is increasingly difficult to compile on modern systems. We are now trying to process the shapefile conversion of the vmap data. If we can crack this, then that opens the doors to future user fixes and contributions of land cover/land use data, lakes, rivers, roads, etc. I've been posting very brief notes and updates on the scenery rebuild to my personal web page (along with a variety of other stuff that probably isn't of great concern to most people in FlightGear land.) http://www.flightgear.org/~curt/ Curt. -- Curtis Olsonhttp://www.flightgear.org/~curt HumanFIRST Program http://www.humanfirst.umn.edu/ FlightGear Project http://www.flightgear.org Unique text:2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] 0.9.9 scenery?
Curtis L. Olson wrote: There is a current world scenery rebuild in progress. We are currently hung up on a data processing glitch that is being worked on. The scenery and the source release can and will happen independently. Rebuilding the world (and trying to fix bugs and improve the result at the same time) is a massive undertaking. The new world will be based on [... data source ...] and hopefully on the scenery objects that are stored in Jon's and my FlightGear Scenery Objects Database located at: http://fgfsdb.stockill.org/ I just finished removing the remaining duplicates at San Francisco downtown - at least I think I did so. Tomorrow, when the next export is done, will prove if I did it right :-) I hope that I'll find the time this weekend to have a further check if I still forgot some, 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] OT: A380 arrived in EDHI (Hamburg-Finkenwerder)
Torsten Dreyer wrote: An aerial foto of EDHI is here http://www.eddh.de/info/landeinfo-ergebnisb.php?ueicao=EDHI would be nice to have the current version of EDHI included in our airports database :-) 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] Strange colors in spash screen
I wish it was that simple. But it does this no matter what aircraft I select. The only change is in the colors really.Any other mac users with this problem?On 11/11/05, Lee Elliott [EMAIL PROTECTED] wrote: On Thursday 10 Nov 2005 18:01, Arthur Wiebe wrote: http://artooro.spymac.com/pub/fg_spash_screen.png This is a screenshot of some very interesting colors I get in the splash screen when launching FlightGear 0.9.9-pre2. Any idea what could be wrong? It all works fine once everything has been initiated. -- Arthur/ - http://sourceforge.net/users/artooro/ - http://artooro.blogspot.comThat looks like a corrupted splash screen image.Does it happen with all the aircraft you've tried?Some aircraft have their own splash image but those that don'tget one of the default splash images.LeeE___ Flightgear-devel mailing listFlightgear-devel@flightgear.orghttp://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d-- Arthur/- http://sourceforge.net/users/artooro/- http://artooro.blogspot.com ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] try ... catch ... throw (up)
I've been trying to use exception handling in a particularly appropriate place
in JSBSim,
but am having little success, and it's got me confused.
I have a section where I am reading in some data. If it is inappropriate, I
need to let
the user know and exit.
Here's what I'm doing:
In the Table class:
In FGTable constructor:
if (operation_types.find(parent_type) == string::npos) {
internal = true;
} else {
throw(string(An internal table cannot be ...));
}
Now, this seems to work OK - I throw an exception if a situation occurs that is
invalid.
Here's where the above code is originally called from:
In FGFunction constructor:
try {
Parameters.push_back(new FGTable(PropertyManager, element));
} catch (...) {throw;}
This is supposed to pass the exception on up the chain to here the code that
calls the
above:
In FGAerodynamics::Load():
try {
variables.push_back( new FGFunction(PropertyManager, function_element) );
} catch(string msg) {
return false;
}
Execution seems to get to the throw in FGFunction and dies. Execution never
gets to the
handler in FGAerodynamics. I get a segfault.
I'm probably missing something fundamental here. Anyone have any suggestions?
Jon
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] mi_cmd_stack_list_frames: Not enough frames in stack.
Now when it comes to debugging stuff like this I'm a newbie.When I select the default c172p aircraft everything works fine. But if I select say the f16 or A-10 then fgfs crashes.Here's the output from gdb. Loading program into debugger… Program loaded.sharedlibrary apply-load-rules all Attaching to program: `/Users/arthur/Projects/FlightGearOSX/build/FlightGear/FlightGear.app/Contents/MacOS/FlightGear', process 5516. mi_cmd_stack_list_frames: Not enough frames in stack.mi_cmd_stack_list_frames: Not enough frames in stack. I never tested pre1 or pre2 with different aircraft so don't know if I got the error then too.-- Arthur/- http://sourceforge.net/users/artooro/ - http://artooro.blogspot.com ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] 0.9.9 scenery?
On Fri, 2005-11-11 at 15:14, Curtis L. Olson wrote: There is a current world scenery rebuild in progress. We are currently hung up on a data processing glitch that is being worked on. The scenery and the source release can and will happen independently. I'll just wait then. Thanks Steve ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Ear Candy: intro.mp3
Hi, There's a file in the base package /data/Sounds/intro.mp3 The filename suggests this is introduction music presumably played during the FG boot. I have CVS FG compiled with Cygwin for Win32 (using Norman Vine's pre-compiled OpenAL libraries in case OpenAL is suspicious here). Windows Media Player can play the mp3 but I don't hear this in FG. My command line is simple: /fg-cvs/bin/fgfs.exe --fg-root=/fg-cvs/data In particular I do *not* use --disable-intro-music or --disable-sound. I've also tried: /fg-cvs/bin/fgfs.exe --fg-root=/fg-cvs/data --enable-intro-music --enable-sound (grep'd from --help --verbose) Other sounds during run-time (engine etc.) are all OK. Kevin. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] mi_cmd_stack_list_frames: Not enough frames in stack.
Arthur Wiebe wrote: Now when it comes to debugging stuff like this I'm a newbie. When I select the default c172p aircraft everything works fine. But if I select say the f16 or A-10 then fgfs crashes. Here's the output from gdb. http://www.codecomments.com/archive242-2004-4-170396.html The problem is gdb. It is the debugger itself that cause the error when stepping instruction. Erik ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Ear Candy: intro.mp3
Kevin Jones wrote: Hi, There's a file in the base package /data/Sounds/intro.mp3 The filename suggests this is introduction music presumably played during the FG boot. I have CVS FG compiled with Cygwin for Win32 (using Norman Vine's pre-compiled OpenAL libraries in case OpenAL is suspicious here). Windows Media Player can play the mp3 but I don't hear this in FG. FlightGear doesn't use OpenAL for MP3 playback. In fact, it isn't even supported. Erik ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] mi_cmd_stack_list_frames: Not enough frames in stack.
OK,But then why when I select the A-10 or f16 fgfs crashes? But when selecting the c172p and j3cub there is no problem?I'll do a bit more testing.It almost seems to be a problem with the actual aircraft. On 11/11/05, Erik Hofman [EMAIL PROTECTED] wrote: Arthur Wiebe wrote: Now when it comes to debugging stuff like this I'm a newbie. When I select the default c172p aircraft everything works fine. But if I select say the f16 or A-10 then fgfs crashes. Here's the output from gdb.http://www.codecomments.com/archive242-2004-4-170396.html The problem is gdb. It is the debugger itself that cause the error when stepping instruction.Erik___Flightgear-devel mailing list Flightgear-devel@flightgear.orghttp://mail.flightgear.org/mailman/listinfo/flightgear-devel2f585eeea02e2c79d7b1d8c4963bae2d -- Arthur/- http://sourceforge.net/users/artooro/- http://artooro.blogspot.com ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] 0.9.9 scenery?
On Friday 11 November 2005 17:14, Curtis L. Olson wrote: The new world will be based on SRTM v2 data supplimented with USGS DEM data to fill in the voids where possible, i.e. in the usa. The grand canyon and rhode island will be much better. These places glitched out in SRTM and portions never got properly mapped. There is 100% void free SRTM data here : http://srtm.csi.cgiar.org/ Paul ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] mi_cmd_stack_list_frames: Not enough frames in stack.
Arthur Wiebe wrote: OK, But then why when I select the A-10 or f16 fgfs crashes? But when selecting the c172p and j3cub there is no problem? The only commonality between the A-10 and f-16 is the turbine sound file?? Erik ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] 0.9.9 scenery?
Paul Surgeon wrote: There is 100% void free SRTM data here : http://srtm.csi.cgiar.org/ As best as I can see from their site, they just interpolated through the voids. That generally works fine and is pretty much what we did for the current scenery, but when you are missing big chunks of things like the grand canyon or tops of moutains, then what? For the USA where we have an alternative data source, I filled in the voids from that data which is good for things like the grand canyon and rhode island that are missing huge chunk. It might bite me elsewhere, but I hope not too much. Outside the USA our algorithm still just interpolates through the holes. Regards, Curt. -- Curtis Olsonhttp://www.flightgear.org/~curt HumanFIRST Program http://www.humanfirst.umn.edu/ FlightGear Project http://www.flightgear.org Unique text:2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Ear Candy: intro.mp3
So can be this mp3 be removed or substitued with wav (ogg)? Regards Ladislav. 2005/11/11, Erik Hofman [EMAIL PROTECTED]: FlightGear doesn't use OpenAL for MP3 playback. In fact, it isn't even supported. Erik ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] 0.9.9 scenery?
Martin Spott wrote: I just finished removing the remaining duplicates at San Francisco downtown - at least I think I did so. Tomorrow, when the next export is done, will prove if I did it right :-) Jon kindly triggered a fresh export and I took the freedom to place the current set of base package objects on my FTP server. Unfortunately my FlightGear test machine refuses to run FlightGear this afternoon (it simply crashes after two minutes) so I'm unable to test this myself today. Please feel free to fetch the package from here: ftp://ftp.ihg.uni-duisburg.de/FlightGear/Devel/BaseObjects.tgz 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] Possible bug in yasim (not sure though?)
George Patterson wrote: I have compiled and installed pre3 and noticed that I was not able to load the b1900d Yeah, that was me. The patch yesterday for turn off the engines when out of fuel broke the solver for turbine aircraft. Fixed. That'll teach me to add features right before release. Apologies. Andy ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] 0.9.9 scenery?
Martin Spott wrote: Jon kindly triggered a fresh export and I took the freedom to place the current set of base package objects on my FTP server. Unfortunately my FlightGear test machine refuses to run FlightGear this afternoon (it simply crashes after two minutes) so I'm unable to test this myself today. I just realized that most buildings in SFO downtown are missing now, but I/we will manage to fix that soon. At least I made sure the duplicates are gone :-) 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] compiling Simgear...
Hi all ... Had some problems with latest CVS ... so I wiped out and downloaded simgear and flightgear again from CVS. I get an error now compiling Simgear . I cant cut and paste from the terminal but make stops at : [visual_enviro.o]Error 1 Has anyone run across this before? ... I get so much email I may have missed the solution if it was posted previously . Thanks . I'll send another update for the B1900D today hopefully , but I want to compile and test from the latest CVS files first. plus Im having a little trouble with a certain nasal file for the GPS , so still a lot of work to do . Havent figured out nasal's undefined symbol at line 1 error yet :) ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] V9.9 test run
I compiled 9.9 test version on my Thinkpad T42 (I'm on the road) and after loading the cloud file, it worked for the default Cessna. However, when I tried the Citation I got the following messages, and it would not take off. It also had a couple of the instruments on the left side o f the panel (clock and the one above it) that were largely obscured by gray lines. Couldn't do much else without a joystick, which is not where I am. Hope this helps somebody, Rex fgfs --aircraft=Citation-II Dent: ..Dent: EHAMDent: .opening file: /usr/local/share/FlightGear/data/Navaids/carrier_nav.dat /usr/local/share/FlightGear/data/Navaids/TACAN_freq.dat RenderTexture Error: Couldn't find a suitable pixel format. open /dev/[sound/]dsp: Device or resource busy Audio initialization failed! WARNING: ssgLoadAC: Failed to open '/usr/local/share/FlightGear/data/Aircraft/c172r/Models/c172-dpm.ac' for reading Reading xml electrical system model from /usr/local/share/FlightGear/data/Aircraft/beech99/beech99-electrical.xml Failed to load electrical system model: /usr/local/share/FlightGear/data/Aircraft/beech99/beech99-electrical.xml netAddress::set: Resource temporarily unavailable Initialising callsign using 'Aircraft/Citation/Models/Citation-II.xml' ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] 0.9.9 scenery?
On Friday 11 November 2005 18:40, Curtis L. Olson wrote: As best as I can see from their site, they just interpolated through the voids. That generally works fine and is pretty much what we did for the current scenery, but when you are missing big chunks of things like the grand canyon or tops of moutains, then what? For the USA where we have an alternative data source, I filled in the voids from that data which is good for things like the grand canyon and rhode island that are missing huge chunk. Isn't SRTM data version 2 allready corrected manually? That's what i thought, when i heard sth. about SRTM v2. Best Regards, Oliver C. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] mi_cmd_stack_list_frames: Not enough frames in stack.
I've compiled a list of all the aircraft included in fgfs-base 0.9.9pre3 that do and don't work:+737-.#A-10cl-A-10cl-A-10fl+bo105+c172p-2dpanel+c172p+c310-yasim+c310dpm-3d-c310-3d +c310-ifr+c310+c310u3a-jsbsim+c310u3a+Citation-||-f16-3d-f16-mlu-f16-f16at+hunter-2tanks+hunter+j3cub+p51d+pa28-161+ufo+wrightFlyer1903Those with a + work and those with the - do not. I wonder what .#A-10cl is doing in there as it's invisible for most people.On 11/11/05, Erik Hofman [EMAIL PROTECTED] wrote:Arthur Wiebe wrote: OK, But then why when I select the A-10 or f16 fgfs crashes? But when selecting the c172p and j3cub there is no problem?The only commonality between the A-10 and f-16 is the turbine sound file??Erik___Flightgear-devel mailing list Flightgear-devel@flightgear.orghttp://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d-- Arthur/- http://sourceforge.net/users/artooro/- http://artooro.blogspot.com ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] mi_cmd_stack_list_frames: Not enough frames in stack.
OK I found the problem. I hope.In A-10cl-set.xml I removed the following line: splash-textureAircraft/A-10/A-10-splash.rgb/splash-textureAnd it worked. So it seems something is broken in whatever loads these rgb files. The file does not look corrupted as it opens fine in QuickTime.On 11/11/05, Arthur Wiebe [EMAIL PROTECTED] wrote:I've compiled a list of all the aircraft included in fgfs-base 0.9.9pre3 that do and don't work: +737-.#A-10cl-A-10cl-A-10fl+bo105+c172p-2dpanel+c172p+c310-yasim+c310dpm-3d-c310-3d +c310-ifr+c310+c310u3a-jsbsim+c310u3a+Citation-||-f16-3d-f16-mlu-f16-f16at+hunter-2tanks+hunter+j3cub+p51d+pa28-161+ufo+wrightFlyer1903Those with a + work and those with the - do not. I wonder what .#A-10cl is doing in there as it's invisible for most people.On 11/11/05, Erik Hofman [EMAIL PROTECTED] wrote:Arthur Wiebe wrote: OK, But then why when I select the A-10 or f16 fgfs crashes? But when selecting the c172p and j3cub there is no problem?The only commonality between the A-10 and f-16 is the turbine sound file??Erik___Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d-- Arthur/- http://sourceforge.net/users/artooro/- http://artooro.blogspot.com -- Arthur/- http://sourceforge.net/users/artooro/- http://artooro.blogspot.com ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] compile error for pre3
Since Flightgear-0.9.9-pre2 compiled fine without any problems, I was surprised to see this: if g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src -I/usr/X11R6/include -I/usr/local/include -DPKGLIBDIR=\/usr/local/share/FlightGear\ -g -O2 -D_REENTRANT -MT fg_init.o -MD -MP -MF .deps/fg_init.Tpo -c -o fg_init.o fg_init.cxx; \ then mv -f .deps/fg_init.Tpo .deps/fg_init.Po; else rm -f .deps/fg_init.Tpo; exit 1; fi fg_init.cxx: In function `bool fgInitSubsystems()': fg_init.cxx:1581: error: `setRealtimeProperty' undeclared (first use this function) fg_init.cxx:1581: error: (Each undeclared identifier is reported only once for each function it appears in.) make[2]: *** [fg_init.o] Error 1 make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/usr/src/FlightGear-0.9.9-pre3/src' make: *** [all-recursive] Error 1 where is setRealtimeProperty get declared? Stewart ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] compile error for pre3
Stewart Andreason wrote: Since Flightgear-0.9.9-pre2 compiled fine without any problems, I was surprised to see this: fg_init.cxx:1581: error: `setRealtimeProperty' undeclared This is SimGear version skew. You need to use the properly matched version of SimGear, but are probably building against an older one still in your /usr/local. Andy ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] OT: A380 arrived in EDHI (Hamburg-Finkenwerder)
Torsten Dreyer schrieb: Hi everybody! Last tuesday, the A380 serial number 2 (F-WXXL) came to the airbus site in Hamburg to get a new painting and the interior. They will also do the .. An aerial foto of EDHI is here http://www.eddh.de/info/landeinfo-ergebnisb.php?ueicao=EDHI but it is a few years old. In the meantime, the bay located in the center of .. I took some fotos of the A380 landing on tuesday and put them here http://www.t3r.de/fg/a380/ I also put 2 movies there for those with a fast internet-link, they are 37MB and 60MB. Hope you like this little story and the pics. Cheers, Torsten ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d Hi Torsten, thank you for sharing this with us, very interesting! *Bremen* is very proud that the A380 made a low approach at the local airport to greet the employees of the local airbus facility where they constructed the A380 flaps (size of a little airliner wing!) and other wing-add-on stuff. I could only see some pictures in the local newspapers as I was very engaged in day-work and could not look out though the airport ist pretty nearby and I'll always have a look at the traffic when it is possible :-) Last November (2004) I shot some pics when we passed EDHI. The new terrain has already been built and most of the buildings, as I assume. I put 3 pics on my homepage, if you are interested how it looked from air: http://home.arcor.de/vollnhals-bremen/HHFinkenwerder/hamburg_finkenwerder.htm Regards Georg (EDDW) ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Which aircraft to include in v0.9.9?
On November 11, 2005 06:23 am, Martin Spott wrote: Ima Sudonim wrote: http://translate.google.com/translate?u=http%3A%2F%2Fwww.linux- user.de%2Fausgabe%2F2005%2F11%2F070-flightgear%2Flangpair=de% 7Cenhl=ensafe=offie=UTF-8oe=UTF-8prev=%2Flanguage_tools Oh yeah: flies are still an expensive pleasure :-) Martin. It is pretty enjoyable to kill them with elastic bands. Ampere ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] 0.9.9 scenery?
On Friday 11 November 2005 22:27, Oliver C. wrote: Isn't SRTM data version 2 allready corrected manually? That's what i thought, when i heard sth. about SRTM v2. Best Regards, Oliver C. Well yes SRTM version 2 has had some corrections made to it including flattening the areas covered by water but it's still FULL of voids. For some other flight sim scenery I use SRTM version 2 and fall back to the CGIAR when voids are encountered. So far so good. Of course the USA has complete coverage in NED1 (30m) which should rather be used in my opinion. 90 meter DEMs are pretty coarse. Regards Paul ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] [PATCH] Re: SEGV with ATIS
Figured out the problem with ATIS voice. It's in SimGear with the
code for OpenAL/Alut 1.1, whereby with in sample_openal.cxx,
alutCreateBufferFromFile() does not give us the raw sound data, and
ATCVoice depends on it, which leaves the data and the data size
uninitialized.
The patch used alutLoadMemoryFromFile() instead, pretty much the new
version of the old deprecated alutLoadWAVFile().
Also someone might know a better, more portable way of converting an
ALfloat to an ALsizei. I'm simply casting it at the moment.
Thanks.
Pigeon.
Index: simgear/sound/sample_openal.cxx
===
RCS file: /var/cvs/SimGear-0.3/source/simgear/sound/sample_openal.cxx,v
retrieving revision 1.19
diff -u -r1.19 sample_openal.cxx
--- simgear/sound/sample_openal.cxx 25 Oct 2005 18:05:23 - 1.19
+++ simgear/sound/sample_openal.cxx 11 Nov 2005 22:27:50 -
@@ -67,6 +67,7 @@
// constructor
SGSoundSample::SGSoundSample( const char *path, const char *file,
bool cleanup ) :
+size(0),
data(NULL),
buffer(0),
source(0),
@@ -77,6 +78,8 @@
loop(AL_FALSE),
playing(false)
{
+ALfloat freqf;
+
SGPath samplepath( path );
if ( strlen(file) ) {
samplepath.append( file );
@@ -105,11 +108,24 @@
// Load the sample file
#if defined(ALUT_API_MAJOR_VERSION) ALUT_API_MAJOR_VERSION = 1
- buffer = alutCreateBufferFromFile(samplepath.c_str());
- if (buffer == AL_NONE) {
- ALenum error = alutGetError ();
- print_openal_error(constructor (alutCreateBufferFromFile));
- throw sg_exception(Failed to load wav file: +string(alutGetErrorString
(error)));
+ data = alutLoadMemoryFromFile( samplepath.c_str(),
+ format, size, freqf );
+ if ( data == NULL ) {
+throw sg_exception(Failed to load wav file.);
+ }
+
+ freq = (ALsizei) freqf;
+
+ alBufferData( buffer, format, data, size, freq );
+ if ( print_openal_error(constructor (alBufferData)) ) {
+ free( data );
+ data = NULL;
+ throw sg_exception(Failed to buffer data.);
+ }
+
+ if ( cleanup ) {
+ free( data );
+ data = NULL;
}
#else
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] compile error for pre3
I _knew_ it was something simple... I guess one prerequisite at http://www.flightgear.org/Downloads/source.shtml needs to be updated. Thanks Andy Stewart Andreason wrote: Since Flightgear-0.9.9-pre2 compiled fine without any problems, I was surprised to see this: fg_init.cxx:1581: error: `setRealtimeProperty' undeclared This is SimGear version skew. You need to use the properly matched version of SimGear, but are probably building against an older one still in your /usr/local. Andy ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] 0.9.9 scenery?
Oliver C. wrote: On Friday 11 November 2005 18:40, Curtis L. Olson wrote: As best as I can see from their site, they just interpolated through the voids. That generally works fine and is pretty much what we did for the current scenery, but when you are missing big chunks of things like the grand canyon or tops of moutains, then what? For the USA where we have an alternative data source, I filled in the voids from that data which is good for things like the grand canyon and rhode island that are missing huge chunk. Isn't SRTM data version 2 allready corrected manually? That's what i thought, when i heard sth. about SRTM v2. SRTM still has all the voids as far as I know. They've done other corrections, but not void filling (as far as I know.) I can vouch for the fact that it still does have a lot of voids, although I can't say for sure if it's all the same ones or fewer or more. Curt. -- Curtis Olsonhttp://www.flightgear.org/~curt HumanFIRST Program http://www.humanfirst.umn.edu/ FlightGear Project http://www.flightgear.org Unique text:2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Problem report related to strange splash screens and crashes with certain aircraft
I think this report basically pins down two of my problems.First, where spash screens on startup showed up as strange color stipes. And second, where certain aircraft which define their own spash screen crash fgfs. I got this report when trying to load the c310 (pre3).Hopefully either one of you will find what's wrong or I'll look into it some more tomorrow.Date/Time: 2005-11-11 22:51:12.314 +OS Version: 10.4.3 (Build 8F46)Report Version: 3Command: fgfsPath: FlightGear.app/Contents/Resources/fgfsParent: FlightGear [271]Version: ??? (???)PID: 272Thread: 0Exception: EXC_BAD_ACCESS (0x0001) Codes: KERN_INVALID_ADDRESS (0x0001) at 0x01db7000Thread 0 Crashed:0 0x8a60 __memcpy + 704 (cpu_capabilities.h:189)1 libSystem.B.dylib 0x9001a878 fread + 152 2 libz.1.dylib 0x9108d1b0 gzread + 3643 fgfs 0x00104dfc SGTexture::ImageGetRow(SGTexture::_ImageRec*, unsigned char*, int, int) + 2484 fgfs 0x0010601c SGTexture::read_rgb_texture(char const*) + 860 5 fgfs 0x0001bce4 fgSplashInit(char const*) + 17646 fgfs 0x7430 fgMainInit(int, char**) + 13487 fgfs 0x3328 main + 1848 fgfs 0x2acc _start + 344 9 fgfs 0x2970 start + 60Thread 0 crashed with PPC Thread State 64: srr0: 0x8a60 srr1: 0x0200f030 vrsave: 0xff00 cr: 0x24000220 xer: 0x0004 lr: 0x9001a878 ctr: 0x0040 r0: 0x r1: 0xb690 r2: 0x r3: 0x01db7000 r4: 0x0354ec40 r5: 0x1000 r6: 0x0010 r7: 0x0020 r8: 0x0030 r9: 0x r10: 0x0060 r11: 0x0080 r12: 0x01db7000 r13: 0x r14: 0x r15: 0x r16: 0x r17: 0x r18: 0x r19: 0x r20: 0x r21: 0x r22: 0x r23: 0x r24: 0x00016bf0 r25: 0x0001 r26: 0x00016bf0 r27: 0x01db7000 r28: 0xa000e790 r29: 0x6bf0 r30: 0x1000 r31: 0x9001a7f0Binary Images Description: 0x1000 - 0x754fff fgfs /Users/arthur/Projects/FlightGearOSX/build/FlightGear/FlightGear.app/Contents/Resources/fgfs0x184 - 0x18b2fff com.apple.GeForce2MXGLDriver 1.4.16 (4.1.6) /System/Library/Extensions/GeForce2MXGLDriver.bundle/Contents/MacOS/GeForce2MXGLDriver 0x18ba000 - 0x18d3fff GLDriver /System/Library/Frameworks/OpenGL.framework/Versions/A/Resources/GLDriver.bundle/GLDriver0x18d9000 - 0x18f4fff GLRendererFloat /System/Library/Frameworks/OpenGL.framework/Versions/A/Resources/GLRendererFloat.bundle/GLRendererFloat 0x1c05000 - 0x1d14fff GLEngine /System/Library/Frameworks/OpenGL.framework/Resources/GLEngine.bundle/GLEngine0x8fe0 - 0x8fe54fff dyld 44.2 /usr/lib/dyld0x9000 - 0x901b3fff libSystem.B.dylib /usr/lib/libSystem.B.dylib 0x9020b000 - 0x9020 libmathCommon.A.dylib /usr/lib/system/libmathCommon.A.dylib0x90211000 - 0x90264fff com.apple.CoreText 1.0.1 (???) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/CoreText.framework/Versions/A/CoreText 0x90291000 - 0x90342fff ATS /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/ATS0x90371000 - 0x906aefff com.apple.CoreGraphics 1.256.27 (???) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/CoreGraphics.framework/Versions/A/CoreGraphics 0x9073a000 - 0x90813fff com.apple.CoreFoundation 6.4.4 (368.18) /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation0x9085c000 - 0x9085cfff com.apple.CoreServices 10.4 (???) /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices 0x9085e000 - 0x90960fff libicucore.A.dylib /usr/lib/libicucore.A.dylib0x909ba000 - 0x90a3efff libobjc.A.dylib /usr/lib/libobjc.A.dylib0x90a68000 - 0x90ad6fff com.apple.framework.IOKit 1.4 (???) /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit 0x90aed000 - 0x90af libauto.dylib /usr/lib/libauto.dylib0x90b06000 - 0x90dddfff com.apple.CoreServices.CarbonCore 671.2 /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore 0x90e43000 - 0x90ec3fff com.apple.CoreServices.OSServices 4.1 /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServices.framework/Versions/A/OSServices0x90f0d000 - 0x90f4efff com.apple.CFNetwork 10.4.3 (129.2) /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CFNetwork.framework/Versions/A/CFNetwork0x90f63000 - 0x90f7bfff com.apple.WebServices 1.1.2 (1.1.0) /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/WebServicesCore.framework/Versions/A/WebServicesCore 0x90f8b000 - 0x9100cfff com.apple.SearchKit 1.0.4 /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchKit.framework/Versions/A/SearchKit0x91052000 - 0x9107bfff
Re: [Flightgear-devel] LibGL error
I am also getting GLXUnsupportedPrivateRequest error. This is so darn annoying! I used to be able to get around this problem by migrating back to XFree, or failing that, start XServer under 16-bit depth. Now, I can't go with either option: Debian has moved onto Xorg, and SDL doesn't allow me to run OpenGL application under 16-bit depth. I am also using ATI card -- ATI 9200 SE to be precise. Ampere ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] diff for browser change for mac os x to use safari
With this change, FlightGear on Mac OS X launches the mac os x Safari browser instead of netscape (w/o this change, the browser won't launch without netscape installed, and netscape isn't one of the installed mac os x browsers). thank you Ima Index: FlightGear/src/Main/options.cxx === RCS file: /var/cvs/FlightGear-0.9/FlightGear/src/Main/options.cxx,v retrieving revision 1.73 diff -u -r1.73 options.cxx --- FlightGear/src/Main/options.cxx 12 Oct 2005 08:55:58 - 1.73 +++ FlightGear/src/Main/options.cxx 9 Nov 2005 01:53:53 - @@ -172,7 +172,11 @@ fgSetString(/sim/control-mode, joystick); fgSetBool(/sim/auto-coordination, false); #if !defined(WIN32) +#if defined (__APPLE__) +fgSetString(/sim/startup/browser-app, safari); +#else fgSetString(/sim/startup/browser-app, netscape); +#endif #else fgSetString(/sim/startup/browser-app, webrun.bat); #endif ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FlightGear Review (was: Which aircraft to include in v0.9.9?)
On Fri, 2005-11-11 at 16:13 +0100, Thomas Förster wrote: A slightly outdated version of FlightGear is installed for Suse via Yast and via Apt for Debian. For the newest release you have to compile the source code yourself [1]. For Mandrake 10.2, Fedora Core 3 and the newest version 5.10 of Ubuntu packets exist for the current release 0.9.8 of FlightGear. The packets may be found here [2]. Last sentence of this paragraph should be The packages may be found here [2]. -- George Patterson ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Citation pitch down divergence. Fixed?
On Friday 11 Nov 2005 02:47, Josh Babcock wrote: Lee Elliott wrote: On Thursday 10 Nov 2005 20:20, Andy Ross wrote: After some prodding from Curt, I finally spent a few hours yesterday tracking down the pitch down discontinuity in the Citation. Well, I didn't find a discontinuity. I can now graph the lift curve from a Surface (a real one, part of the real aircraft, not an isolated test instance) and verify that it's valid and correct looking through the entire AoA regime. But I think I *did* find the problem: it seems that I, er, misdocumented the incidence and twist parameters in the YASim configuration. The README.yasim file states that these numbers are positive for positive AoA (i.e. a positive incidence on a wing generates extra lift, and a negative twist causes the wing tips to stall after the root). But the code was interpreting the number as a rotation about the YASim Y axis, which points out the left wing and therefore is positive *down*. Oops. The reason the citation exhibited this especially is just luck: the file lists an incidence of 3.0 (which is relatively high, and the inversion bug therefore puts the wing 3 degrees closer to a negative stall) the solver happens to generate a nose-down cruise configuration of about 1.5 degrees, and the elevator authority is actually quite high (which causes higher pitch rates under autopilot control). So the bottom line is that Curt was right: it *was* the negative AoA stall (probably the tail's, not the wing's) happening too soon. :) I'm a little leery of changing this in code this close to a release -- the risk of breaking working aircraft is too high. For the short term, this can be fixed in the Citation-II.xml file by simply negating the incidence and twist values on the wing. I did this and tried the autopilot in a maximum speed cruise at low level (which should produce the highest nose-down AoA) without any odd behavior. Curt, can you try that and see if it appears to fix the handling issues? Likewise, anyone with a YASim aircraft that makes use of incidence or twist values is encouraged to try the same modification and report any problems. We can go back after the release and fix the code and all the aircraft files. Andy I'll try to check the ones I've done over the weekend. The one that concerns me most is the B-52F. The wing incidence is set to 6 and the twist to -4 and I'm starting to wonder how it manages to fly at all. Nose down. The fuselage is about 5 deg down when in level flight. I got some good info on the B-52F from someone who flew around 3000 hrs in that model and around 6000 hrs total in all models, apart from the A/B, and it was flying to within around 10 kts or so of what it should have been doing and was climbing at about the right rate. LeeE Depending on weight, alt and speed, 5 deg nose-down could be correct. The incidence of +6 degrees is correct but I had to estimate the twist. I should be able to have a look at it sometime this weekend. Ta for having a look. LeeE ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Citation pitch down divergence. Fixed?
Lee Elliott wrote: On Friday 11 Nov 2005 02:47, Josh Babcock wrote: Lee Elliott wrote: On Thursday 10 Nov 2005 20:20, Andy Ross wrote: After some prodding from Curt, I finally spent a few hours yesterday tracking down the pitch down discontinuity in the Citation. Well, I didn't find a discontinuity. I can now graph the lift curve from a Surface (a real one, part of the real aircraft, not an isolated test instance) and verify that it's valid and correct looking through the entire AoA regime. But I think I *did* find the problem: it seems that I, er, misdocumented the incidence and twist parameters in the YASim configuration. The README.yasim file states that these numbers are positive for positive AoA (i.e. a positive incidence on a wing generates extra lift, and a negative twist causes the wing tips to stall after the root). But the code was interpreting the number as a rotation about the YASim Y axis, which points out the left wing and therefore is positive *down*. Oops. The reason the citation exhibited this especially is just luck: the file lists an incidence of 3.0 (which is relatively high, and the inversion bug therefore puts the wing 3 degrees closer to a negative stall) the solver happens to generate a nose-down cruise configuration of about 1.5 degrees, and the elevator authority is actually quite high (which causes higher pitch rates under autopilot control). So the bottom line is that Curt was right: it *was* the negative AoA stall (probably the tail's, not the wing's) happening too soon. :) I'm a little leery of changing this in code this close to a release -- the risk of breaking working aircraft is too high. For the short term, this can be fixed in the Citation-II.xml file by simply negating the incidence and twist values on the wing. I did this and tried the autopilot in a maximum speed cruise at low level (which should produce the highest nose-down AoA) without any odd behavior. Curt, can you try that and see if it appears to fix the handling issues? Likewise, anyone with a YASim aircraft that makes use of incidence or twist values is encouraged to try the same modification and report any problems. We can go back after the release and fix the code and all the aircraft files. Andy I'll try to check the ones I've done over the weekend. The one that concerns me most is the B-52F. The wing incidence is set to 6 and the twist to -4 and I'm starting to wonder how it manages to fly at all. Nose down. The fuselage is about 5 deg down when in level flight. I got some good info on the B-52F from someone who flew around 3000 hrs in that model and around 6000 hrs total in all models, apart from the A/B, and it was flying to within around 10 kts or so of what it should have been doing and was climbing at about the right rate. LeeE Depending on weight, alt and speed, 5 deg nose-down could be correct. The incidence of +6 degrees is correct but I had to estimate the twist. I should be able to have a look at it sometime this weekend. Ta for having a look. LeeE ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d Yeah, look at a picture of one in flight. The wings are mounted at a high AOA so it can make four point landings at low airspeeds and low descent rates. The b47 had a similar setup, but only the gear was level, the entire fuselage pointed up in the air on that one. Several soviet bombers with bicycle gear also had that look. Josh ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] mi_cmd_stack_list_frames: Not enough frames in stack.
On Friday 11 Nov 2005 17:35, Erik Hofman wrote: Arthur Wiebe wrote: OK, But then why when I select the A-10 or f16 fgfs crashes? But when selecting the c172p and j3cub there is no problem? The only commonality between the A-10 and f-16 is the turbine sound file?? Erik Agreed - I used the generic sound files for the A-10 but the engine related ones are probably the only ones common to the F-16 and A-10 but not used by the C-172 or j3 cub. LeeE ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] V9.9 test run
[EMAIL PROTECTED] wrote: I compiled 9.9 test version on my Thinkpad T42 (I'm on the road) and after loading the cloud file, it worked for the default Cessna. However, when I tried the Citation I got the following messages, and it would not take off. It also had a couple of the instruments on the left side o f the panel (clock and the one above it) that were largely obscured by gray lines. Couldn't do much else without a joystick, which is not where I am. Hope this helps somebody, Rex fgfs --aircraft=Citation-II Dent: ..Dent: EHAMDent: .opening file: /usr/local/share/FlightGear/data/Navaids/carrier_nav.dat /usr/local/share/FlightGear/data/Navaids/TACAN_freq.dat RenderTexture Error: Couldn't find a suitable pixel format. open /dev/[sound/]dsp: Device or resource busy Audio initialization failed! WARNING: ssgLoadAC: Failed to open '/usr/local/share/FlightGear/data/Aircraft/c172r/Models/c172-dpm.ac' for reading Reading xml electrical system model from /usr/local/share/FlightGear/data/Aircraft/beech99/beech99-electrical.xml Failed to load electrical system model: /usr/local/share/FlightGear/data/Aircraft/beech99/beech99-electrical.xml netAddress::set: Resource temporarily unavailable Initialising callsign using 'Aircraft/Citation/Models/Citation-II.xml' Ahhh, good catch. The citation-ii has an external dependency on an aircraft not distributed with the base package. This will be fixed in the next round ... Curt. -- Curtis Olsonhttp://www.flightgear.org/~curt HumanFIRST Program http://www.humanfirst.umn.edu/ FlightGear Project http://www.flightgear.org Unique text:2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FlightGear v0.0.9-pre3
Jon Stockill wrote: The following files probably *shouldn't* be there: Aircraft/A-10/.#A-10cl-set.xml.1.6 Aircraft/c172/Models/.#c172p.ac.1.1 Aircraft/c172/Panels/.#default.xml.1.3 Aircraft/c172/Panels/.#c172-panel.xml.1.8 Aircraft/c172/Panels/.#c172-panel.xml.1.4 Models/Trees/.#deciduous-tree.ac.1.3 Scenery/Terrain/w130n30/w123n37/.#KSFO.btg.gz.1.2 Ok, sorry about the emacs droppings, I'll get rid of those for the next round. Thanks for catching this. Curt. -- Curtis Olsonhttp://www.flightgear.org/~curt HumanFIRST Program http://www.humanfirst.umn.edu/ FlightGear Project http://www.flightgear.org Unique text:2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: 0.9.9 scenery?
Speaking of scenery, there are still people from time to time having trouble installing new sceneries. (The whole Scenery/ vs Scenery/Terrain/ and Scenery/Objects/ issues). I think it's worthwhile updating the docs and the getstart guide with these details. It's quite well described at Franz's page: http://members.aon.at/mfranz/flightgear/flightgear-howto.html Another thing is a lot of people expect scenery to be scenery + 3d buildings/objects. While, when you download scenery from FG's site they are pretty much terrain only. It might be useful to emphasising these things in the docs as well. Pigeon. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: 0.9.9 scenery?
On November 11, 2005 08:59 pm, Pigeon wrote: Today 08:59:41 pm Speaking of scenery, there are still people from time to time having trouble installing new sceneries. (The whole Scenery/ vs Scenery/Terrain/ and Scenery/Objects/ issues). I think it's worthwhile updating the docs and the getstart guide with these details. It's quite well described at Franz's page: http://members.aon.at/mfranz/flightgear/flightgear-howto.html Another thing is a lot of people expect scenery to be scenery + 3d buildings/objects. While, when you download scenery from FG's site they are pretty much terrain only. It might be useful to emphasising these things in the docs as well. Pigeon. I think it would a good idea to provide a document on how to use Terrasync as well. Ampere ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] diff for browser change for mac os x to use safari
On 12 Nov 2005, at 00:58, Ima Sudonim wrote:With this change, FlightGear on Mac OS X launches the mac os x Safari browser instead of netscape (w/o this change, the browser won't launch without netscape installed, and netscape isn't one of the installed mac os x browsers). This approach seems silly - I've got Core Foundation code to launch a URL string via LaunchServices - using whatever browser the user has selected in the system. Hard-coding a browser is always going to annoy people.I'll post the patch once I dig out the code.HHJames___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Is it any mistake?
On November 11, 2005 08:05 pm, Gerard ROBIN wrote: Le vendredi 11 novembre 2005 à 19:47 -0500, Ampere K. Hardraade a écrit : On November 11, 2005 07:32 pm, Gerard ROBIN wrote: DO http://ghours.club.fr/fgfs-tux.tar.gz Is it GPL'ed? If so, it will be a good idea to put it into FlightGear's hangar. Ampere Don't know , i only remember it was included in an old FG package. some files are 2001-01 dated. This is the aircraft with tux that some people are looking for: http://ghours.club.fr/Happy-penguin.jpg Would it be possible to put the tarball on our server somewhere? Ampere ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] 0.9.9 repost
Due to underwhelming response to my previous post concerning a test run of 0.9.9-pre2, I'll repost now. Here is the console output while running the F-16: Dent: .Dent: ..Dent: EHAMopening file: /home/dave/FlightGear-0.9.9-pre2/data/Navaids/carrier_nav.dat /home/dave/FlightGear-0.9.9-pre2/data/Navaids/TACAN_freq.dat WARNING: ssgLoadAC: Failed to open '/home/dave/FlightGear-0.9.9-pre2/data/Aircraft/c172r/Models/c172-dpm.ac' for reading Reading xml electrical system model from /home/dave/FlightGear-0.9.9-pre2/data/Aircraft/Generic/generic-electrical.xml Initialising callsign using 'Aircraft/f16/Models/f16.xml' I don't know what the Dent stuff is. The carrier and TACAN stuff is obviously carrier stuff. Every aircraft I've run tries to open a c172 model. Is this because the c172 model is the default and gets loaded even if it isn't needed, or is this the AI-Traffic manager trying to load GA traffic even when it's disabled by default? And the callsign thing, is this a multiplayer or ATC message? Dave ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] 0.9.9 repost
On Fri, 2005-11-11 at 20:17 -0600, Dave Culp wrote: Due to underwhelming response to my previous post concerning a test run of 0.9.9-pre2, I'll repost now. Here is the console output while running the F-16: Dent: .Dent: ..Dent: EHAMopening file: /home/dave/FlightGear-0.9.9-pre2/data/Navaids/carrier_nav.dat /home/dave/FlightGear-0.9.9-pre2/data/Navaids/TACAN_freq.dat WARNING: ssgLoadAC: Failed to open '/home/dave/FlightGear-0.9.9-pre2/data/Aircraft/c172r/Models/c172-dpm.ac' for reading Reading xml electrical system model from /home/dave/FlightGear-0.9.9-pre2/data/Aircraft/Generic/generic-electrical.xml Initialising callsign using 'Aircraft/f16/Models/f16.xml' I don't know what the Dent stuff is. The carrier and TACAN stuff is obviously The Dents are someone's debug code and should probably be removed. carrier stuff. Every aircraft I've run tries to open a c172 model. Is this because the c172 model is the default and gets loaded even if it isn't needed, or is this the AI-Traffic manager trying to load GA traffic even when it's disabled by default? /home/dave/FlightGear-0.9.9-pre2/data/Aircraft/c172r/Models/c172-dpm.ac Does this file exist? And the callsign thing, is this a multiplayer or ATC message? It's a Multiplayer message -- George Patterson ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] CVS SIGSEGV?
I just did a cvs up and when I run fg I get this strace output
.
.
.
ioctl(7, 0x6447, 0) = 0
ioctl(7, 0x6447, 0) = 0
ioctl(7, 0x6447, 0) = 0
ioctl(7, 0x6447, 0) = 0
ioctl(7, 0x6447, 0) = 0
ioctl(7, 0x6447, 0) = 0
ioctl(7, 0x6447, 0) = 0
ioctl(7, 0x6447, 0) = 0
ioctl(7, 0x6447, 0) = 0
ioctl(7, 0x6447, 0) = 0
ioctl(7, 0x6447, 0) = 0
ioctl(7, 0x6447, 0) = 0
ioctl(7, 0x6447, 0) = 0
ioctl(7, 0x6447, 0) = 0
gettimeofday({1131761484, 337352}, NULL) = 0
sched_yield() = 0
select(6, [5], NULL, NULL, {0, 0}) = 0 (Timeout)
gettimeofday({1131761484, 365260}, {300, 0}) = 0
time([1131761484]) = 1131761484
time(NULL) = 1131761484
time(NULL) = 1131761484
gettimeofday({1131761484, 366251}, {300, 0}) = 0
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV +++
Caveats:
I'm using the following patch:
? simgear/math/linalg.h
? simgear/misc/swap_test
? simgear/scene/fgsg
Index: simgear/screen/RenderTexture.cpp
===
RCS file: /var/cvs/SimGear-0.3/SimGear/simgear/screen/RenderTexture.cpp,v
retrieving revision 1.10
diff -u -r1.10 RenderTexture.cpp
--- simgear/screen/RenderTexture.cpp5 Sep 2005 09:02:56 - 1.10
+++ simgear/screen/RenderTexture.cpp31 Oct 2005 07:04:52 -
@@ -456,6 +456,11 @@
#elif defined( __APPLE__ )
#else // !_WIN32
+
+/// Ugly workaround for gl drivers not working correctly with pbuffers.
+return false;
+
+
_pDisplay = glXGetCurrentDisplay();
GLXContext context = glXGetCurrentContext();
int screen = DefaultScreen(_pDisplay);
And also, I have been having some GL issues. glxgears and glxinfo all
work ok, but I am still suspicious. Anyone else having this problem?
Josh
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] 0.9.9 repost
On Friday 11 November 2005 08:31 pm, George Patterson wrote: /home/dave/FlightGear-0.9.9-pre2/data/Aircraft/c172r/Models/c172-dpm.ac Does this file exist? It exists in CVS data, but not in 0.9.9-pre2 data. I think the underlying question is the more interesting one. Why is FG trying to load it anyway? Dave ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] 0.9.9 repost
Dave Culp wrote: Due to underwhelming response to my previous post concerning a test run of 0.9.9-pre2, I'll repost now. Here is the console output while running the F-16: Dent: .Dent: ..Dent: EHAMopening I can get rid of the Dent ... debugging output in Airport/simple.cxx which someone has changed into a big convoluted monster with all kinds of extraneous crap ... not happy about that ... no time to dig through and fix though ... :-( file: /home/dave/FlightGear-0.9.9-pre2/data/Navaids/carrier_nav.dat /home/dave/FlightGear-0.9.9-pre2/data/Navaids/TACAN_freq.dat WARNING: ssgLoadAC: Failed to open '/home/dave/FlightGear-0.9.9-pre2/data/Aircraft/c172r/Models/c172-dpm.ac' for reading Reading xml electrical system model from /home/dave/FlightGear-0.9.9-pre2/data/Aircraft/Generic/generic-electrical.xml Initialising callsign using 'Aircraft/f16/Models/f16.xml' I don't know what the Dent stuff is. The carrier and TACAN stuff is obviously carrier stuff. Every aircraft I've run tries to open a c172 model. Is this because the c172 model is the default and gets loaded even if it isn't needed, or is this the AI-Traffic manager trying to load GA traffic even when it's disabled by default? And the callsign thing, is this a multiplayer or ATC message? Dave ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d -- Curtis Olsonhttp://www.flightgear.org/~curt HumanFIRST Program http://www.humanfirst.umn.edu/ FlightGear Project http://www.flightgear.org Unique text:2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] diff for browser change for mac os x to use safari
I agree with James. I've been using the --open-with option for sometime in the mac builds which is set to open. This opens the url is whatever is the default browser.On 11/12/05, James Turner [EMAIL PROTECTED] wrote: On 12 Nov 2005, at 00:58, Ima Sudonim wrote: With this change, FlightGear on Mac OS X launches the mac os x Safari browser instead of netscape (w/o this change, the browser won't launch without netscape installed, and netscape isn't one of the installed mac os x browsers). This approach seems silly - I've got Core Foundation code to launch a URL string via LaunchServices - using whatever browser the user has selected in the system. Hard-coding a browser is always going to annoy people. I'll post the patch once I dig out the code.HHJames ___Flightgear-devel mailing listFlightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d-- Arthur/- http://sourceforge.net/users/artooro/- http://artooro.blogspot.com ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Possible bug in yasim (not sure though?)
On Fri, 2005-11-11 at 10:04 -0800, Andy Ross wrote: George Patterson wrote: I have compiled and installed pre3 and noticed that I was not able to load the b1900d Yeah, that was me. The patch yesterday for turn off the engines when out of fuel broke the solver for turbine aircraft. Fixed. That'll teach me to add features right before release. Apologies. Andy Thanks Andy. I just completed a nice flight from KSFO to KLAX with 3D clouds turned on. Mistakenly misread 25L as being 24L. George ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Possible bug in yasim (not sure though?)
George Patterson wrote: Thanks Andy. I just completed a nice flight from KSFO to KLAX with 3D clouds turned on. Mistakenly misread 25L as being 24L. George Ooops, stop by the FAA office, do not pass Go, do not collet $200 ... Curt. -- Curtis Olsonhttp://www.flightgear.org/~curt HumanFIRST Program http://www.humanfirst.umn.edu/ FlightGear Project http://www.flightgear.org Unique text:2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Runtime error 0.9.9 on Debian/Testing
I haven't tried to debug this yet, but thought I'd report it. $ fgfs opening file: /usr/local/share/FlightGear/Navaids/carrier_nav.dat /usr/local/share/FlightGear/Navaids/TACAN_freq.dat RenderTexture Error: glXCreateGLXPbufferPtr() failed. Initialising callsign using 'Aircraft/c172p/Models/c172p.xml' freeglut (fgfs): Failed to create cursor freeglut ERROR: Function glutSetCursor called \ without first calling 'glutInit'. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] diff for browser change for mac os x to use safari
Arthur and James, Yes, I agree it's silly, but currently help was broken on my two mac systems (giving a log message that netscape couldn't be found), followed by a dialog that my browser was started. It's really important to me to have browser-based help work on 0.9.9... I forgot that it was broken until now. (I know I had this working at one point, and thought I still did as I was building with a modified options.cxx. I was wrong). I promise to pay much more attention next time or at least be conscious when I try these things Unfortunately, my fix doesn't work. I think it should have been the following diff, but as neither diff is working, don't apply them to cvs please. I can't get this options.cxx change working on Mac OS X, I have to use the option --browser-app=open /Applications/Safari.app when starting flightgear. Any idea where else /sim/startup/browser-app is set or what (if anything) is overwriting it? Never mind about the cvs update. It wouldn't break anything even if applied, because it didn't work anyway. 8-( It looks like the mac browser exec actually belongs in gui/ gui_funcs.cxx. If I modify void helpCb (puObject *) (line 238) to read: string help_app = open /Applications/Safari.app ;//fgGetString (/sim/startup/browser-app); Safari starts up fine and opens help so this is the spot Arthur would need to pop his code into, I guess. It would be nice if the return code from the system call or ShellExecute could be checked before mkDialog is called. It's adding insult to injury when your browser hasn't started, but the dialog says it has 8-( I'm still a little confused as to where /sim/startup/browser-app is being set, as it doesn't seem to be in main/options.cxx as I expected. I will leave this to much wiser heads than my own. Sorry for the trouble. Some days it doesn't pay to get out of bed in the morning... 8-( I'll happily wait for arthur to fix it. Thanks to Arthur and James and all the rest... Ima Index: FlightGear/src/Main/options.cxx === RCS file: /var/cvs/FlightGear-0.9/FlightGear/src/Main/options.cxx,v retrieving revision 1.73 diff -u -r1.73 options.cxx --- FlightGear/src/Main/options.cxx 12 Oct 2005 08:55:58 - 1.73 +++ FlightGear/src/Main/options.cxx 12 Nov 2005 02:41:34 - @@ -172,7 +172,11 @@ fgSetString(/sim/control-mode, joystick); fgSetBool(/sim/auto-coordination, false); #if !defined(WIN32) +#ifdef __APPLE__ +fgSetString(/sim/startup/browser-app, open /Applications/ Safari.app); +#else fgSetString(/sim/startup/browser-app, netscape); +#endif #else fgSetString(/sim/startup/browser-app, webrun.bat); #endif ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Runtime error 0.9.9 on Debian/Testing
Alex Perry wrote: I haven't tried to debug this yet, but thought I'd report it. $ fgfs opening file: /usr/local/share/FlightGear/Navaids/carrier_nav.dat /usr/local/share/FlightGear/Navaids/TACAN_freq.dat RenderTexture Error: glXCreateGLXPbufferPtr() failed. Initialising callsign using 'Aircraft/c172p/Models/c172p.xml' freeglut (fgfs): Failed to create cursor freeglut ERROR: Function glutSetCursor called \ without first calling 'glutInit'. Hey Alex, this has been a 'common' issue that has bit a lot of people. There appears to be a problem with freeglut 2.4. The solution has been to downgrade to freeglut 2.2 or run freeglut-cvs. You could also build with sdl (configure --enable-sdl) and that might side step the issue altogether. Regards, Curt. -- Curtis Olsonhttp://www.flightgear.org/~curt HumanFIRST Program http://www.humanfirst.umn.edu/ FlightGear Project http://www.flightgear.org Unique text:2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] OT: FYI, mac os x developers, xcode 2.2 has been released
According to apple developer connection (ADC) news, Apple's xcode 2.2 has been released. It would be nice to know that the new fixes haven't broken FlightGear... It is an 834 MB disk image update for mac os x 10.4.x. Download Newly Released Xcode 2.2 Today Latest tools make building universal binaries even easier. All Apple Developer Connection members can download the newly released Xcode 2.2 at no cost from the ADC Member Site. Basic ADC memberships are free, and permit downloading development tools and updates. ADC members can download from http://insideapple.apple.com/redir/ 303569/452_100/1ef0a2707706d7cd11214f98ad642f06 Best regards, Ima ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] c172-dpm.ac
The message: WARNING: ssgLoadAC: Failed to open '/home/dave/FlightGear-0.9.9-pre2/data/Aircraft/c172r/Models/c172-dpm.ac' for reading appears all the time now because FGAIMgr::init() attempts to pre-load this model even if the AI-Traffic system is disabled (and it's disabled by default).See src/ATC/AIMgr.cxx lines 78-95. It also assumes that the c172-dpm.ac model will exist. One solution is to fix FGAIMgr to not do this. Another solution would be to put the c172-dpm.ac model in the data/Models/Geometry directory and fix the FGAIMgr to look there instead. Dave ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] PropertyList over network
Hello All, I am considering using a property tree similar to that in Flightgear for a UAV ground control application, and I have a question for the developers on the list. Has anyone ever looked into creating a system to share a common property tree between two computers over a network connection? E.g. when a property is changed at one end it is updated at the other end as well. Do you think that this could be done efficiently? Has anyone written code to do it? Thanks, -Jeff ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: 0.9.9 scenery?
Pigeon wrote: Another thing is a lot of people expect scenery to be scenery + 3d buildings/objects. While, when you download scenery from FG's site they are pretty much terrain only. This is in fact everything we have for most parts of the world until people start populating their favourite areas. Jon and I are ready to accept submissions as we have already been for a long time, 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
