Re: [Flightgear-devel] releases +- bugs
John Denker wrote: It's going to need testing. I'm seeing some peculiar things, e.g. http://www.av8n.com/fly/fgfs/htm/bug-list.htm#bug-jfk-peculiar-taxiways Just for the record: This is caused by a well-known and long-standing 'feature' in the 'genapts' utility, due to the fact that stopways are not getting processed. Cheers, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] releases +- bugs
On Tue, 8 Dec 2009, dave perry wrote: On 12/01/2009 11:38 AM, John Denker wrote: On 12/01/2009 11:19 AM, Heiko Schulz wrote: To your note: So the c172p has now: -struts animation The reported bug http://www.av8n.com/fly/fgfs/htm/bug-list.htm#bug-x1768 concerns the nutcracker, which as of 1 Dec 2009 looks quite weird because it doesn't fold; it just gets shoved rigidly up into the cowling. I just submitted a patch that animates the c172p nose gear nutcracker so it folds as the strut is compressed. It's called an oleo strut. :) g. -- Proud owner of F-15C 80-0007 http://www.f15sim.com - The only one of its kind. ScarletDME - The red hot Data Management Environment A Multi-Value database for the masses, not the classes. http://www.scarletdme.org - Get it _today_! -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] releases +- bugs
I am not exactly sure what you guys are talking about with the nut cracker reference, but the Oleo Strut the vertical assembly with compressed air (or Nitrogen) and hydraulic oil. There is a piston assembly and a metered orifice arrangement, allowing this assembly to act as a shock-absorbing device. The scissors assembly is a torque link, and helps dampen/resist torque moments imposed on the nose landing gear. AP school was a while ago for me, but generally speaking, I believe the torque link is considered a part of the entire Oleo assembly. TB On Dec 9, 2009, at 8:13 AM, Gene Buckle wrote: On Tue, 8 Dec 2009, dave perry wrote: On 12/01/2009 11:38 AM, John Denker wrote: On 12/01/2009 11:19 AM, Heiko Schulz wrote: To your note: So the c172p has now: -struts animation The reported bug http://www.av8n.com/fly/fgfs/htm/bug-list.htm#bug-x1768 concerns the nutcracker, which as of 1 Dec 2009 looks quite weird because it doesn't fold; it just gets shoved rigidly up into the cowling. I just submitted a patch that animates the c172p nose gear nutcracker so it folds as the strut is compressed. It's called an oleo strut. :) g. -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] releases +- bugs
A quick follow-up on my previous post... While researching this a bit more, I found a very interesting engineering document on the mechanics of landing gear systems: http://www.mecheng.adelaide.edu.au/~marjom01/Aeronautical%20Engineering%20Projects/2006/group11.pdf The PDF is just over 6mb in size, but well worth the download. There are very good descriptions of the mechanics involved with different gear systems--and included is some c172-specific information as well, in Chapter 8 (Page 38). The author also shows a calculation showing that a typical nose strut in a 172 compresses about 9.3 on landing. TB On Dec 9, 2009, at 9:02 AM, Thomas Betka wrote: I am not exactly sure what you guys are talking about with the nut cracker reference, but the Oleo Strut the vertical assembly with compressed air (or Nitrogen) and hydraulic oil. There is a piston assembly and a metered orifice arrangement, allowing this assembly to act as a shock-absorbing device. The scissors assembly is a torque link, and helps dampen/resist torque moments imposed on the nose landing gear. AP school was a while ago for me, but generally speaking, I believe the torque link is considered a part of the entire Oleo assembly. TB On Dec 9, 2009, at 8:13 AM, Gene Buckle wrote: On Tue, 8 Dec 2009, dave perry wrote: On 12/01/2009 11:38 AM, John Denker wrote: On 12/01/2009 11:19 AM, Heiko Schulz wrote: To your note: So the c172p has now: -struts animation The reported bug http://www.av8n.com/fly/fgfs/htm/bug-list.htm#bug-x1768 concerns the nutcracker, which as of 1 Dec 2009 looks quite weird because it doesn't fold; it just gets shoved rigidly up into the cowling. I just submitted a patch that animates the c172p nose gear nutcracker so it folds as the strut is compressed. It's called an oleo strut. :) g. -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] releases +- bugs
On 12/01/2009 11:38 AM, John Denker wrote: On 12/01/2009 11:19 AM, Heiko Schulz wrote: To your note: So the c172p has now: -struts animation The reported bug http://www.av8n.com/fly/fgfs/htm/bug-list.htm#bug-x1768 concerns the nutcracker, which as of 1 Dec 2009 looks quite weird because it doesn't fold; it just gets shoved rigidly up into the cowling. I just submitted a patch that animates the c172p nose gear nutcracker so it folds as the strut is compressed. I wrote a wiki article some time ago to do the animation of the nutcracker oleo scissor without the need for nasal: http://wiki.flightgear.org/index.php/Howto:_Animate_gear_scissors Enjoy, Torsten -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] releases +- bugs
On 12/01/2009 11:38 AM, John Denker wrote: On 12/01/2009 11:19 AM, Heiko Schulz wrote: To your note: So the c172p has now: -struts animation The reported bug http://www.av8n.com/fly/fgfs/htm/bug-list.htm#bug-x1768 concerns the nutcracker, which as of 1 Dec 2009 looks quite weird because it doesn't fold; it just gets shoved rigidly up into the cowling. I just submitted a patch that animates the c172p nose gear nutcracker so it folds as the strut is compressed. -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] releases +- bugs
On 12/06/2009 12:26 PM, Stuart Buchanan wrote: 14 :: c172p rudder pedals Can you confirm that the pedals are mounted on the floor? Yes. Useful reference for pedal layout and other details: http://www.flyjnm.com/db4/00381/flyjnm.com/_uimages/P1010033.JPG The recent upgrades (pedals and otherwise) are a huge improvement. Many thanks! One slight suggestion: It might help to make the trim indicator wire 2x or 3x thicker. On a low-resolution screen it sometimes disappears entirely. Thicker would be more realistic ... and more useful. And another: Maybe tilt the fuel caps a few degrees so that the top of the cap is parallel to the local surface of the wing. -- Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] releases +- bugs
John Denker wrote: On 12/04/2009 03:29 PM, Martin Spott wrote in part: Actually, I think, when the release happens we're simply going to make a snapshot of what is available via TerraSync and offer this for a packaged download. As a side effect, this would be the best way to have a large user base testing the Scenery. It's going to need testing. Ah, really ? Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- -- Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] releases +- bugs
Stuart Buchanan wrote: Hi John, Thanks for the list. A number of the c172p issues are on my to-do list (I've indicated relative priorities - let me know if you think they are wrong), and others should have been fixed recently. I've put some comments inline, along with some specific questions. Of course, if you'd like to submit patches for the c172p, I can get them committed. -Stuart I've now checking into CVS fixes for the c172p issues below. I've also modified the prop to give more realistic climb and cruise performance. Unfortunate at full throttle and below-ISA temperatures, you can still over-rev the engine in cruise to 2900rpm + and over 120kts. Feedback is welcome as always. If you had time to add an updated c172p bug list to the wiki (http://wiki.flightgear.org/index.php/Cessna_C172), that would be very helpful from my perspective. -Stuart 5 :: duplicate livery This is on my todo list. Fixed, though I think a better fix would be to have a new default livery with the registration visible. 8 :: c172p and pa24-250 : weird noises For the c172p, would it be worthwhile just replacing the sounds with the c182rg ones? Done - replaced with the c182 engine sounds,. 14 :: c172p rudder pedals On the todo list, but fairly low down. Done. However, I've not made any attempt to model the mechanism behind the pedals. Can you confirm that the pedals are mounted on the floor? 15 :: c172p parking brake Good point - I'll get this on the todo list. Should be straight-forward to add. For reference, is this pulled on and rotated? Could you describe the movement and the shape of the handle? Done. 20 :: c172p carb heat The model for this is improved, but adding the function requires some sort of FDM update, but I'm not quite sure what. Carb heat now fixed properly - pull for on. 22 :: c172p trim indicator Do you have any pictures of this? I've had difficulty finding anything. Also, what's the take-off trim position? Done. 24 :: c172p fuel caps Modelling issue - easy to resolve. What colour should they be? Done. -- Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] releases +- bugs
On 12/04/2009 03:29 PM, Martin Spott wrote in part: Actually, I think, when the release happens we're simply going to make a snapshot of what is available via TerraSync and offer this for a packaged download. As a side effect, this would be the best way to have a large user base testing the Scenery. It's going to need testing. I'm seeing some peculiar things, e.g. http://www.av8n.com/fly/fgfs/htm/bug-list.htm#bug-jfk-peculiar-taxiways -- Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] releases +- bugs
John Denker wrote: On 12/01/2009 12:47 PM, Stuart Buchanan wrote: 4 :: wrong runway, not in airport database I suspect that might be an artifact of the apt.dat file being out of kilter with the scenery you've got. Have you tried TerraSync to see what the latest scenery looks like. Yes, things look much different now. I got rid of the old 1.0.1 scenery, fired up terrasync, restarted fgfs a couple of times so that terrasync would load the new scenery and fgfs would find out about it. Thanks for the clue. I never would have guessed that the problem was scenery-related. In fact I still don't understand how using the old 1.0.1 scenery could cause an existing runway to vanish and a spurious runway to appear. Are runways part of the scenery? Yes, runways are generated as part of the scenery Is the runway information in apt.dat now obsolete, or soon to become obsolete? The apt.dat file is still used by FG for position and airport information, so it is not obselete. However, I believe that some airport information is now also stored as part of the scenery (at least through TerraSync), so there may be some duplication. Perhaps Martin can comment? Is there any chance of making the code more robust, so that it correctly parses apt.dat even when the new scenery is in use? I think the longer-term plan is to move more of the information into the scenery database so there is less reliance on apt.dat. Again, this is something that Martin would be better placed to answer. Does the new scenery have a new version number, or is it still considered 1.0.1? Are there plans for making the new scenery available as tarballs, for folks who aren't running (or can't run) terrasync? I would expect that the new scenery will be released with the next FG release, so that apt.dat and scenery will match. Maybe this would be a good occasion to implement version numbers in the scenery files, and version checking in the scenery-processing code ... so that if it can't handle the old data, it at least realizes it can't handle it. I think the version mismatch issue is specific to CVS users. Always using TerraSync works around the problem, and means you get to pick up the latest scenery updates ;) This obviously isn't a complete solution, but it mitigates the issue. -Stuart -- Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] releases +- bugs
Stuart Buchanan wrote: John Denker wrote: On 12/01/2009 12:47 PM, Stuart Buchanan wrote: Is the runway information in apt.dat now obsolete, or soon to become obsolete? The apt.dat file is still used by FG for position and airport information, so it is not obselete. However, I believe that some airport information is now also stored as part of the scenery (at least through TerraSync), so there may be some duplication. Perhaps Martin can comment? Yes, Sir ;-) Well, I'll save me from writing a longish explanation (last but not least because my hands and fingers are hurting) and, instead, point you to this old posting - written several months before the v1.9.0 release: http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg17407.html The content is still valid as-is. Thanks to James Turner and Durk Talsma we now have a working implementation of the desired features in FlightGear (except from a little nit wrt. the startup position with displaces thresholds present). Is there any chance of making the code more robust, so that it correctly parses apt.dat even when the new scenery is in use? I think the longer-term plan is to move more of the information into the scenery database so there is less reliance on apt.dat. As far as I understand, several people would feel a little bit unhappy about moving more AptNav data into the Scenery - for good reasons. Therefore I'd prefer to stick with the current, somehow 'minimalistic' approach. Aside from that, I'm unaware of any faults, missing 'robustness' in the current 'apt.dat' parser, no matter if old or new Scenery is in use. It's working pretty well for me. Does the new scenery have a new version number, or is it still considered 1.0.1? Are there plans for making the new scenery available as tarballs, for folks who aren't running (or can't run) terrasync? I would expect that the new scenery will be released with the next FG release, so that apt.dat and scenery will match. Yup. Actually, I think, when the release happens we're simply going to make a snapshot of what is available via TerraSync and offer this for a packaged download. As a side effect, this would be the best way to have a large user base testing the Scenery. Nevertheless, there are a few special items which have to get closely synced to the software release process with this very upcoming release. Cheers, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- -- Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] releases +- bugs
Torsten Dreyer a écrit : No transponder correct, an IFR certified aircraft without a transponder is unrealistic. It's low priority on my todo list and I consider it a missing feature, not a bug. My goal is to model a GTX330 which is what I have in the RL Seneca. As a side note: I consider a transponder optional. It's one of the very few items I carry on board just for other peoples (ATC) purpose - next to sick bags ;-) The transponder isn't often powered in a school glider (who cares to take another battery on board when you just plan to turn around the field ?) But for sure, the first time a glider student has the chance to fly (high) in the ATC wisdom, this thing becomes suddenly important. And well, how did you say it works ? Alexis -- Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] releases +- bugs
Hi, Torsten Dreyer a écrit : No transponder correct, an IFR certified aircraft without a transponder is unrealistic. It's low priority on my todo list and I consider it a missing feature, not a bug. My goal is to model a GTX330 which is what I have in the RL Seneca. As a side note: I consider a transponder optional. It's one of the very few items I carry on board just for other peoples (ATC) purpose - next to sick bags ;-) The transponder isn't often powered in a school glider (who cares to take another battery on board when you just plan to turn around the field ?) But for sure, the first time a glider student has the chance to fly (high) in the ATC wisdom, this thing becomes suddenly important. And well, how did you say it works ? Alexis I had to smile a bit, when I read about no transponder - even we had this in the FGFS c172p- it would be useless, as this is only a dummy. We don't have any real simulating transponder yet- so our ATC-tool can't see our squawks, altitude etc;-) Our transponder models are just dummies __ Do You Yahoo!? Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz gegen Massenmails. http://mail.yahoo.com -- Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] releases +- bugs
On 12/01/2009 12:47 PM, Stuart Buchanan wrote: 4 :: wrong runway, not in airport database I suspect that might be an artifact of the apt.dat file being out of kilter with the scenery you've got. Have you tried TerraSync to see what the latest scenery looks like. Yes, things look much different now. I got rid of the old 1.0.1 scenery, fired up terrasync, restarted fgfs a couple of times so that terrasync would load the new scenery and fgfs would find out about it. Thanks for the clue. I never would have guessed that the problem was scenery-related. In fact I still don't understand how using the old 1.0.1 scenery could cause an existing runway to vanish and a spurious runway to appear. Are runways part of the scenery? Is the runway information in apt.dat now obsolete, or soon to become obsolete? Is there any chance of making the code more robust, so that it correctly parses apt.dat even when the new scenery is in use? Does the new scenery have a new version number, or is it still considered 1.0.1? Are there plans for making the new scenery available as tarballs, for folks who aren't running (or can't run) terrasync? Maybe this would be a good occasion to implement version numbers in the scenery files, and version checking in the scenery-processing code ... so that if it can't handle the old data, it at least realizes it can't handle it. -- Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] releases +- bugs
On 2 Dec 2009, at 06:34, Ron Jensen wrote: | 39 – model capitalization – | observed: 19 Dec 2008 | again: 31 Oct 2009 |For example: when specifying the option --aircraft=dhc2W, the |dhc must not be capitalized, while the W must be capitalized. The value used for --aircraft is the file name of the -set.xml file. The command line user can ask flightgear for the value by --show-aircraft. The power user can list the aircraft folder and figure it out for himself. The novice should be using FGRun and avoiding this unpleasantness altogether. OPINION. Actually this one bites me regularly, I was planning to do it when I have a spare moment. James -- Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] releases +- bugs
Do what ? This was brought up in the past , and I suggested changing it to dhc2-wheels , etc ... but dont remember getting much feedback about it ... and I dont have much patience if those people pointing out bugs cant follow through and assist in coming up with a solution if they are able. I'll change these tomorrow in cvs to -wheels ,-skis , etc , where applicable. On 12/2/09, James Turner zakal...@mac.com wrote: On 2 Dec 2009, at 06:34, Ron Jensen wrote: | 39 – model capitalization – | observed: 19 Dec 2008 | again: 31 Oct 2009 |For example: when specifying the option --aircraft=dhc2W, the |dhc must not be capitalized, while the W must be capitalized. The value used for --aircraft is the file name of the -set.xml file. The command line user can ask flightgear for the value by --show-aircraft. The power user can list the aircraft folder and figure it out for himself. The novice should be using FGRun and avoiding this unpleasantness altogether. OPINION. Actually this one bites me regularly, I was planning to do it when I have a spare moment. James -- Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] releases +- bugs
syd adams wrote: Do what ? This was brought up in the past , and I suggested changing it to dhc2-wheels , etc ... but dont remember getting much feedback about it ... and I dont have much patience if those people pointing out bugs cant follow through and assist in coming up with a solution if they are able. I'll change these tomorrow in cvs to -wheels ,-skis , etc , where applicable. Hi Syd, I think the suggestion is that this is fixed in the code, so you don't need to change any of your -set.xml files. So, the following arguments would all work: --aircraft=dhc2w --aircraft=dhc2W --aircraft=DHC2W Of course, if you think that dhc2-ski is better than dhc2s, then that's obviously your decision, but that's a different issue to the one John brought up. -Stuart -- Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] releases +- bugs
On 2 Dec 2009, at 09:19, Stuart Buchanan wrote: Of course, if you think that dhc2-ski is better than dhc2s, then that's obviously your decision, but that's a different issue to the one John brought up. Agreed on all counts - I will fix the case-sensitivity, but other issues are up to the aircraft developer! James -- Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] releases +- bugs
Stuart Buchanan wrote: So, the following arguments would all work: --aircraft=dhc2w --aircraft=dhc2W --aircraft=DHC2W Of course, if you think that dhc2-ski is better than dhc2s, then that's obviously your decision, but that's a different issue to the one John brought up. -Stuart Years ago I tweaked my local FG so that it first did a case sensitive search for aircraft (to cover the case that you had a c172 and a C172 which were different), and then if it found nothing in that search, it did a case insensitive search. I seem to remember that this was 5 or 6 lines of extra code, but I don't have that source tree any more. Richard This e-mail has been scanned for all viruses by Star. 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 -- Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] releases +- bugs
Hi John, thank your for the bug report. But it would be great if you could update your datas and FGFS generally, there was some smaller changes done on the c172p and other things lately. But generally: missing features arent't bugs! To your note: So the c172p has now: -kollsman window -new modelled carb heat, mixturs, throttle controlls -struts animation Feel free to improve the aircraft yourself or provide more informations like manuals, images etc. to the involved aircraft developers, so they can make it better. HHS --- John Denker j...@av8n.com schrieb am Di, 1.12.2009: Von: John Denker j...@av8n.com Betreff: [Flightgear-devel] releases +- bugs An: FlightGear developers discussions flightgear-devel@lists.sourceforge.net Datum: Dienstag, 1. Dezember 2009, 19:02 On 11/26/2009 11:28 PM, Tim Moore wrote: When those are merged in, and I expect that to happen before December 1st, I suggest we roll those up as a real beta and start working towards a New Year's Eve release. I won't plan on merging anything else to the master branches before the release except for bug fixes. Here are some bugs that might be worth fixing before the next release. 1 :: invisible hot spots 2 :: c172p basic flight dynamics 3 :: viewer: weird orange cast 4 :: wrong runway, not in airport database 5 :: duplicate livery 6 :: navradio: reversible ILS 7 :: X52 joystick configuration 8 :: c172p and pa24-250 : weird noises 9 :: c182 sound 10 :: c172p interior lighting 11 :: landing light and taxi light not usable for landing or taxiing 12 :: disappearing GS needle 13 :: no Kollsman window 14 :: c172p rudder pedals 15 :: c172p parking brake 16 :: c172p switches 17 :: c172p voltmeter 18 :: c172p carb heat, throttle, mixture 19 :: c172p audio panel 20 :: c172p carb heat 21 :: c182rg sunk in 22 :: c172p trim indicator 23 :: c172p flap position 24 :: c172p fuel caps 25 :: c172p nutcracker 26 :: see-through 172 27 :: c172p EGT 28 :: c172p and SenecaII transponder 29 :: gps 30 :: SenecaII flap motor 31 :: check for missing scenery 32 :: check for wrong scenery 33 :: creepy creep when parked 34 :: initialization on the glideslope 35 :: locate-in-air trashes the sim 36 :: model-hz trashes sim 37 :: runway lights 38 :: FGShortRef out of date 39 :: c172p stray structure 40 :: CPU hog 41 :: memory hog 42 :: Mr. Freeze 43 :: model capitalization 44 :: airport lights, other airport services 45 :: OAT gauges 46 :: dhc2 engine controls 47 :: kx165 pick animation 48 :: zombie adf 49 :: c182 zombie adf 50 :: adf 3:00 51 :: KAP-140 alerter 52 :: tower view 53 :: c172p electrical system 54 :: documentation: SG_LOG feature 55 :: FDM initialization 56 :: 64-bit acinclude.m4 and configure script 57 :: c182rg sunk in 58 :: VOR shacks 59 :: xml panel group 60 :: xml panel sublayers 61 :: Seneca initialization noises 62 :: Seneca console warnings 63 :: c172p splash screen 64 :: splash screen during re-init 65 :: inappropriate vegetation 66 :: heading indicator 67 :: flight dynamics in general; heading indicator errors 68 :: dealing with ambiguous navaids 69 :: prop strike For details, see http://www.av8n.com/fly/fgfs/htm/bug-list.htm -- Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel __ Do You Yahoo!? Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz gegen Massenmails. http://mail.yahoo.com -- Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] releases +- bugs
On 12/01/2009 11:19 AM, Heiko Schulz wrote: thank your for the bug report. :-) But it would be great if you could update your datas and FGFS generally, there was some smaller changes done on the c172p and other things lately. Every one of those bug reports has a date. There are so many bugs that I can't check them all every day. To your note: So the c172p has now: -kollsman window OK. Thanks! Listing updated. -new modelled carb heat, mixturs, throttle controlls OK. They look nice. Listing updated. -struts animation The reported bug http://www.av8n.com/fly/fgfs/htm/bug-list.htm#bug-x1768 concerns the nutcracker, which as of 1 Dec 2009 looks quite weird because it doesn't fold; it just gets shoved rigidly up into the cowling. -- Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] releases +- bugs
Hi, Every one of those bug reports has a date. There are so many bugs that I can't check them all every day. Yep, exactly that makes me woender! Even with the newest date, you must probably missed some things. Generally I found some other things, which was improved. But as I use win32, it might be that some things aren't working on your system but on others, so should name your system specs (GPU, OS etc...) as well. HHS __ Do You Yahoo!? Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz gegen Massenmails. http://mail.yahoo.com -- Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] releases +- bugs
Eh, a bugtracker? Jari Heiko Schulz wrote: Hi, Every one of those bug reports has a date. There are so many bugs that I can't check them all every day. Yep, exactly that makes me woender! Even with the newest date, you must probably missed some things. Generally I found some other things, which was improved. But as I use win32, it might be that some things aren't working on your system but on others, so should name your system specs (GPU, OS etc...) as well. HHS __ Do You Yahoo!? Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz gegen Massenmails. http://mail.yahoo.com -- Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] releases +- bugs
Hi John, Thanks for the list. A number of the c172p issues are on my to-do list (I've indicated relative priorities - let me know if you think they are wrong), and others should have been fixed recently. I've put some comments inline, along with some specific questions. Of course, if you'd like to submit patches for the c172p, I can get them committed. -Stuart 2 :: c172p basic flight dynamics You suggest two possible explanations. Not having access to a C-172, nor enough flight time to be able to guess which is correct, I'm not sure there's much I can sensibly do without making it worse. If you can suggest which is wrong, I'll see what I can do. My guess would be idle RPM, given your previous comments that the aircraft if over-powered. 4 :: wrong runway, not in airport database I suspect that might be an artifact of the apt.dat file being out of kilter with the scenery you've got. Have you tried TerraSync to see what the latest scenery looks like. 5 :: duplicate livery This is on my todo list. 8 :: c172p and pa24-250 : weird noises For the c172p, would it be worthwhile just replacing the sounds with the c182rg ones? 10 :: c172p interior lighting This should now be fixed - there's a dial to control lighting next to the carb heat. However, it's not connected to the (non-existant!) master switch, or an electrical system in general. 11 :: landing light and taxi light not usable for landing or taxiing This is a general issue that requires a general fix. 12 :: disappearing GS needle Lacking IFR experience, I don't know exactly how to fix this, and in particular the barber-pole behaviour. 13 :: no Kollsman window As mentioned by HHS, this should now be fixed. 14 :: c172p rudder pedals On the todo list, but fairly low down. 15 :: c172p parking brake Good point - I'll get this on the todo list. Should be straight-forward to add. For reference, is this pulled on and rotated? Could you describe the movement and the shape of the handle? 16 :: c172p switches On the todo list, but low down. 17 :: c172p voltmeter A side-effect of the lack of an electrical system. 18 :: c172p carb heat, throttle, mixture Now fixed. 19 :: c172p audio panel Requires electrical system. 20 :: c172p carb heat The model for this is improved, but adding the function requires some sort of FDM update, but I'm not quite sure what. 21 :: c182rg sunk in On the todo, but low priority. 22 :: c172p trim indicator Do you have any pictures of this? I've had difficulty finding anything. Also, what's the take-off trim position? 23 :: c172p flap position Now fixed. 24 :: c172p fuel caps Modelling issue - easy to resolve. What colour should they be? 25 :: c172p nutcracker Added to the todo list, low priority. 26 :: see-through 172 Added to TODO list, low priority. 27 :: c172p EGT Added to TODO list, medium priority. 28 :: c172p and SenecaII transponder Added to todo list, medium priority. 29 :: gps Is it realistic to fly without a GPS these days? Well, I manage quite happily ;) Seriously - I think adding a GPS will be quite a lot of work. Do we have any that are plug-and-play? 31 :: check for missing scenery A fine idea. I'll see if I have time. snip 38 :: FGShortRef out of date Very good point. I'll look into what we need to do to regenerate. 39 :: c172p stray structure On the todo list 53 :: c172p electrical system If you have a patch, that would be great. snip -- Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] releases +- bugs
Hi Guys, Nice list! I gave up modelling, as didn't find enough and sufficient pics of the whole cockpit. John, you forgot to mention that the c172 seems also to have a fuel selector similar to the PA24, as well as braking circuits, primer, which are also missing on the c172p in FGFS. And a flight hour recorder maybe Maybe this: http://www.redskyventures.org/doc/cessna-poh/C172N-1978-POH-S1to7-scanned.pdf could help a bit. It is a POH of the c172N, but maybe the difference isn't all too big. To simulate the real thing it would be great if we had a real aircraft as reference like Torsten has with his own SenecaII or Dave Perry with the PA24-250. Cheers HHS __ Do You Yahoo!? Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz gegen Massenmails. http://mail.yahoo.com -- Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] releases +- bugs
On 12/01/2009 12:47 PM, Stuart Buchanan wrote: Hi John, Thanks for the list. A number of the c172p issues are on my to-do list (I've indicated relative priorities - let me know if you think they are wrong), and others should have been fixed recently. I've put some comments inline, along with some specific questions. Of course, if you'd like to submit patches for the c172p, I can get them committed. -Stuart 2 :: c172p basic flight dynamics You suggest two possible explanations. Not having access to a C-172, nor enough flight time to be able to guess which is correct, I'm not sure there's much I can sensibly do without making it worse. If you can suggest which is wrong, I'll see what I can do. My guess would be idle RPM, given your previous comments that the aircraft if over-powered. 4 :: wrong runway, not in airport database I suspect that might be an artifact of the apt.dat file being out of kilter with the scenery you've got. Have you tried TerraSync to see what the latest scenery looks like. 5 :: duplicate livery This is on my todo list. 8 :: c172p and pa24-250 : weird noises For the c172p, would it be worthwhile just replacing the sounds with the c182rg ones? 10 :: c172p interior lighting This should now be fixed - there's a dial to control lighting next to the carb heat. However, it's not connected to the (non-existant!) master switch, or an electrical system in general. 11 :: landing light and taxi light not usable for landing or taxiing This is a general issue that requires a general fix. 12 :: disappearing GS needle Lacking IFR experience, I don't know exactly how to fix this, and in particular the barber-pole behaviour. This was fixed as well as adding realistic GS and Nav flags and smooth transitions to 0 position when out of range or switching to new freq w/o LOC. The c172p, pa24, and pa28 all now use the vor in Aircraft/Instruments-3d. 13 :: no Kollsman window As mentioned by HHS, this should now be fixed. 14 :: c172p rudder pedals On the todo list, but fairly low down. 15 :: c172p parking brake Good point - I'll get this on the todo list. Should be straight-forward to add. For reference, is this pulled on and rotated? Could you describe the movement and the shape of the handle? 16 :: c172p switches On the todo list, but low down. 17 :: c172p voltmeter A side-effect of the lack of an electrical system. 18 :: c172p carb heat, throttle, mixture Now fixed. 19 :: c172p audio panel Requires electrical system. 20 :: c172p carb heat The model for this is improved, but adding the function requires some sort of FDM update, but I'm not quite sure what. 21 :: c182rg sunk in On the todo, but low priority. 22 :: c172p trim indicator Do you have any pictures of this? I've had difficulty finding anything. Also, what's the take-off trim position? 23 :: c172p flap position Now fixed. 24 :: c172p fuel caps Modelling issue - easy to resolve. What colour should they be? 25 :: c172p nutcracker Added to the todo list, low priority. 26 :: see-through 172 Added to TODO list, low priority. 27 :: c172p EGT Added to TODO list, medium priority. 28 :: c172p and SenecaII transponder Added to todo list, medium priority. 29 :: gps Is it realistic to fly without a GPS these days? Well, I manage quite happily ;) Seriously - I think adding a GPS will be quite a lot of work. Do we have any that are plug-and-play? 31 :: check for missing scenery A fine idea. I'll see if I have time. snip 38 :: FGShortRef out of date Very good point. I'll look into what we need to do to regenerate. 39 :: c172p stray structure On the todo list 53 :: c172p electrical system If you have a patch, that would be great. snip -- Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev ___ Flightgear-devel
Re: [Flightgear-devel] releases +- bugs
For details, see http://www.av8n.com/fly/fgfs/htm/bug-list.htm I only checked your reported Seneca issues: ...including the c182rg, Seneca, pa24-250, and even the c172r, which have animated rudder pedals with some degree of realism. At least 'some degree' ;-) No transponder correct, an IFR certified aircraft without a transponder is unrealistic. It's low priority on my todo list and I consider it a missing feature, not a bug. My goal is to model a GTX330 which is what I have in the RL Seneca. As a side note: I consider a transponder optional. It's one of the very few items I carry on board just for other peoples (ATC) purpose - next to sick bags ;-) Flap motor sound I can confirm, there is no flap motor and no flap motor sound in RL. Flaps are manually operated. I need to record the t-klockkk sound when operating the handle to be realistic. Since there is no flap indicator, It might be OK to have the sound of the motor as an audible feedback for flap operation. Moving with parking brake set I think this is JSBSim related, I tried to increase the friction coefficient without success. Open issue. misteriously disappearing OAT gauge demystified - fixed in CVS (relaxed range animation) initialization noises not observable here anymore with latest CVS Console warning: could not find texture garmin.rgb This texture is not used in any of the 3d models, please check your files gma340.ac and gps155.ac for latest updates. Console warning: ..wdot doesn't appear to be trimmable Should have been gone a while ago. Thanks for testing and reporting. I have added the open items to the Seneca's wiki page. From my point of view, there is no showstopper for a release with the Seneca. Regards, Torsten -- Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] releases +- bugs
On 12/01/2009 02:04 PM, Torsten Dreyer wrote: Thanks for testing and reporting. :-) I updated my bug list. From my point of view, there is no showstopper for a release with the Seneca. Agreed. It's definitely an impressive piece of work. Transponder ... not a bug. I moved it to the wish list section. My goal is to model a GTX330 which is what I have in the RL Seneca. That is a fine goal. But in the meantime, it wouldn't be too horrible to use the KT70, as seen in e.g. the C182RG and PA24-250. Think of it as a loaner while the GTX330 is in the shop. :-) It increases the utility of the aircraft. -- Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] releases +- bugs
On 12/01/2009 12:47 PM, Stuart Buchanan wrote: Thanks for the list. :-) 22 :: c172p trim indicator Do you have any pictures of this? I've had difficulty finding anything. Also, what's the take-off trim position? As mentioned by HHS, here is a Cessna POH in .pdf format: http://www.redskyventures.org/doc/cessna-poh/C172N-1978-POH-S1to7-scanned.pdf Pages 7-6 and 7-7 have an annotated diagram of the instrument panel. That's pdf page 57. The trim indicator is a thick white wire that sticks out of the black slot about 1 cm to the left of the trim wheel. Nose-UP trim is represented by the wire being LOWER int the slot. That's logical if you think that you are moving the back of the wheel, while the nose is in front of the wheel. Nominal takeoff trim is near the middle of the range. Real-world takeoff trim with only the front seats occupied is a little more nose-up than that. 24 :: c172p fuel caps Modelling issue - easy to resolve. What colour should they be? Light gray would be fine. Just something to contrast with the color of the wing. And if you want to get fancy, maybe dark gray on the vertical cylindrical sides of the cap, and lighter gray on the top disk. A 3x decrease in the height of the cylinder, relative to what's currently used for the main body of the cap, would probably look about right. 15 :: c172p parking brake Good point - I'll get this on the todo list. Should be straight-forward to add. For reference, is this pulled on and rotated? Yes, pulled a few cm and rotated 90 degrees. Could you describe the movement and the shape of the handle? See item 37 on the aforementioned diagram. It rotates around its starboard end, above the 7 in the 37. The axis of rotation is also the axis of pull; it's a rod in a sleeve. It pulls out pretty much parallel to the aircraft X axis. If that's not clear enough, please re-ask the question. === Other questions have been noted, but I don't have time to answer them right now. -- Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] releases +- bugs
On Tue, 2009-12-01 at 11:38 -0700, John Denker wrote: On 12/01/2009 11:19 AM, Heiko Schulz wrote: thank your for the bug report. :-) But it would be great if you could update your datas and FGFS generally, there was some smaller changes done on the c172p and other things lately. Every one of those bug reports has a date. There are so many bugs that I can't check them all every day. It would be nice if you would put this list on a wiki somewhere instead of engaging in this monologue with yourself. Then you wouldn't be burdened to do all this by yourself, and your useful observations could be sorted from the chaff that comprises a large portion of this list. |28 – check for wrong scenery – | observed: 16 Dec 2008 | FGFS needs to be more defensive about out-of-date or otherwise | defective scenery files. The scenery format has be constant for years. There is absolutely no reason to refuse to use scenery just because its not the latest release. Mark this bug as bogus. | 32 – model-hz trashes sim – | observed: 12 Dec 2008 | again: 1 Nov 2009 | The –model-hz=10 setting still crashes the sim. No doubt. --model-hz is the speed the flight dynamics model runs at. It is an advanced control and should be left at the default 120 unless you know what you are doing, and are changing it for a specific purpose. And in any case should be higher than the frame rate. Another bogus bug. | 39 – model capitalization – | observed: 19 Dec 2008 | again: 31 Oct 2009 |For example: when specifying the option --aircraft=dhc2W, the |dhc must not be capitalized, while the W must be capitalized. The value used for --aircraft is the file name of the -set.xml file. The command line user can ask flightgear for the value by --show-aircraft. The power user can list the aircraft folder and figure it out for himself. The novice should be using FGRun and avoiding this unpleasantness altogether. OPINION. | 51 – FDM initialization – | observed: 1 Nov 2009 | Attempts to initialize the simulator aloft cause ugly error messages | and other problems. If I specify the options | --vor=SFO --altitude=5000 on the command line, I get on the console: Specifying a velocity by adding --vc=120 to your command line will prevent the stall. The console messages are showing trim errors caused by JSBSim being (incorrectly) re-initialized. This does need to be fixed. Also it appears the initialized running flag is being over-ridden so the engine is not running at start-up. | Inconsistency detected by ld.so: dl-close.c: 719: _dl_close: Assertion `map-l_init_called' failed! This is caused by a bug in you openal-soft version. | 58 – splash screen during re-init – | observed: 1 Nov 2009 |During a re-init, such as occurs when the relocate-in-air popup is |invoked, the splash-screen reappears. This is unexpected and unhelpful. Opinion. The splash screen hides the visual discontinuity caused by jumping to a new location, and serves as a visual indicator that you have been restarted. I just wish it would fade out a bit faster. |59 – inappropriate vegetation – | observed: 2 Nov 2009 |There are trees that look like pine trees on the infield of Tucson |International Airport. |First of all, airports don’t generally allow trees of any kind on the |infield, because of the collision hazard. |Secondly, the Tucson area is a desert. Pine trees are not very common |in the desert. With the current terragear the airport boundaries are a fixed distance from the runway/taxiways. Once we switch to version 8.5 of the apt.dat and regenerate scenery this should go away. |63 – prop strike – | observed: 29 Dec 2008 | again: 1 Nov 2009 |In many aircraft including the default c172p, the engine continues |to run after a crash. In Real Life a prop strike tends to stop the | engine This could be modeled on a per-aircraft/per-engine basis by adding a contact point on the spinner and if its wow goes true shutting the engine off. And when we are done updating all the aircraft we can change the name from flightgear to crashgear. Ron -- Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
