RE: [Flightgear-devel] Question re: bug reporting/tracking/etc.
Lee Elliott On Tuesday 08 June 2004 23:01, Vivian Meazza wrote: Andy Ross wrote Chris Metzler wrote: Sometimes I run into issues with FlightGear -- fgfs, data, scenery, whatever -- that I'm reluctant to report because I'm concerned that the developers already know about them; Indeed, that's a good idea. We've been known to kill and eat reporters of known bugs. :) As for using a bugzilla or whatnot, I'm neutral. I find that I always end up fixing the bugs that people whine about the most anyway. Bug tracking systems tend to fill up quickly with not-quite-bugs that no one wants to look at. Speaking of which, is there any progress on the Merlin propeller gearing issue? Regards Vivian I was having similar problems with the Comper Swift geared prop and at one point I was getting the right power and rpm but at the wrong mixture and fuel flow rates - both seemed out by approx the same ratio as the prop gearing. I haven't looked at it for while but I'll try it in the next few days or so and see what the situation is with it now. Ta. The Spitfire model is nearing completion, and I need to fly it to test the sounds etc., so I would be grateful if we could sort this one. Vivian ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Question re: bug reporting/tracking/etc.
On Wednesday 09 June 2004 17:03, Vivian Meazza wrote: Lee Elliott On Tuesday 08 June 2004 23:01, Vivian Meazza wrote: Andy Ross wrote Chris Metzler wrote: Sometimes I run into issues with FlightGear -- fgfs, data, scenery, whatever -- that I'm reluctant to report because I'm concerned that the developers already know about them; Indeed, that's a good idea. We've been known to kill and eat reporters of known bugs. :) As for using a bugzilla or whatnot, I'm neutral. I find that I always end up fixing the bugs that people whine about the most anyway. Bug tracking systems tend to fill up quickly with not-quite-bugs that no one wants to look at. Speaking of which, is there any progress on the Merlin propeller gearing issue? Regards Vivian I was having similar problems with the Comper Swift geared prop and at one point I was getting the right power and rpm but at the wrong mixture and fuel flow rates - both seemed out by approx the same ratio as the prop gearing. I haven't looked at it for while but I'll try it in the next few days or so and see what the situation is with it now. Ta. The Spitfire model is nearing completion, and I need to fly it to test the sounds etc., so I would be grateful if we could sort this one. Vivian I did some ground running tests on the Comper Swift today, after updating the YASim config to use the new piston-engine sub-element of propeller, and tried different combinations of engine and propeller rpms. The gearing on the Comper Swift was 0.47 and the max engine rpm was 3300 rpm so I tried ungeared settings with the with both the prop and engine rpm set to 3300, and then 1551, and got the following results:- rpm_Max rpm_Max PT__Fuel Flow 33003306267_9.68 15511553264_9.68 This seemed ok and the a/c performed about right too. However, when I introduced gearing at 0.47, so that the engine was rated at 3300 rpm and the prop at 1551 rpm I got the following numbers:- Max rpm_Max PT__Fuel Flow 2205117_6.45 A quick bit of math with the numbers produced for PT: 117/267 = 0.43 - this is close'ish to the gear ratio. 117/264 = 0.44 - even closer. for eng rpm: 2205/3306 = 0.666 2205/1553 = 1.419 for fuel flow: 6.45/9.68 = 0.666 The way that the geared rpm slotted between the eng and prop rpms seemed curious too:- (3300+1551)*0.47 = 2282 (3300+1551)*0.43 = 2085 (3300+1551)*0.44 = 2134 just out of curiosity (3300+1551)*0.4545 = 2204 Allowing for the fact that YASim will be generating a different solution for each combination, so I'd expect some variation in the results, some of the numbers seem as though they might be significant, but as to what exactly they signify... LeeE ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Question re: bug reporting/tracking/etc.
On Tue, 08 Jun 2004 12:00:50 -0500 Jon S Berndt [EMAIL PROTECTED] wrote: I think a bug/feature request facility such as the one on the SourceForge site is invaluable. I've certainly found the Debian and GNOME BTSes invaluable. A ton of times I've run into issues with stuff on Debian, immediately checked the BTS and found that it relates to a bug that someone else has already reported. Sometimes, workarounds are present in the discussion about that bug (and thus available in a place most likely to be encountered by others experiencing the same problem), which is handy for when the fix is not yet available in the official package. The GNOME bugzilla appears to also be used to keep track of who's working on fixing something; and if they had to put the problem down because of other commitments or whatever, there's a record of what they learned and how far they got. OTOH, it takes a fair amount of effort to maintain such a BTS. FG is a much smaller project, and thus would require less effort, to be sure; but for the same reason, it'd have (it has) a lot fewer bugs to keep track of, and so there's less of a compelling need. And while I think it'd be handy to have, I have no idea whatsoever whether the overhead is larger than the benefit. And of course, it'd only be useful if people committed to using it. If you ever find an issue with JSBSim in FlightGear, please do report it. You can find the link to the reporting facilities for JSBSim at www.jsbsim.org. Well, some problems one might run into are clearly not FDM related. But given my current state of ignorance, I can imagine running into problems for which I would have no idea whether they're related to the guts of fgfs or whether they're related to the FDM used. Hopefully that will change with time. -c -- Chris Metzler [EMAIL PROTECTED] (remove snip-me. to email) As a child I understood how to give; I have forgotten this grace since I have become civilized. - Chief Luther Standing Bear pgpqYyXBzLkTK.pgp Description: PGP signature ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Question re: bug reporting/tracking/etc.
On Tue, 08 Jun 2004 10:04:54 -0700 Andy Ross [EMAIL PROTECTED] wrote: Chris Metzler wrote: Sometimes I run into issues with FlightGear -- fgfs, data, scenery, whatever -- that I'm reluctant to report because I'm concerned that the developers already know about them; Indeed, that's a good idea. We've been known to kill and eat reporters of known bugs. :) Heh. Well, actually, everyone I've talked to here and on #flightgear has been very very friendly. It's not so much fear of anyone's wrath as just wanting to be kind. I've personally been in other situations where I was responsible for something that became broken, and after being told for the fourth or fifth time that something was broken, I was longing for a door sign that said Yes, I know it's broken; tell me it's broken again and you'll be replaced with a very small shell script. As for using a bugzilla or whatnot, I'm neutral. I find that I always end up fixing the bugs that people whine about the most anyway. Bug tracking systems tend to fill up quickly with not-quite-bugs that no one wants to look at. Fair enough. Most of my experience with BTSes has been regarding bugs I've filed, or bugs that other people have filed that relate to some problem I'm having, or whatever. The developers' perspectives are necessarily different. -c -- Chris Metzler [EMAIL PROTECTED] (remove snip-me. to email) As a child I understood how to give; I have forgotten this grace since I have become civilized. - Chief Luther Standing Bear pgpqcWjDN0inL.pgp Description: PGP signature ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Question re: bug reporting/tracking/etc.
On Tue, 8 Jun 2004 12:44:33 -0400 Chris Metzler [EMAIL PROTECTED] wrote: When the project was hosted at SF, there was a bug tracking system there. Was it used? Would having a working BTS be a good thing, I think a bug/feature request facility such as the one on the SourceForge site is invaluable. If you ever find an issue with JSBSim in FlightGear, please do report it. You can find the link to the reporting facilities for JSBSim at www.jsbsim.org. Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Question re: bug reporting/tracking/etc.
Chris Metzler wrote: Sometimes I run into issues with FlightGear -- fgfs, data, scenery, whatever -- that I'm reluctant to report because I'm concerned that the developers already know about them; Indeed, that's a good idea. We've been known to kill and eat reporters of known bugs. :) As for using a bugzilla or whatnot, I'm neutral. I find that I always end up fixing the bugs that people whine about the most anyway. Bug tracking systems tend to fill up quickly with not-quite-bugs that no one wants to look at. Andy ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] Question re: bug reporting/tracking/etc.
Andy Ross wrote Chris Metzler wrote: Sometimes I run into issues with FlightGear -- fgfs, data, scenery, whatever -- that I'm reluctant to report because I'm concerned that the developers already know about them; Indeed, that's a good idea. We've been known to kill and eat reporters of known bugs. :) As for using a bugzilla or whatnot, I'm neutral. I find that I always end up fixing the bugs that people whine about the most anyway. Bug tracking systems tend to fill up quickly with not-quite-bugs that no one wants to look at. Speaking of which, is there any progress on the Merlin propeller gearing issue? Regards Vivian ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Question re: bug reporting/tracking/etc.
On Tuesday 08 June 2004 23:01, Vivian Meazza wrote: Andy Ross wrote Chris Metzler wrote: Sometimes I run into issues with FlightGear -- fgfs, data, scenery, whatever -- that I'm reluctant to report because I'm concerned that the developers already know about them; Indeed, that's a good idea. We've been known to kill and eat reporters of known bugs. :) As for using a bugzilla or whatnot, I'm neutral. I find that I always end up fixing the bugs that people whine about the most anyway. Bug tracking systems tend to fill up quickly with not-quite-bugs that no one wants to look at. Speaking of which, is there any progress on the Merlin propeller gearing issue? Regards Vivian I was having similar problems with the Comper Swift geared prop and at one point I was getting the right power and rpm but at the wrong mixture and fuel flow rates - both seemed out by approx the same ratio as the prop gearing. I haven't looked at it for while but I'll try it in the next few days or so and see what the situation is with it now. LeeE ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
