David Megginson wrote:
> Frederic BOUVIER wrote:
>
> > I don't know for the original bug reporter, but I am using Windows and NVIDIA
> > if it is of any importance.
>
> That could matter -- I'm using Linux and NVIDIA. Do you have trouble with
> transparencies anywhere else? Do other people usi
* David Megginson -- Friday 12 March 2004 15:29:
> That's interesting -- is anyone else seeing this problem?
All needles are OK. The only bug that I see is the non-transparent
attitude 'needle': http://members.aon.at/mfranz/pa28.jpg
The SGI image seems to be OK, though (and I'm an SGI image expert
Frederic BOUVIER wrote:
I don't know for the original bug reporter, but I am using Windows and NVIDIA
if it is of any importance.
That could matter -- I'm using Linux and NVIDIA. Do you have trouble with
transparencies anywhere else? Do other people using Windows and NVIDIA see
a white rectan
David Megginson wrote:
> Frederic Bouvier wrote:
>
> >>Was this in PLIB 1.6, again? The alpha transparency is fine using the CVS
>
> > I am using the CVS plib and I am seeing this bug.
>
> That's interesting -- is anyone else seeing this problem?
I don't know for the original bug reporter, but
David Megginson wrote:
Frederic Bouvier wrote:
Was this in PLIB 1.6, again? The alpha transparency is fine using
the CVS
I am using the CVS plib and I am seeing this bug.
That's interesting -- is anyone else seeing this problem?
No, not for IRIX, not for Linux.
Erik
___
Frederic Bouvier wrote:
Was this in PLIB 1.6, again? The alpha transparency is fine using the CVS
I am using the CVS plib and I am seeing this bug.
That's interesting -- is anyone else seeing this problem?
All the best,
David
___
Flightgear-devel ma
On Thu, 11 Mar 2004 20:07:10 -0500, David Megginson
<[EMAIL PROTECTED]> wrote:
Was this in PLIB 1.6, again? The alpha transparency is fine using the
CVS plib.
I'm pretty sure it was CVS plib.
--
Roy Vegard Ovesen
___
Flightgear-devel mailing list
[EM
David Megginson wrote:
> Roy Vegard Ovesen wrote:
>
> > Another thing that I noticed about the pa28 panel was the plane in the
> > TC was not transparent where it should be. The rgb file did have an
> > alpha channel but because the file was only 256 colors the alpha channel
> > was not transparen
Roy Vegard Ovesen wrote:
I too, experienced this, no needles in the instruments. I use a NVidia
card under Cygwin. After installing the cvs version of plib, the needles
appeared (I used to have plib 1.6.0).
Ah, yes -- the last official PLIB version has a bug (I can hardly consider
it a feature)
On Thu, 11 Mar 2004, David Megginson wrote:
> I used geometry for the needles, and they must just be too narrow to show
> up. It's strange, because I also use Linux+NVIDIA (GeForce2Go), and the
> needles do show up on my system at 1600x1200.
>
> In any case, I'll be switching to bigger quads with
On Thu, 11 Mar 2004 17:10:30 +, David Luff <[EMAIL PROTECTED]>
wrote:
One bug though - I don't see the instrument needles under Linux with an
NVidia card. I thought you simply hadn't done them, until I saw them
under Cygwin with an ATI card. I see the large tilting plane in the
turn co-o
David Luff wrote:
I'll second that - it really is good. It looks really good, and at high
resolutions the frame rate is much better than the default - I've seen 60
(pa28) vs. 30 (c172) at some locations and resolutions.
The old (2D) panel code seemed to be the real killer, since I'm using much
m
Martin Spott writes:
> David Megginson wrote:
> > Update of /var/cvs/FlightGear-0.9/data/Aircraft/pa28-161/Models
> > In directory baron:/tmp/cvs-serv6690/Aircraft/pa28-161/Models
>
> > Modified Files:
> > pa28-161.ac panel.rgb
> > Added Files:
> > bench-back.rgb glareshield.rgb
> > Log
Martin Spott wrote:
This aircraft gets really nice.
Thanks. The big breakthrough was my finally learning to use Blender to make
the textures (such as the panel plastics and screws) as well as the geometry
-- using a good 3D modeller with a bit of lighting can make even a
ham-fisted dolt like m
David Megginson wrote:
> Update of /var/cvs/FlightGear-0.9/data/Aircraft/pa28-161/Models
> In directory baron:/tmp/cvs-serv6690/Aircraft/pa28-161/Models
> Modified Files:
> pa28-161.ac panel.rgb
> Added Files:
> bench-back.rgb glareshield.rgb
> Log Message:
> Added textures for the b
It's fixed in CVS now... Thanks !
--
Jorge Van Hemelryck
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
On Fri, 27 Feb 2004 17:37:48 +0100 (CET)
Frederic BOUVIER wrote:
> Erik Hofman wrote:
>
> > David Megginson wrote:
> > > Martin Spott wrote:
> > >
> > >> Great idea - unfortunately 'fgfs' now dies with a segmentation fault
> > >> just a split second after the FlightGear window appears (Linux),
>
On Friday 27 February 2004 17:25, Curtis L. Olson wrote:
> David Luff wrote:
> > Whilst on the subject of initialisation order, currently the tile manager
> > gets initialised before an initial position is set. This means that it
> > loads a set of tiles centered on lat/lon of 0,0, and then loads
On Friday 27 February 2004 14:02, David Megginson wrote:
> Erik Hofman wrote:
> > Modified Files:
> > radar_misc.rgb
> > Log Message:
> > Add support for a storm blib
>
> Excellent.
>
> As far as I know, civilian airliners carry radar that is capable only of
> detecting weather, not small thing
On Fri, 27 Feb 2004 11:25:00 -0600,
"Curtis L. Olson" <[EMAIL PROTECTED]> wrote in message
<[EMAIL PROTECTED]>:
> David Luff wrote:
> > Whilst on the subject of initialisation order, currently the tile
> > manager gets initialised before an initial position is set. This
> > means that it loads
"Curtis L. Olson" said:
> David Luff wrote:
> > Whilst on the subject of initialisation order, currently the tile manager
> > gets initialised before an initial position is set. This means that it
> > loads a set of tiles centered on lat/lon of 0,0, and then loads a set of
> > tiles at the correc
David Luff wrote:
Whilst on the subject of initialisation order, currently the tile manager
gets initialised before an initial position is set. This means that it
loads a set of tiles centered on lat/lon of 0,0, and then loads a set of
tiles at the correct location. In conditions of limited visib
On 2/27/04 at 11:56 AM David Megginson wrote:
>The way to fix all this is to decouple the subsystems using properties so
>that there is no init-order dependency (and no need for unrelated
>subsystems
>to know about other subsystems' internals), but I see at least 4-8 hours'
>work sorting out t
Martin Spott wrote:
The idea is good - don't dump it,
Thanks, but it's going to be too much work for now -- there are some bizarre
interdependencies. For example, FGInterface, the FDM base class that should
know nothing about 3D models, pokes around inside the aircraft model when
the FDM is in
Erik Hofman wrote:
> David Megginson wrote:
> > Martin Spott wrote:
> >
> >> Great idea - unfortunately 'fgfs' now dies with a segmentation fault
> >> just a split second after the FlightGear window appears (Linux),
> >
> >
> > Yes, I was using the wrong executable to test it. Give me about an
David Megginson wrote:
> Martin Spott wrote:
>> Great idea - unfortunately 'fgfs' now dies with a segmentation fault
>> just a split second after the FlightGear window appears (Linux),
> Yes, I was using the wrong executable to test it. Give me about an hour,
> and I'll revert if I cannot fix t
David Megginson wrote:
Martin Spott wrote:
Great idea - unfortunately 'fgfs' now dies with a segmentation fault
just a split second after the FlightGear window appears (Linux),
Yes, I was using the wrong executable to test it. Give me about an
hour, and I'll revert if I cannot fix the problem.
Martin Spott wrote:
Great idea - unfortunately 'fgfs' now dies with a segmentation fault
just a split second after the FlightGear window appears (Linux),
Yes, I was using the wrong executable to test it. Give me about an hour,
and I'll revert if I cannot fix the problem.
All the best,
David
_
David Megginson wrote:
> Update of /var/cvs/FlightGear-0.9/source/src/Main
> In directory baron:/tmp/cvs-serv25641/src/Main
> Modified Files:
> fg_init.cxx main.cxx
> Log Message:
> Add the aircraft model, model manager, view manager, and scenery
> manager to the standard subsystem collecti
Erik Hofman wrote:
David Megginson wrote:
Erik Hofman wrote:
I know that in Europe they recently added a requirement for collision
detection after two civilian aircraft hit each other when the ATC had
given inappropriate directions.
Is that a requirement for TCAS, or for something else in add
On Freitag, 27. Februar 2004 15:40, David Megginson wrote:
> That said, I'm sorry to hear that the Swiss controller died. Was it in any
> way related to the accident?
It was not clear up to the yesterday evening news.
Have not seen/heared news from today.
Greetings
Mathias
--
Mathias
David Megginson wrote:
Erik Hofman wrote:
I know that in Europe they recently added a requirement for collision
detection after two civilian aircraft hit each other when the ATC had
given inappropriate directions.
Is that a requirement for TCAS, or for something else in addition to TCAS?
Every
Erik Hofman wrote:
I know that in Europe they recently added a requirement for collision
detection after two civilian aircraft hit each other when the ATC had
given inappropriate directions.
Is that a requirement for TCAS, or for something else in addition to TCAS?
The copilot on one of those p
David Megginson wrote:
Erik Hofman wrote:
Modified Files:
radar_misc.rgb Log Message:
Add support for a storm blib
Excellent.
As far as I know, civilian airliners carry radar that is capable only of
detecting weather, not small things like aircraft. They also use a
separate radar system
Erik Hofman wrote:
Modified Files:
radar_misc.rgb
Log Message:
Add support for a storm blib
Excellent.
As far as I know, civilian airliners carry radar that is capable only of
detecting weather, not small things like aircraft. They also use a separate
radar system for ground separation (the
Erik Hofman wrote:
> Update of /var/cvs/FlightGear-0.9/FlightGear/src/Environment
> In directory baron:/tmp/cvs-serv510
> Modified Files:
> environment_ctrl.cxx environment_ctrl.hxx
> Log Message:
> Add support for a proxy server when retreiving metar data.
> Index: environment_ctrl.cxx
>
* Martin Spott -- Thursday 26 February 2004 12:45:
> I thank you very much for implementing real weather and proxy support.
> This is really a great improvement !
I'm quite happy about it, too. It really gives a special feeling to
start from ULLI with the real, actual weather from there, or to fly
Melchior FRANZ wrote:
* Martin Spott -- Thursday 26 February 2004 12:45:
I thank you very much for implementing real weather and proxy support.
This is really a great improvement !
I'm quite happy about it, too. It really gives a special feeling to
start from ULLI with the real, actual weather f
* Melchior FRANZ -- Thursday 26 February 2004 12:59:
> Airport-Id: EFHK
> Report time:2004/2/26 11:20 UTC
> 3.5 km W2.2 US-miles W
> Wind: from the SSE (160°) at 24.1 km/h13 kt = 15 mph = 6.7
Martin Spott wrote:
Erik Hofman wrote:
Add an option to define the proxy settings (used by metar data
fetching only at this time). Usage: --proxy=user:[EMAIL PROTECTED]:port
The notation works for me - as long as I don't have to use proxy
authorization. Thanks,
If authentication support is prope
Erik Hofman wrote:
> Update of /var/cvs/FlightGear-0.9/FlightGear/src/Main
> In directory baron:/tmp/cvs-serv14944
> Modified Files:
> options.cxx
> Log Message:
> Add an option to define the proxy settings (used by metar data
> fetching only at this time). Usage: --proxy=user:[EMAIL PROTEC
"Curtis L. Olson" wrote:
> Update of /var/cvs/FlightGear-0.9/source/src/Environment
> In directory baron:/tmp/cvs-serv19928
> Modified Files:
> environment_ctrl.cxx environment_ctrl.hxx
> Log Message:
> For weather fetching from the noaa.gov site: If the closest station hasn't
> changed, w
Martin Spott wrote:
Very wise :-) I'd be a bit concerned that NOAA might close their
service if they realize an increasing amount of requests from the same
host for the same airfield within a too short timeframe.
Wouldn't it make sense to evaluate the timestamp of each dataset and
delay the next
* Norman Vine -- Monday 23 February 2004 20:55:
> Melchior FRANZ writes:
> > http://weather.noaa.gov/data/nsd_.gz
>
> AFAIK this is same as the link I posted earlier with a different sorting
Oh, yes. Missed that, sorry. Seems that 'mine' is sorted by ICAO codes,
and 'yours' by ... umm ... b
Melchior FRANZ writes:
>
> * Curtis L. Olson -- Monday 23 February 2004 18:27:
> > Any one know where we can get current and definitive information?
>
> Here is a list of weather stations with ICAO ids. But it's not obvious
> if all of these do also provide metar reports:
>
> http://weather.no
* Curtis L. Olson -- Monday 23 February 2004 18:27:
> Any one know where we can get current and definitive information?
Here is a list of weather stations with ICAO ids. But it's not obvious
if all of these do also provide metar reports:
http://weather.noaa.gov/data/nsd_.gz
m.
___
* Curtis L. Olson -- Monday 23 February 2004 18:27:
> There are definitely many weather stations
> not colocated with airports (or at least that don't have corresponding
> airports in our database.)
Ahh, yes. And my assumption that only four letter ids is apparently wrong.
There are stations wi
Curtis L. Olson writes:
> David Megginson wrote:
> > Curtis L. Olson wrote:
> >
> >> A simple list of id's of metar stations. We can use this list to mark
> >> which airports have corresponding metar data so we don't flood the
> >> noaa site
> >> with bogus queries.
> >
> >
> > It might be a g
David Megginson wrote:
Curtis L. Olson wrote:
A simple list of id's of metar stations. We can use this list to mark
which airports have corresponding metar data so we don't flood the
noaa site
with bogus queries.
It might be a good idea actually to add lat/lon/elev of each station to
the list
Curtis L. Olson wrote:
A simple list of id's of metar stations. We can use this list to mark
which airports have corresponding metar data so we don't flood the noaa site
with bogus queries.
It might be a good idea actually to add lat/lon/elev of each station to the
list, and to use it instead of
On Thu, 12 Feb 2004 15:36:13 -0500
Josh Babcock <[EMAIL PROTECTED]> wrote:
This has all got me thinking a bit. This subject seems to come up
quite a bit, and frankly I have found it a dificult problem too. In
addition, there are some related things that can get hard as well
like placing the w
This has all got me thinking a bit. This subject seems to come up quite
a bit, and frankly I have found it a dificult problem too. In addition,
there are some related things that can get hard as well like placing the
wheels right on the ground, and getting the landing gear elements for
wingti
"Jon S Berndt" <[EMAIL PROTECTED]> wrote:
> Is there now a difference in the way that JSBSim and YASim match up
> the 3D model with the FDM?
No, the discussion is only about placement of the 3D model vs. some FDM
reference point, I think (but I'm not absolutely shure if there _might_
be a hidden
"Jim Wilson" <[EMAIL PROTECTED]> wrote:
> Trust me, I've been all over every line of the viewer code. You aren't really
> seeing what you think you are. It just looks that way.
Jim, do you want to tell me I'm blind ? I must admit that I probably
never looked at the code but I can assure you tha
On Thu, 12 Feb 2004 19:50:48 -
"Jim Wilson" <[EMAIL PROTECTED]> wrote:
You actually want to be very exact about matching the model to the
FDM origin.
...
Jim (or someone ... *anyone*):
Could you summarize the argument taking place here? I seem to only be
getting parts of it - I guess I did
Vivian Meazza <[EMAIL PROTECTED]> said:
> I was only using the CofG (and approximately at that) as a better visual
> reference than the nose. I was only concerned to make things look right. I'm
> sure that the FDMs are quite correct, or the models wouldn't fly very well,
> if at all. I take it the
Martin Spott <[EMAIL PROTECTED]> said:
> You _might_ be right, but in the case we are talking abouth things are
> different. For example use the "Tower view" and zoom enough to get the
> details. Take off and stay 100 ft above the ground. Now push the
> elevator violently aband you'll notice that
Andy wrote
>
>
> Martin Spott wrote:
> > Jim Wilson wrote:
> > > If the camera is tracking the nose, then it moves up and down as
> > > well with the nose. This creates the _illusion_ that the rest of
> > > the aircraft (and of the scene for that matter) is
> moving, and the
> > > nose is r
Andy Ross <[EMAIL PROTECTED]> wrote:
> Martin Spott wrote:
>> Jim Wilson wrote:
>> > If the camera is tracking the nose, then it moves up and down as
>> > well with the nose. This creates the _illusion_ that the rest of
>> > the aircraft (and of the scene for that matter) is moving, and the
>> > n
Martin Spott wrote:
> Jim Wilson wrote:
> > If the camera is tracking the nose, then it moves up and down as
> > well with the nose. This creates the _illusion_ that the rest of
> > the aircraft (and of the scene for that matter) is moving, and the
> > nose is remaining stationary when in fact it
"Jim Wilson" <[EMAIL PROTECTED]> wrote:
> David Megginson <[EMAIL PROTECTED]> said:
>> Martin Spott wrote:
>> > At least in the _outside_ views the PA-28 still rotates around its nose
>> > after the recent changes,
>>
>> That seemed funny to me as well, but when I looked from the outside view, it
David Megginson <[EMAIL PROTECTED]> said:
> Martin Spott wrote:
>
> > I can't withstand the impression that changing the _camera_ position
> > didn't lead to the intended success. Take a simple stick and rotate it
> > around one of its ends. For an observer the phenomenon is still the
> > same ev
Martin Spott wrote:
I can't withstand the impression that changing the _camera_ position
didn't lead to the intended success. Take a simple stick and rotate it
around one of its ends. For an observer the phenomenon is still the
same even when he changes his viewpoint.
If you want to rotate the sti
David Megginson <[EMAIL PROTECTED]> wrote:
> Update of /var/cvs/FlightGear-0.9/data/Aircraft/pa28-161
> In directory baron:/tmp/cvs-serv12589
> Modified Files:
> pa28-161-yasim-set.xml
> Log Message:
> Change camera position so that model doesn't rotate around the nose.
I can't withstand t
-0.7
That should do the trick :)
David Megginson wrote:
Jim Wilson wrote:
Actually, it isn't that. It is just the location that the "camera"
points to.
You don't want it pointing at the nose. So add the entry below to the
external views in your xml wrapper that track the plane. The val
Jim Wilson wrote:
I wonder if we can model the broken air vent door on the pilot's side that
blows -35 degC air on my feet when I'm flying in the winter.
It's already there (parameter: --frostbite=mins where mins is number of
minutes before you lose your toes). With that all you need is an old
a
David Megginson <[EMAIL PROTECTED]> said:
> I wonder if we can model the broken air vent door on the pilot's side that
> blows -35 degC air on my feet when I'm flying in the winter.
It's already there (parameter: --frostbite=mins where mins is number of
minutes before you lose your toes). With
David Megginson wrote:
Thanks -- that did the trick. The plane is actually flying well, and
I'm starting to feel tempted to go back and do more work to make it a
fully-usable alternative to the [EMAIL PROTECTED]@#na 172 -- after all, it would be
nice for users to be able to fly a light single w
Jim Wilson wrote:
Actually, it isn't that. It is just the location that the "camera" points to.
You don't want it pointing at the nose. So add the entry below to the
external views in your xml wrapper that track the plane. The value is the
distance in meters from the FDM reference point (the n
On Sun, 08 Feb 2004 21:31:30 +0100,
Erik Hofman <[EMAIL PROTECTED]> wrote in message
<[EMAIL PROTECTED]>:
> Martin Spott wrote:
>
> > Anyway: Thanks for this very nice addition to the FlightGear hangar,
>
> I'm already investigating for a larger home airport. KSFO isn't going
> to take it anym
David Megginson <[EMAIL PROTECTED]> said:
> Martin Spott wrote:
>
> > Hello David, I like your PA-28 very much, but I can't resist to note
> > that there is one 'feature' that is really annoying (I must admit that
> > this word is a bit too strong in this context !):
> > At least in the outside v
Martin Spott wrote:
Anyway: Thanks for this very nice addition to the FlightGear hangar,
I'm already investigating for a larger home airport. KSFO isn't going to
take it anymore.
Erik
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.fli
Hello,
"Curtis L. Olson" <[EMAIL PROTECTED]> wrote:
> Update of /var/cvs/FlightGear-0.9/data/Aircraft/Hunter/Models
> In directory baron:/tmp/cvs-serv1093
> Added Files:
> pilots-notes.txt
> Log Message:
> Missed one important file.
> The following additional keyboard controls have been i
> > Hello David, I like your PA-28 very much, but I can't resist to note
> > that there is one 'feature' that is really annoying (I must admit that
> > this word is a bit too strong in this context !):
> > At least in the outside views the aircraft rotate around its nose.
> > It's difficult to tell
Martin Spott wrote:
Hello David, I like your PA-28 very much, but I can't resist to note
that there is one 'feature' that is really annoying (I must admit that
this word is a bit too strong in this context !):
At least in the outside views the aircraft rotate around its nose.
It's difficult to tel
David Megginson <[EMAIL PROTECTED]> wrote:
> Update of /var/cvs/FlightGear-0.9/data/Aircraft/pa28-161/Models
> In directory baron:/tmp/cvs-serv27479
> Modified Files:
> pa28-161.ac
> Added Files:
> pa28-161-01.rgb panel-tex01.rgb panel-tex02.rgb
> panel-tex03.rgb panel.rgb
> L
Am Montag, 2. Februar 2004 23:38 schrieb Melchior FRANZ:
> Who? The Empress? She was actually called Sisi ...
http://dict.leo.org/?search=sissy&lang=de
> That a solution for non-US-keyboards is necessary was never argued about,
> and actually discussed a few times already. It's just that nobody f
* Ronny Standtke -- Monday 02 February 2004 23:01:
> But dont be a sissy,
Who? The Empress? She was actually called Sisi ...
> I am a developer myself [...] and the German keyboard never troubled me
> while programming.
But not a TeX programmer, right? :-}
> > But thats quite OT, because
> The places where they put "unimportant" things like @, [, ], {, }, \,
> etc. Face it: German keyboards may be suitable for secretaries or poets,
> but they are a royal pain for technical stuff like programming.
If you look back in history (damn, I'm not that old) keyboards _have_ been
designed
* Ronny Standtke -- Monday 02 February 2004 18:46:
> What exactly do you despise about the layout of German kezboards :-)
The places where they put "unimportant" things like @, [, ], {, }, \,
etc. Face it: German keyboards may be suitable for secretaries or poets,
but they are a royal pain for tec
Am Montag, 2. Februar 2004 11:51 schrieb Melchior FRANZ:
> Don't know. I'm Austrian.
> No, seriously: I can't stand German keyboards. Their layout is brain-dead,
> so I'm using an US-American one. I'd say that it's up to those who suffer
> the most to fix the unfortunate situation. (I use the compo
* Martin Spott -- Monday 02 February 2004 11:25:
> I appreciate your effort - on the other hand I feel required to note,
> that there are still unsolved issues because some of the key controls
> work different on different national keyboards.
I know. But having documentation about the current stat
Erik Hofman <[EMAIL PROTECTED]> wrote:
> Update of /var/cvs/FlightGear-0.9/data/Docs/keyboard
> In directory baron:/tmp/cvs-serv21524/keyboard
> Added Files:
> VERSION map.pdf map.tex
> Log Message:
> Add a per aircraft keyboard refference
I appreciate your effort - on the other hand I fee
Martin Spott wrote:
Update of /var/cvs/FlightGear-0.9/data/Aircraft/f16/Models
In directory baron:/tmp/cvs-serv20447
Modified Files:
f16.ac f16.xml
Log Message:
Add gear animation
Woohooo !
I take this as a compliment.
Thanks!
Erik
___
Flightgear-d
> Update of /var/cvs/FlightGear-0.9/data/Aircraft/f16/Models
> In directory baron:/tmp/cvs-serv20447
> Modified Files:
> f16.ac f16.xml
> Log Message:
> Add gear animation
Woohooo !
Martin.
--
Unix _IS_ user friendly - it's just selective about who its friends are !
Hello Erik,
Erik Hofman <[EMAIL PROTECTED]> wrote:
> +href="http://www.flightgear.org/default.css";>
[...]
> + http://www.flightgear.org/";> src="http://www.flightgear.org/images/fglogosm.jpg"; alt="">
You probably might want to use references _without_ hostname here -
like it's already
Andy Ross writes:
> Sure, there's a print() function which uses SG_LOG; for exactly this
> purpose. There's even a fancy dump() method on a property node that
> you can use to dump a property tree to the console.
Ok, thanks, I eventually found it. Quite useful, thanks. :-)
> It turns out to be
Curtis L. Olson wrote:
> It appears (to me) to be a property setting problem. Andy, does
> nasal have the ability to dump console output for temporary
> debugging?
Sure, there's a print() function which uses SG_LOG; for exactly this
purpose. There's even a fancy dump() method on a property node
Curt wrote:
> select = sel.getChild("engine", i);
> Could there be a bug in this form of getChild()?
Heh, bingo. That was exactly it. See the other post for notes.
Andy
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightge
Andy Ross writes:
> Curtis L. Olson wrote:
> > David, (Andy?)
> >
> > It appears that in the latest cvs, we have lost the ability to control
> > the engines independently.
>
> This one is mine. The recent Nasal stuff contains a rework of the
> engine handling to allow for arbitrary numbers of eng
Andy Ross writes:
> Curtis L. Olson wrote:
> > David, (Andy?)
> >
> > It appears that in the latest cvs, we have lost the ability to control
> > the engines independently.
>
> This one is mine. The recent Nasal stuff contains a rework of the
> engine handling to allow for arbitrary numbers of eng
Jon S Berndt writes:
> On Mon, 29 Dec 2003 15:49:30 -0600
> "Curtis L. Olson" <[EMAIL PROTECTED]> wrote:
> >David, (Andy?)
> >
> >It appears that in the latest cvs, we have lost the ability to control
> >the engines independently. Previously you could type
> > ... etc. to select an engine. Th
Andy Ross writes:
> Curtis L. Olson wrote:
> > David, (Andy?)
> >
> > It appears that in the latest cvs, we have lost the ability to control
> > the engines independently.
>
> This one is mine. The recent Nasal stuff contains a rework of the
> engine handling to allow for arbitrary numbers of eng
On Mon, 29 Dec 2003 15:49:30 -0600
"Curtis L. Olson" <[EMAIL PROTECTED]> wrote:
David, (Andy?)
It appears that in the latest cvs, we have lost the ability to control
the engines independently. Previously you could type
... etc. to select an engine. Then '{' and '}'
would select the magnetos.
Curtis L. Olson wrote:
> David, (Andy?)
>
> It appears that in the latest cvs, we have lost the ability to control
> the engines independently.
This one is mine. The recent Nasal stuff contains a rework of the
engine handling to allow for arbitrary numbers of engines, and avoid
the "why are there
David, (Andy?)
It appears that in the latest cvs, we have lost the ability to control
the engines independently. Previously you could type
... etc. to select an engine. Then '{' and '}'
would select the magnetos. Finally, "space bar" would kick in the
starter motor for as long as it was depr
Martin Spott wrote:
Erik Hofman <[EMAIL PROTECTED]> wrote:
Update of /var/cvs/FlightGear-0.9/data/Models/Geometry
In directory baron:/tmp/cvs-serv27779
Added Files:
frighter.ac
Shou?ld this ship frighten us ? ;-)
Only if it's directly above you ...
Erik
___
Erik Hofman <[EMAIL PROTECTED]> wrote:
> Update of /var/cvs/FlightGear-0.9/data/Models/Geometry
> In directory baron:/tmp/cvs-serv27779
> Added Files:
> frighter.ac
Shouöld this ship frighten us ? ;-)
Martin.
--
Unix _IS_ user friendly - it's just selective about who its friends are !
David,
As for the STL headers, use these instead:
#include STL_IOSTREAM
#include STL_IOMANIP
There are actually many files that are not using these variables from
simgear/compiler.h. It looks like the ATC code and JSBSim are handling
this on their own instead of letting Simgear do it (though
David,
There's a sprintf in Rotor.cpp and compilation is failing with the stdio.h
include removed.
Best,
Jim
David Megginson <[EMAIL PROTECTED]> said:
> Index: Rotor.cpp
> ===
> RCS file: /var/cvs/FlightGear-0.9/source/src/FDM/YAS
301 - 400 of 591 matches
Mail list logo
