On Sun, 03 Jul 2011 16:30:35 -0700, Bruce wrote in message
<4e10fb9b.7070...@celebritycc.com>:
> This is on Ubuntu 10.10, Nvidia GeForce 7300GS, with the Nvidia
> proprietary drivers.
..does it work with the nouveau driver? (It may work for
FG-git and may still be slower for everything else.)
Chris Wilkinson wrote:
> So if I keep custom and default separate, depending on which I start
> the sim with, one or the other will be absent (correct me if wrong).
When requesting a new scenery tile, FlightGear walks the scenery path
and will load the respective terrain tile from the first dire
> We currently have
> - 777-200
I have been trying the CRJ700 lately, and I think this might be an option
for an airliner as well - the cockpit has a nice visual quality, it comes
with engine start procedure, the AP seems to be well-tuned and free of
oscillatory behaviour and the night lights in t
If the scope is to show off the capabilities, I'd really consider the IAR-80
too.
Alessandro
> Date: Mon, 4 Jul 2011 12:50:57 +0300
> From: thorsten.i.r...@jyu.fi
> To: flightgear-devel@lists.sourceforge.net
> Subject: Re: [Flightgear-devel] Aircraft selection for 2.4.0
>
> > We currently have
On Monday, July 04, 2011 13:16:33 TDO_Brandano - wrote:
> If the scope is to show off the capabilities, I'd really consider the
> IAR-80 too.
>
> Alessandro
>
I agree, the Mig-15b and IAR-80 are really well done and the ASK13 is the best
glider imo.
Adrian
On Mon, Jul 4, 2011 at 11:50 AM, wrote:
>
> The AP has some trouble following a VOR radial or intercepting a
> glideslope, but then I don't really know any airliner (with the exception
> of the Concorde) which doesn't have any oddity in the AP.
Rest assured, the Concorde has its share of odditie
HI,
Have been digging into the source trying to better understand the
structure of the FG lighting system and constructs.
Keep coming across this function "toOsg" as in
bb.expandBy(toOsg(_lights[i].position));
or
fog->setColor(toOsg(fogColor));
and
light->setDiffuse(toOsg(l->scene_diffuse()));
Hi,
On Monday, July 04, 2011 16:38:26 John Wojnaroski wrote:
> HI,
>
> Have been digging into the source trying to better understand the
> structure of the FG lighting system and constructs.
>
> Keep coming across this function "toOsg" as in
> bb.expandBy(toOsg(_lights[i].position));
> or
> fo
On Monday 04 July 2011 08:38:26 John Wojnaroski wrote:
> toOsg
Converts SG Vectors to OSG Vectors
simgear/simgear/math/SGVec2.hxx
simgear/simgear/math/SGVec3.hxx
simgear/simgear/math/SGVec4.hxx
toOsg(const SGVec2d& v)
{ return osg::Vec2d(v[0], v[1]); }
--
toOsg(const SGVec2f& v)
{ return osg::V
Hi Torsten et al.,
As mentioned by others, I do believe that this is quite a nice selection. But,
I think that we should consider our original intentions for rotating the
aircraft selection. By changing the selection, we have a nice platform to
showcase some of the recent development and highli
He, he
Now it makes more sense.
Thanks guys
John
On Mon, 4 Jul 2011 09:57:32 -0600, Ron Jensen wrote:
> On Monda 04 July 2011 08:38:26 John Wojnaroski wrote:
>> toOsg
>
> Converts SG Vectors to OSG Vectors
>
> simgear/simgear/math/SGVec2.hxx
> simgear/simgear/math/SGVec3.hxx
> simgear/simgear/m
Hi,
On Mon, 2011-07-04 at 19:53 +0200, Durk Talsma wrote:
> > Let's start our traditional discussion about what aircraft should be in the
> > base package of the next release (2.4.0).
> >
> > We currently have
CRJ700-family?
signature.asc
Description: This is a digitally signed message part
--
On 30 Jun 2011, at 23:31, Torsten Dreyer wrote:
> Hi all,
>
> Our goal is to be able to present it later in several options of completeness:
> - complete aircraft
> - just the fuselage, wing and elevator removed
> - just the cabin, no wing or elevator, fuselage cut behind the rear window
> - the
Hi All,
I've been trying to fix bug 340
(http://code.google.com/p/flightgear-bugs/issues/detail?id=340), where
the VS KAP140 display in the c172p mysteriously stopped working about
a month ago.
To fix it partially, I've created a new AP filter converting from the
pressure-rate-target to a fpm val
Stuart wrote
>
> I've been trying to fix bug 340
> (http://code.google.com/p/flightgear-bugs/issues/detail?id=340), where
> the VS KAP140 display in the c172p mysteriously stopped working about
> a month ago.
>
> To fix it partially, I've created a new AP filter converting from the
> pressure-ra
> Anyone got any ideas?
Hi Stuart,
The correct usage would be
textranslate
vs-digit5
/autopilot/KAP140/settings/target-pressure-rate-fpm
0.1
1
1
0
0
textranslate
vs-digit4
/autopilot/KAP140/settings/target-pressure-rate-fpm
0
Typo!!! (see inline)
> Why?
> The order of computation is (example for digit2, propertyvalue=500):
> 1. get property value (500)
> 2. apply stepping ( 500 step 1000 = 0)
> 3. apply factor (0 * 0.0001 = 0 --> don't shift texture)
> or for propertyvalue=5500
> 1. get property value (500)
1. get prope
17 matches
Mail list logo