Hi,
is there somebody who can tell me, if there is a timer-function which I can use
for starting my listener in nasal? I created a script which shows the forces
and moments on an ASK21 as arrows. I know, there is a listener-command but it
do not work with properties in .../jsbim/aero/.. so I
* timo van Overbrüggen -- Monday 29 January 2007:
I know, there is a listener-command but it do not work with
properties in .../jsbim/aero/.. so I can not link the
listener-command to the aerodynamical forces.
listeners are triggered whenever something writes to the listened-to
property by
Martin Spott wrote:
Maik Justus wrote:
the ov10 has two files, which can not live together on Windows:
Aircraft/OV10/Models/CDF/OV10.xml
Aircraft/OV10/Models/CDF/ov10.xml
To my impression the upper-case letter file is a newer variant of the
other - and actually it's the one that gets
On 01/28/2007 04:43 PM, Martin Spott wrote:
[last week] I applied the patch which implemented your 'semi-transponder'
right the next day. Anything wrong with this ?
Definitely not wrong! Thanks!
Indeed this week's patches are dependent on last week's
patches. Only a few lines of last week's
Thanks Martin for the heads up. I updated my FlightGear and SimGear
sources and rebuilt and now the rendering is working very well.
I noticed one artifact that might be related to the heads up display,
shown here:
http://www.futuretek.com/flight/fgfs-screen-005.jpg
When I adjust the alpha
Rob Ratcliff wrote:
I noticed one artifact that might be related to the heads up display,
shown here:
http://www.futuretek.com/flight/fgfs-screen-005.jpg
Looks like US DHS has erected hard limits for airspace borders ;-)
Sorry, I have no idea. People often try to relate this do graphics
FYI: I'm using the latest Linux driver from NVIDIA. The details are
included below.
Martin Spott wrote:
Rob Ratcliff wrote:
I noticed one artifact that might be related to the heads up display,
shown here:
http://www.futuretek.com/flight/fgfs-screen-005.jpg
Looks like US DHS has
Martin Spott schrieb:
Rob Ratcliff wrote:
I noticed one artifact that might be related to the heads up display,
shown here:
http://www.futuretek.com/flight/fgfs-screen-005.jpg
Looks like US DHS has erected hard limits for airspace borders ;-)
Sorry, I have no idea. People
Does anybody else has that ugly broken sky with FG Osg ?
http://perso.orange.fr/GRTux/OSG-sky.jpg
Regards
--
Gérard
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get
Does anybody else has that ugly broken sky with FG Osg ?
http://perso.orange.fr/GRTux/OSG-sky.jpg
Regards
--
Gérard
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get
gh.robin wrote:
Does anybody else has that ugly broken sky with FG Osg ?
If you would have read previous EMails, you would already know the
answer ;-)
Martin.
BTW, a single posting would be sufficient.
--
Unix _IS_ user friendly - it's just selective about who its friends are !
I'll post a me too message here. But note that I have also seen this show
up in the v0.9.10 version on my same system (which is plib based.) I
suspect it could be a driver related issue, or something in the newest
nvidia driver exposes a state management bug in FlightGear?
This seems to be
On Mon 29 January 2007 18:16, Martin Spott wrote:
gh.robin wrote:
Does anybody else has that ugly broken sky with FG Osg ?
If you would have read previous EMails, you would already know the
answer ;-)
Martin.
BTW, a single posting would be sufficient.
Oh so..so..so..sorry i
Curtis Olson wrote:
I'll post a me too message here. But note that I have also seen this show
up in the v0.9.10 version on my same system (which is plib based.) I
suspect it could be a driver related issue, or something in the newest
nvidia driver exposes a state management bug in
Hi Fred,
On Monday 29 January 2007 10:03, Frederic Bouvier wrote:
The core of the fix is the change from a pointer to a reference to avoid
the deletion of the texture while the pointer still hold a non null value.
Thanks.
Greetings
Mathias
Hi,
On Monday 29 January 2007 18:32, Martin Spott wrote:
Curtis Olson wrote:
I'll post a me too message here. But note that I have also seen this
show up in the v0.9.10 version on my same system (which is plib based.)
I suspect it could be a driver related issue, or something in the
On 1/29/07, Mathias Fröhlich wrote:
Known bug. But it does not happen on my machines.
Even though, I have a machine with this effect reachable but not time yet
to
follow that bug ...
I only found that problem when a message box appears. It appears to happen
every time for you?
What airport is
* Melchior FRANZ -- Monday 29 January 2007:
The replacement would be a simple $FG_ROOT/Aircraft/Generic/annunciator.nas
Or $FG_ROOT/Aircraft/Instruments/annunciator.nas?
And it would look like the attached file (with some small
changes planned).
m.
var volts =
Hi Martin,
thanks,
Maik
Martin Spott schrieb am 29.01.2007 16:16:
Martin Spott wrote:
Maik Justus wrote:
the ov10 has two files, which can not live together on Windows:
Aircraft/OV10/Models/CDF/OV10.xml
Aircraft/OV10/Models/CDF/ov10.xml
To my impression the
Stuart Buchanan schrieb:
--- Mathias Fröhlich wrote:
Hi,
I need to have an other update to the openscenegraph tarball. For those
ones
not tracking cvs I have put together a tarball as usual. The key feature
I
need is the txf file font loader. That is with the time of packing that
On Mon 29 January 2007 19:11, Curtis Olson wrote:
On 1/29/07, Mathias Fröhlich wrote:
Known bug. But it does not happen on my machines.
Even though, I have a machine with this effect reachable but not time yet
to
follow that bug ...
I only found that problem when a message box
We're looking at using FlightGear as a framework for displaying images
and instrument displays to the pilot of a UAV. We might get real-time,
forward-looking video from the UAV, or we might get less frequent (every
second or two) snapshots from an array of cameras that cover a wider
field of
7000 ft above KSFO, daytime:
http://people.freebsd.org/~jylefort/fg-noon.png
As you can see, the thin cloud layer does not hide the
ground. However, after switching the time of day to night:
http://people.freebsd.org/~jylefort/fg-night.png
The airport and city lights only become visible
On Mon, 2007-01-29 at 19:27 +0100, Melchior FRANZ wrote:
* Melchior FRANZ -- Monday 29 January 2007:
The replacement would be a simple $FG_ROOT/Aircraft/Generic/annunciator.nas
Or $FG_ROOT/Aircraft/Instruments/annunciator.nas?
And it would look like the attached file (with some small
On Monday 29 January 2007 17:37, Melchior FRANZ wrote:
I'd like to remove the annunciator instrument from the C++
sources and replace it with a Nasal version.
Obviously, I agree. :-)
--
Roy Vegard Ovesen
-
Take Surveys.
On 1/29/07, Roy Vegard Ovesen wrote:
On Monday 29 January 2007 17:37, Melchior FRANZ wrote:
I'd like to remove the annunciator instrument from the C++
sources and replace it with a Nasal version.
Obviously, I agree. :-)
Hi Melchior,
I have an outside project (the ATC-710M FAA certified
following john's comment, have you developers ever think about a
switch over subversion?
just a question, no flames please...
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and
* Curtis Olson -- Monday 29 January 2007:
I don't have any problems with you proceeding, but if you don't
mind, could you let me know when the change is made so I can
double check the ATC-710M aircraft and make sure nothing got broke.
Thanks. That's done now. annunciator.[ch]xx removed from
On 01/29/2007 06:15 PM, Martin Spott wrote:
I don't think there's a real solution to this problems that adresses
all your concerns.
/All/ my concerns? As the saying goes: Do not let the perfect
be the enemy of the good.
I don't expect a SCM system to end world hunger. But there
are things
I had not planned to comment again on this issue. But today, I received
an AOPA e-mail that included a link to NTSB accident report Number:
DEN04FA043 concerning a FATAL accident involving a Cessna 206 on a
flight from Jeffco (KBJC) to just beyond the Medicine Bow VOR, where it
crashed into a
30 matches
Mail list logo
