John Denker wrote:
One guy says not to report bugs in the old FGPiston,
because it has been fixed upstream.
Another guy say snot to report bugs in the new FGPiston,
because it is not committed code.
I guess that's one way to make sure there are no reported
bugs.
Fair enough, but make
I quote from
http://www.av8n.com/fly/fgfs/htm/bug-list.htm
80::As of mid-January 2008, there is a “new” version of
FGPiston.cpp floating around. It has not yet been committed to
FlightGear CVS. It gets rid of the specific problems mentioned in bug
79, replacing them with new and
John Denker wrote:
I quote from
http://www.av8n.com/fly/fgfs/htm/bug-list.htm
80::As of mid-January 2008, there is a “new” version of
FGPiston.cpp floating around. It has not yet been committed to
FlightGear CVS. It gets rid of the specific problems mentioned in bug
79,
* John Denker -- Friday 23 January 2009:
81::The FlightGear interface to the festival text-to-speech
server [...] doesn’t work [...] It hasn’t worked for years. I
have never heard of anyone actually using it.
Works for me since years.
m.
Melchior FRANZ wrote:
* John Denker -- Friday 23 January 2009:
81::The FlightGear interface to the festival text-to-speech
server [...] doesn???t work [...] It hasn???t worked for years. I
have never heard of anyone actually using it.
Works for me since years.
Someone who's using
One guy says not to report bugs in the old FGPiston,
because it has been fixed upstream.
Another guy say snot to report bugs in the new FGPiston,
because it is not committed code.
I guess that's one way to make sure there are no reported
bugs.
=
If anybody is interested in a
On Fri, 23 Jan 2009 07:29:25 -0700, John wrote in message
4979d445.3070...@av8n.com:
82::Choppy video and sound. I observe that things work fine when
the FlightGear window is the default size, 800x600. The frame rate is
in the range 45 to 50. However, if I enlarge the window even
On Jan 23, 2009, at 6:29 AM, John Denker wrote:
I quote from
81::The FlightGear interface to the festival text-to-speech
server is documented in section 5.6.2 of the getstart manual. I
observe that it doesn’t work (even though the festival server itself
works fine when FG is not
Ron == Ron Jensen writes:
81:: Consider the case where FlightGear is run with the
--disable-ai-models command line option.
It appears that some of the ai-related code continues to
run. You can easily verify by turning on log-level=info, in
which case you will see
Brian Schack wrote:
I've noticed that with AI traffic turned on, there is a constant
setting and resetting of the time accessed by
globals-get_time_params()
This sounds like a misplaced leading slash in a property for AI models
to me.
Erik
79::Let’s do an ordinary preflight runup in the c182rg. With the
prop control full forward, advance the throttle to 1700 rpm in
accordance with the POH checklist. Now pull the prop control full
back. In the Sim World as of 1.9.0, I observe the RPM drops from 1700
to 1400. This is highly
On Thu, 2009-01-08 at 13:49 -0700, John Denker wrote:
80::As of 1.9.0, in the c182rg on the runway at KSFO, I observe
that with the throttle wide open the MAP is 29.97. With the throttle
pulled back to 0.6, the MAP is still 29.97. This is wildly
unrealistic. Similar problems in the c172p
On 01/08/2009 04:59 PM, Ron Jensen wrote:
this has been
fixed up stream,
Wow. That's great. Perhaps I overlooked the announcement.
Will the fix be coming downstream anytime soon?
Is there any other news we should know about.
75:: As of 1.9.0, in the c182, the altimeter is not self-consistent.
There is an analog scale and a digital readout. It takes 10 clicks of
the Kollsman setting knob to move the digital readout ten hundredths
of an inch. It takes 14 or 15 clicks to rotate the analog scale the
corresponding amount.
On Wed, 2009-01-07 at 17:34 -0700, John Denker wrote:
77:: In the default c172p model, sitting on the runway at KSFO, at
full power the engine consumes about 78 pph of fuel. So far, so good.
Now stop the engine by pulling the mixture to cutoff. I observe that
the fuel flow, as reported by
In the code FuelFlow_gph is the canonical property, FuelFlow_pph is
only
calculated when we actually consume fuel. Slamming the mixture to 0 at
a high fuel flow rate causes consumption to stop leaving the
FuelFlow_pph value unable to update and stuck indicating a high value.
If you'll
Additional JSBsim FDM initialization-related bugs:
62:: I observe that in a JSBsim aircraft e.g. c182rg, after departing
the runway via the location-in-air menu item, there remains weight
on wheels. That is, the gear/wow property remains true. It appears
to remain true forever, long after
57:: Core feature: As of CVS 26 Dec 2008 I observe that at (say) KJFK
the Tower view and the Tower Look From view are conspicuously
broken. Other airports are broken, just less conspicuously so. This
appears to be the same problem previously discussed on the devel list
under the heading
On 25 Dec 2008, at 10:54, John Denker wrote:
52:: Core feature: Nav: Reversible ILS: Consider the following
scenario. In the 1.9.0 Sim World, you are on the KJFK ILS RWY 31R
snip
In the Real World, the active runway is determined based on wind
conditions (etc.) and the reversible ILS is
19 matches
Mail list logo