Hi all,
I just thought that displaying Flightgear and the aircraft version
numbers on the splash screen could help a bit the supporting effort we
do on the forum and the users list.
Thinking out loud,
Alexis
--
James Turner wrote:
On 27 Dec 2008, at 15:04, Tim Moore wrote:
Here's my workflow for using git with the FlightGear sources in CVS.
Note that
there are separate repositories for Fightgear, Simgear and the
Flightgear data.
This is inconvenient and there may a workaround using git
Hum experiencing some unexpected results.
I have reworked the engine parameters (the old files will definitely NOT work
on the current version of FlightGear).
I have also removed all form of SAS so that I can start working in Nasal (to
simulate hydraulics ...).
Here are the results.
a/ The
On 7 Jan 2009, at 19:05, Tim Moore wrote:
I like to fetch and then rebase my local work without merging; it
makes
it much easier to get the commits into CVS via git-cvsexportcommit.
When we move
to git and publish (sometimes) personal branches, I'll probably
switch back to
git-pull.
On 01/07/2009 01:19 PM, James Turner wrote:
On 7 Jan 2009, at 19:05, Tim Moore wrote:
I like to fetch and then rebase my local work without merging; it
makes
it much easier to get the commits into CVS via git-cvsexportcommit.
When we move
to git and publish (sometimes) personal
Hello !
In past couple of weeks I wrote GLSL-based shader for fluid surfaces and now
trying to deploy it into FlightGear.
As far as I know - there's no diference between solid and liquid surfaces
from FG/SG point of view. In other words
- rivers, lakes, ocean are a part of TerraGear scenery
On mercredi 07 janvier 2009, Vladimir Karmisin wrote:
Hello !
In past couple of weeks I wrote GLSL-based shader for fluid surfaces and
now trying to deploy it into FlightGear.
As far as I know - there's no diference between solid and liquid surfaces
from FG/SG point of view. In other words
-
0x006a3b59 in yasim::Airplane::compileFuselage
(this=0xc066688, f=0x7f84f00bf930) at src/FDM/YASim/Airplane.cpp:512
512 float segWgt = len*wid/segs;
(gdb) p segs
$1 = 0
(gdb) p *f
$3 = {front = {-13.604, 0, 1.3998}, back = {-13.604, 0,
1.3998}, width = 5.901,
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.
79::As of 1.9.0, changing helvetica-bold to helvetica in e.g.
Instruments/altimeter.xml causes the cockpit/panel loader to
segfault.
a) It would be nice if helvetica were supported.
b) Failing that, if helvetica is called for it would be nice to print
a warning and substitute some
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
12 matches
Mail list logo
