On 12 Apr 2010, at 13:07, Erik Hofman wrote:
Log Message:
Replace Devid Megginsons version of the j3cub with the excellent work of
karla from the forum. Signed off by David.
Woo-hoo!
This is an awesome model, about to fire it up and take it for a spin.
Thanks to all involved for their
Hi,
Woo-hoo!
This is an awesome model, about to fire it up and take it
for a spin.
Thanks to all involved for their hard work, the results
speak for themselves I'd say.
James
Yes, great little aircraft, very accurate modelled! Now only a PA18 Super Cub
with the same qualitity
Hi Stuart,
Stuart Buchanan wrote:
Update of /var/cvs/FlightGear-0.9/data/Aircraft/c172p/Models/Liveries
In directory baron.flightgear.org:/tmp/cvs-serv9716/Models/Liveries
Modified Files:
fuselage-normal.png tail-normal.png wing-normal.png
Log Message:
Updated normal mapping with
Martin Spott wrote:
Erik
Erik Hofman wrote:
Update of /var/cvs/FlightGear-0.9/data/Models/Airport
In directory baron.flightgear.org:/tmp/cvs-serv32368
Modified Files:
B-1200.ac BAK-12-0.ac Schopf_F110.ac TowBear_TT.ac
default01.rgb eddf_lamp_t2.xml radar.ac tacan.ac
Log
Erik
Erik Hofman wrote:
Update of /var/cvs/FlightGear-0.9/data/Models/Airport
In directory baron.flightgear.org:/tmp/cvs-serv32368
Modified Files:
B-1200.ac BAK-12-0.ac Schopf_F110.ac TowBear_TT.ac
default01.rgb eddf_lamp_t2.xml radar.ac tacan.ac
Log Message:
fix line
On 24 Feb 2010, at 22:15, Torsten Dreyer wrote:
logic filters use well known conditions to drive output properties. Example
for bax = baz (foo | bar).
Nice!
Regards,
James
--
Download Intel#174; Parallel Studio
On Thursday 25 Feb 2010, James Turner wrote:
On 24 Feb 2010, at 22:15, Torsten Dreyer wrote:
logic filters use well known conditions to drive output
properties. Example for bax = baz (foo | bar).
Nice!
Regards,
James
Yes, a very useful addition.
LeeE
Welcome back, Frederic!
Where have you been so long? :-)
still in work: http://www.hoerbird.net/galerie.html
But already done: http://www.hoerbird.net/reisen.html
__
Do You Yahoo!?
Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden
back.
Alan
--
From: Heiko Schulz aeitsch...@yahoo.de
Sent: Sunday, January 17, 2010 3:15 PM
To: FlightGear developers discussions
flightgear-devel@lists.sourceforge.net
Subject: [Flightgear-devel] [Flightgear-cvslogs] CVS: source
configure.ac
Erik, we may need to discuss Santa theology on the developers list here.
Are you just making this stuff up?
:-)
Curt.
On Sat, Jan 16, 2010 at 8:37 AM, Erik Hofman
ehof...@baron.flightgear.orgwrote:
Update of /var/cvs/FlightGear-0.9/data/Aircraft/santa/Models/Effects
In directory
Curtis Olson wrote:
Erik, we may need to discuss Santa theology on the developers list
here. Are you just making this stuff up?
It's true, it's really true! I saw it myself ... once.
I think.
Erik
--
Throughout its
Hi,
I'd always got the crash when SGProp trying to delete /sim/logging/classes.
So this must be the root cause of the crash (sound manager code is innocent).
Now it quits without weird crash or malloc errors.
Thanks!!
Tat
On Jan 1, 2010, at 2:32 AM, Martin Spott wrote:
Tim Moore wrote:
Emmanuel Baranger wrote:
Update of /var/cvs/FlightGear-0.9/data/Aircraft/HM-14
In directory baron.flightgear.org:/tmp/cvs-serv28022/HM-14
Log Message:
Directory /var/cvs/FlightGear-0.9/data/Aircraft/HM-14 added to the repository
Oh yes, _that_ is a nice one !
Folks, forget everything
Tim Moore wrote:
Update of /var/cvs/FlightGear-0.9/source/src/Main
In directory baron.flightgear.org:/tmp/cvs-serv17684/src/Main
Modified Files:
fg_props.cxx
Log Message:
Move getLoggingClasses() result buffer to file level.
Getting it out of the function fixes some corruption
James Turner wrote:
Update of /var/cvs/FlightGear-0.9/source/src/Navaids
In directory baron.flightgear.org:/tmp/cvs-serv28367/src/Navaids
Modified Files:
navdb.cxx navrecord.cxx
Log Message:
Fix for Martin: tolerate runway-associated navaids with a bogus ICAO/runway
ident.
On 9 Dec 2009, at 00:25, Sébastien MARQUE wrote:
I've got an suggestion for the gps code: a command nearest-coord (or
better name) which would give nearest navaid for arbitrary coordinates,
given by scratch/longitude-deg and scratch/latitude-deg. It will allow
to implement a simple
On 8 Dec 2009, at 20:18, Alexis Bory wrote:
- Sebastien Marque: Turnpoint is managed using OBS mode, the route is still
managed by zkv500's Nasal, only obs mode is available
(seehttp://wiki.flightgear.org/index.php/GPS_internals). It should be leg
mode but I can't get it to work as I
Hi James,
I'm sure this is not a problem with the gps code but only with the
zkv500 code, because it manages itself the route (it has its own route
manager), so the gps code just can't use leg as it doesn't know the
entry point of the leg.
I'm working on it, transferring the route management
Alex Romosan wrote:
James Turner j...@baron.flightgear.org writes:
Log Message:
Fix displaced threshold handling when using in-scenery definitions of
runways.
[...]
i submitted a patch for this a while ago. if you actually add
_displ_thresh then the aircraft gets positioned at the
Vivian Meazza wrote:
Update of /var/cvs/FlightGear-0.9/data/Scenery/Objects/w130n30/w123n37
In directory baron.flightgear.org:/tmp/cvs-serv13878
Modified Files:
942050.stg
Added Files:
KSFO_AirTrain.ac KSFO_DomesticGarage.ac KSFO_GarageA.ac
On 12/05/2009 01:35 PM, Martin Spott wrote:
The displaced threshold is relevant for landing, in the sense of don't
touch ground before this line, maybe due to noise abatement measures,
safety or some other reasons.
Exactly so.
The take-off run, in contrast, defaults to start at the runway
On 30 Nov 2009, at 14:24, Erik Hofman wrote:
Modified Files:
main.cxx options.cxx
Log Message:
update to allow selection of a new sound device
Nice work! And the preference / settings changes too - I know this is painful
work, but it's long overdue and will really help make using
Stuart Buchanan wrote:
Update of /var/cvs/FlightGear-0.9/docs/getstart/source
In directory baron.flightgear.org:/tmp/cvs-serv25730
Modified Files:
features.tex
Log Message:
Update Features list:
- Re-ordering to put MP at the top
- Updated desrcription of AAR making use of
Martin Spott wrote:
Stuart Buchanan wrote:
Update of /var/cvs/FlightGear-0.9/docs/getstart/source
In directory baron.flightgear.org:/tmp/cvs-serv25730
Modified Files:
features.tex
Log Message:
Update Features list:
- Re-ordering to put MP at the top
- Updated
On Sun, 2009-11-22 at 16:06 -0600, James Turner wrote:
Update of /var/cvs/FlightGear-0.9/data/Aircraft/c172p/Nasal
In directory baron.flightgear.org:/tmp/cvs-serv24918/Nasal
Modified Files:
action-sim.nas
Log Message:
Dave Perry:
This patch adds main gear rotations about the
On Tue, Nov 24, 2009 at 5:28 PM, Ron Jensen w...@jentronics.com wrote:
The relationship between feet and meters is exactly 0.3048 feet per
meter. Your conversion value of 12/39.4 is approximately 0.30456... It
would be better to do:
# constants
...
var radTOdeg = 57.295779;
var
Ron Jensen wrote:
The relationship between feet and meters is exactly 0.3048 feet per
meter. Your conversion value of 12/39.4 is approximately 0.30456... It
would be better to do:
# constants
...
var radTOdeg = 57.295779;
var ftTOmeter = 0.3048;
...
# Right main
var
On Thu, 19 Nov 2009 16:55:42 + (GMT)
Heiko Schulz aeitsch...@yahoo.de wrote:
One other issue I see with the 3d model and the
textures. The way the
cuts in the textures is done, one has nearly vertical
surfaces on each
side near the bottom edge of the windshield. This
results
James Turner wrote:
Update of /var/cvs/FlightGear-0.9/data/Aircraft/c172p
In directory baron.flightgear.org:/tmp/cvs-serv24918
Modified Files:
c172p.xml
Log Message:
Dave Perry:
This patch adds main gear rotations about the fuselage attach points that
keep
the wheels in
Hello.
First thanks for comitting the changes to the c172p.
For all, I don't see me as main author, just as another one beside the already
known, just made a new 3d-model and 3d-panel.
So thanks for Dave Perry as another contributer for the instruments-lights!
I see still issues and this
Heiko Schulz wrote:
Hello.
First thanks for comitting the changes to the c172p.
For all, I don't see me as main author, just as another one beside the
already known, just made a new 3d-model and 3d-panel.
So thanks for Dave Perry as another contributer for the instruments-lights!
I see
Hello,
Hello Heiko,
I have another patch ready to submit with xml indents and
tabs fixed and
consolidation of redundant sections as well as alignment of
the
propeller spin axis with the spinner axis.
I believe that the position on the ground should be totally
determined
by the
On Thu, 2009-11-19 at 09:37 -0700, dave perry wrote:
I believe that the position on the ground should be totally determined
by the gear compression forces and the mass and cg. I.e. it will
correct itself once we implement correct gear compressions. So don't
mess with rotating the 3d
Csaba Halász wrote:
On 5 Nov 2009, at 09:18, Erik Hofman wrote:
John Denker:
Add a view debugging functions and represent the viewer quats in the
property tree for debugging.
Unfortunately the debug code is broken and causes segfaults. It is
tieing temporary char pointers to property
Hi Erik,
Erik Hofman wrote:
Update of /var/cvs/FlightGear-0.9/source/src/Main
In directory baron.flightgear.org:/tmp/cvs-serv10148
Modified Files:
viewmgr.cxx
Log Message:
put the debugging quat strings as doubles under /sim/current-view/debug
instead.
I suspect that
Martin Spott wrote:
Hi Erik,
Erik Hofman wrote:
Update of /var/cvs/FlightGear-0.9/source/src/Main
In directory baron.flightgear.org:/tmp/cvs-serv10148
Modified Files:
viewmgr.cxx
Log Message:
put the debugging quat strings as doubles under /sim/current-view/debug
instead.
I
On 11/10/2009 06:36 PM, Csaba Halász wrote:
On 5 Nov 2009, at 09:18, Erik Hofman wrote:
John Denker:
Add a view debugging functions and represent the viewer quats in the
property tree for debugging.
Unfortunately the debug code is broken and causes segfaults. It is
tieing temporary char
On Wed, Nov 11, 2009 at 2:43 PM, John Denker j...@av8n.com wrote:
Before switching to the string representation, I read the
code for the tie functions. I got the impression the code
was making a clone, i.e. a deep copy. Apparently this
impression was incorrect. Sorry.
No, the problem
John Denker wrote:
Having used the feature both ways, I remain of the opinion
that the string representation is easier for the user to
interpret. Doing this safely via a few static char*s is
easy to do. Let me work on it.
To be honest I don't think it's worth the effort, but I wont hold you
Erik Hofman wrote:
Martin Spott wrote:
Hi Erik,
Erik Hofman wrote:
Update of /var/cvs/FlightGear-0.9/source/src/Main
In directory baron.flightgear.org:/tmp/cvs-serv10148
Modified Files:
viewmgr.cxx
Log Message:
put the debugging quat strings as doubles under
On 11/11/2009 07:10 AM, Erik Hofman wrote:
John Denker wrote:
Having used the feature both ways, I remain of the opinion
that the string representation is easier for the user to
interpret. Doing this safely via a few static char*s is
easy to do. Let me work on it.
To be honest I don't
On 5 Nov 2009, at 09:18, Erik Hofman wrote:
John Denker:
Add a view debugging functions and represent the viewer quats in the
property tree for debugging.
Unfortunately the debug code is broken and causes segfaults. It is
tieing temporary char pointers to property nodes. In its current
On 9 Nov 2009, at 10:29, Erik Hofman wrote:
allow sound effects in the configuration file to be added to the
'avionics' sample group by setting 'typeavionics/type'.
Awesome stuff, this is such a good step towards better sound handling.
James
Hi Martin, Vivian team
This is an honest question, trying to understand the direction where we can
evolve FG.
Currently the models in data/Models seem to serve two purposes, and I'm
wondering if they can be divided (kept in different repositories) based on
the purpose?
1) static objects
On Thu, Nov 5, 2009 at 6:52 PM, Tom P wrote:
Hi Martin, Vivian team
This is an honest question, trying to understand the direction where we can
evolve FG.
Currently the models in data/Models seem to serve two purposes, and I'm
wondering if they can be divided (kept in different
On Mon, 2 Nov 2009, Martin Spott wrote:
Vivian Meazza wrote:
[-- text/plain, Encoding 7bit, Zeichensatz: ISO-8859-1, 254 Zeilen --]
Update of /var/cvs/FlightGear-0.9/data/Aircraft/ZLT-NT/Engines
In directory baron.flightgear.org:/tmp/cvs-serv11954
Modified Files:
engIO360C.xml
On 31 Oct 2009, at 15:10, Ron Jensen wrote:
Starting with fgfs --disable-real-weather-fetch --timeofday=noon
Also reported on IRC by stuart, MyName, pab...
And me.
--
Come build with us! The BlackBerry(R) Developer
On 11/01/2009 12:28 PM, James Turner wrote:
On 31 Oct 2009, at 15:10, Ron Jensen wrote:
Starting with fgfs --disable-real-weather-fetch --timeofday=noon
Also reported on IRC by stuart, MyName, pab...
And me.
I believe this is fixed now; let me know if not.
Tim
Hi Tim,
On Sunday 01 November 2009 09:08:35 pm Tim Moore wrote:
I believe this is fixed now; let me know if not.
Works for me. (And the moon is still correctly illuminated).
Cheers,
Durk
--
Come build with us! The
Vivian Meazza wrote:
[-- text/plain, Encoding 7bit, Zeichensatz: ISO-8859-1, 254 Zeilen --]
Update of /var/cvs/FlightGear-0.9/data/Aircraft/ZLT-NT/Engines
In directory baron.flightgear.org:/tmp/cvs-serv11954
Modified Files:
engIO360C.xml propHO-V373-D.xml
Log Message:
Update by
On Mon, 2009-11-02 at 00:01 +, Martin Spott wrote:
Vivian Meazza wrote:
[-- text/plain, Encoding 7bit, Zeichensatz: ISO-8859-1, 254 Zeilen --]
Update of /var/cvs/FlightGear-0.9/data/Aircraft/ZLT-NT/Engines
In directory baron.flightgear.org:/tmp/cvs-serv11954
Modified Files:
On 10/31/2009 04:58 AM, Ron Jensen wrote:
On Fri, 2009-10-30 at 18:15 -0500, Tim Moore wrote:
Update of /var/cvs/FlightGear-0.9/source/src/Main
In directory baron.flightgear.org:/tmp/cvs-serv5452/src/Main
Modified Files:
fg_os_osgviewer.cxx renderer.cxx
Log Message:
fix moon lighting
On 10/31/2009 08:34 AM, Tim Moore wrote:
On 10/31/2009 04:58 AM, Ron Jensen wrote:
On Fri, 2009-10-30 at 18:15 -0500, Tim Moore wrote:
Update of /var/cvs/FlightGear-0.9/source/src/Main
In directory baron.flightgear.org:/tmp/cvs-serv5452/src/Main
Modified Files:
fg_os_osgviewer.cxx
On Sat, 2009-10-31 at 09:04 +0100, Tim Moore wrote:
On 10/31/2009 08:34 AM, Tim Moore wrote:
On 10/31/2009 04:58 AM, Ron Jensen wrote:
On Fri, 2009-10-30 at 18:15 -0500, Tim Moore wrote:
Update of /var/cvs/FlightGear-0.9/source/src/Main
In directory
On Sat, 2009-10-31 at 08:34 +0100, Tim Moore wrote:
On 10/31/2009 04:58 AM, Ron Jensen wrote:
On Fri, 2009-10-30 at 18:15 -0500, Tim Moore wrote:
Update of /var/cvs/FlightGear-0.9/source/src/Main
In directory baron.flightgear.org:/tmp/cvs-serv5452/src/Main
Modified Files:
Vivian Meazza wrote:
Update of /var/cvs/FlightGear-0.9/data/Models/Maritime/Military
In directory baron.flightgear.org:/tmp/cvs-serv17265
Modified Files:
OliverPerryFFG.ac
Log Message:
Rotate to standard FG orientation
Please see 'data/Models/00README.CONTRIBUTE':
The following
On Fri, 2009-10-30 at 18:15 -0500, Tim Moore wrote:
Update of /var/cvs/FlightGear-0.9/source/src/Main
In directory baron.flightgear.org:/tmp/cvs-serv5452/src/Main
Modified Files:
fg_os_osgviewer.cxx renderer.cxx
Log Message:
fix moon lighting at night
This hasn't worked since the
On 22 Oct 2009, at 13:54, Erik Hofman wrote:
-std::auto_ptrunsigned char ptr( buf.c_str() );
+std::auto_ptrunsigned char ptr( (unsigned char*)
buf.c_str() );
This still looks wrong to me - you can't create an auto_ptr from
buf.c_str(), it will delete memory
On 22 Oct 2009, at 17:23, James Turner wrote:
without
using a copy to turn the temporary data from c_str() into something
that lives on the heap.
This is factually wrong, I realise - of course the data returned by
c_str() *does* live on the heap, but that does't change the original
James Turner wrote:
On 22 Oct 2009, at 17:23, James Turner wrote:
without
using a copy to turn the temporary data from c_str() into something
that lives on the heap.
This is factually wrong, I realise - of course the data returned by
c_str() *does* live on the heap, but that does't
On 22 Oct 2009, at 17:50, Erik Hofman wrote:
I dislike the method of using strings to story binary data anyhow.
Yes, agreed 100%.
--
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only
On 14 Oct 2009, at 21:37, Roy Vegard Ovesen wrote:
What if I really, really, really don't want a GPS? :-)
But seriously, why must every aircraft have a GPS?
The problem here is the name. Don't think of it as 'GPS', think of it
as 'lazy default navigation aid for people who are not
On 14 Oct 2009, at 22:37, Pete Morgan wrote:
I cannot see tcan on a civil aircraft, however its there on the nav
display F12 with no purpose ?? confusing ??
I just realised, with my GUI-dialogs-selective-widget-visiblity fix of
a few weeks back, I can update the default radios dialog to
Update of /var/cvs/FlightGear-0.9/source/src/Instrumentation
In directory baron.flightgear.org:/tmp/cvs-serv24388/src/Instrumentation
Modified Files:
instrument_mgr.cxx instrument_mgr.hxx
Log Message:
Ensure we always create a GPS instrument.
What if I really, really, really don't want a
Roy Vegard Ovesen wrote:
Update of /var/cvs/FlightGear-0.9/source/src/Instrumentation
In directory baron.flightgear.org:/tmp/cvs-serv24388/src/Instrumentation
Modified Files:
instrument_mgr.cxx instrument_mgr.hxx
Log Message:
Ensure we always create a GPS instrument.
What if I
Hi John,
I just fixed what appeared to me as a bug:
mixing altitude_ft and altitude_m and wrong sign when computing temperature at
sea level from temperature at altitude.
Can you check and confirm that this is correct and reflects your original
intention?
Thanks, Torsten
On 09/20/09 08:52, Torsten Dreyer wrote:
Hi John,
I just fixed what appeared to me as a bug:
mixing altitude_ft and altitude_m and wrong sign when computing temperature
at
sea level from temperature at altitude.
Can you check and confirm that this is correct and reflects your original
On Sat, 2009-09-12 at 10:21 -0500, Tim Moore wrote:
Update of /var/cvs/FlightGear-0.9/source/src/Environment
In directory baron.flightgear.org:/tmp/cvs-serv2733/src/Environment
Modified Files:
atmosphere.cxx atmosphere.hxx environment.cxx environment.hxx
Log Message:
Merge branch
On 09/13/09 19:22, Ron Jensen wrote:
639 : timoore 1.28 if (elevation_ft = ISA_def[1].height) {
640 : SG_LOG(SG_GENERAL, SG_ALERT, recalc_sl_temperature:
641 : valid only in troposphere, not elevation_ft);
642 : return;
Quick question. The old code would silently
On 29 Aug 2009, at 14:24, Torsten Dreyer wrote:
Modified Files:
runways.cxx
Log Message:
missing declaration of SGPropertyNode
Cheers Torsten - really odd that it built fine for me.
James
--
Let Crystal
Martin Spott wrote:
-Actual Version v.0.4
+Actual version v0.5
+---
+-photorealistic cockpit in progress
+-more realistic fdm
[...]
Arrrgh, 'patch' failed with a return code of 0
I'll fix this,
Martin.
--
Unix _IS_
Vivian Meazza wrote:
Update of /var/cvs/FlightGear-0.9/data/Models/Airport
In directory baron.flightgear.org:/tmp/cvs-serv26998
Added Files:
BAK-12-0.ac BAK12.xml
Log Message:
Add runway arrester gear type BAK-12. Based on Dave Culp's original work
Just as a reminder, as written
Martin Spott wrote:
Vivian Meazza wrote:
Update of /var/cvs/FlightGear-0.9/data/Models/Airport
In directory baron.flightgear.org:/tmp/cvs-serv26998
Added Files:
BAK-12-0.ac BAK12.xml
Log Message:
Add runway arrester gear type BAK-12. Based on Dave Culp's original work
Just as a
Vivian Meazza wrote:
Update of /var/cvs/FlightGear-0.9/data/Aircraft/MPCarrier
In directory baron.flightgear.org:/tmp/cvs-serv18340
Modified Files:
help.xml
Log Message:
Update to reflect recent changes
Please excuse my curiosity: Isn't the number of consecutive empty lines
pretty
Hi Erik,
Erik Hofman wrote:
Update of /var/cvs/FlightGear-0.9/source/src/Network
In directory baron.flightgear.org:/tmp/cvs-serv24469
Modified Files:
generic.cxx generic.hxx
Log Message:
Out of curiosity: Did you make sure there's nothing missing ?
jive: 12:54:04
On 16 Jun 2009, at 12:04, Tim Moore wrote:
sg_location now uses C strings. Also, change uses of sg_throwable to
more
specific exceptions like sg_io_exception.
A bit of a tangent, but: I've used exceptions in the code I've
contributed, where I feel they are appropriate, but I've often
On 14 Jun 2009, at 12:08, Frederic Bouvier wrote:
FGPavement::FGPavement(const std::string aIdent, const SGGeod
aPos) :
FGPositioned(TAXIWAY, aIdent, aPos, false)
Fred, are you sure we don't want to add a new FGPositioned::Type for
this? I don't mind either way, it's whatever you think
James Turner a écrit :
On 14 Jun 2009, at 12:08, Frederic Bouvier wrote:
FGPavement::FGPavement(const std::string aIdent, const SGGeod
aPos) :
FGPositioned(TAXIWAY, aIdent, aPos, false)
Fred, are you sure we don't want to add a new FGPositioned::Type for
this? I don't mind
gerard robin wrote:
On mardi 05 mai 2009, Alexis Bory - xiii wrote:
I still don't know if it's ok to let the pushback stuff in the Nasal dir.
IMHO this should be further discussed.
Won't it be better to have it within Aircraft/Generic ?
with others stuffs like aar or radar
I agree
On Friday 10 April 2009 23:44:09 Syd Adams wrote:
Update of /var/cvs/FlightGear-0.9/data/AI/Airports/TXKF
In directory baron.flightgear.org:/tmp/cvs-serv16099/TXKF
Added Files:
parking.xml
Log Message:
new airport file from msmith..
FWIW, I just added a copy of this file into the
Alexis Bory wrote:
Update of /var/cvs/FlightGear-0.9/data/Nasal In directory
baron.flightgear.org:/tmp/cvs-serv9196
Modified Files: pushback.nas Log Message: - Now the pushback door
will be created only if /sim/model/pushback has already been created
by the modeler via the
On mardi 05 mai 2009, Alexis Bory - xiii wrote:
Alexis Bory wrote:
Update of /var/cvs/FlightGear-0.9/data/Nasal In directory
baron.flightgear.org:/tmp/cvs-serv9196
Modified Files: pushback.nas Log Message: - Now the pushback door
will be created only if /sim/model/pushback has
Torsten Dreyer wrote:
-// Written by David Culp, started Feb 2004.
+// Original by Written by David Culp
//
-// Copyright (C) 2004 David P. Culp - davidcu...@comcast.net
+// An attempt to refine the thermal shape and behaviour by WooT 2009
+//
+// Copyright (C) 2009 Patrice Poly ( WooT )
- Erik Hofman a écrit :
Torsten Dreyer wrote:
-// Written by David Culp, started Feb 2004.
+// Original by Written by David Culp
//
-// Copyright (C) 2004 David P. Culp - davidcu...@comcast.net
+// An attempt to refine the thermal shape and behaviour by WooT
2009
+//
+//
Torsten Dreyer wrote:
-// Written by David Culp, started Feb 2004.
+// Original by Written by David Culp
//
-// Copyright (C) 2004 David P. Culp - davidcu...@comcast.net
+// An attempt to refine the thermal shape and behaviour by WooT 2009
+//
+// Copyright (C) 2009 Patrice Poly (
Torsten Dreyer wrote:
Erik
You are right - sorry. It is corrected. I am sure there was no evil mind
behind that.
Probably not but I felt it was important to point out.
Anyway, thanks for fixing it.
Erik
--
Stay on
* Melchior FRANZ -- Monday 16 March 2009:
+ vary callsign TACAN id
+ fly refueling pattern
That's now done. The tanker flies a refueling pattern with length
50 nm and 25 degree turns. You get a warning 1 nm before the turn.
Note that pilots also tank during the turn!
Bank angle and turn rate
Hi,
On Tuesday 17 March 2009 23:01:38 Melchior Franz wrote:
Update of /var/cvs/FlightGear-0.9/source/src/Instrumentation
In directory baron.flightgear.org:/tmp/cvs-serv17937/src/Instrumentation
Modified Files:
agradar.cxx rad_alt.cxx wxradar.cxx wxradar.hxx
Log Message:
wxradar: read
* Durk Talsma -- Sunday 22 March 2009:
FWIW, I just checked in a small change that allows the AI Air Traffic
controller to request the AI Aircraft to set a squawk code.
Yeah, I've read that, and we've immediately discussed on IRC how to use
that. Unfortunately, we didn't have an ATC/Radar
On Sunday 22 March 2009 15:58:27 Melchior FRANZ wrote:
* Durk Talsma -- Sunday 22 March 2009:
FWIW, I just checked in a small change that allows the AI Air Traffic
controller to request the AI Aircraft to set a squawk code.
Yeah, I've read that, and we've immediately discussed on IRC how to
Melchior FRANZ wrote:
* Durk Talsma -- Sunday 22 March 2009:
FWIW, I just checked in a small change that allows the AI Air
Traffic controller to request the AI Aircraft to set a squawk code.
Yeah, I've read that, and we've immediately discussed on IRC how to
use that. Unfortunately,
* Durk Talsma -- Sunday 22 March 2009:
On Sunday 22 March 2009 15:58:27 Melchior FRANZ wrote:
One idea would be to put it by where the callsign is now, and only
if it's not available use the callsign.
Sound good. Just let me know If there's anything that I need to change.
OK, I'll hack
* gerard robin -- Thursday 19 March 2009:
I can only answer that i never had any problem with the actual AI/MP radar,
it is very flexible , since the main required values x-shift, y-shift, in
addition to the other useful aircraft data ( range-nm, altitude, heading )
are there. These data
Mathias Froehlich wrote:
Update of /var/cvs/FlightGear-0.9/data/AI/Aircraft/Fokker-50/Models
In directory baron.flightgear.org:/tmp/cvs-serv2499/Aircraft/Fokker-50/Models
Modified Files:
fokker50.ac
Log Message:
Set the ambient color equal to the rgb color.
This is what currently
Erik,
On Thursday 19 March 2009 09:08:29 Erik Hofman wrote:
To be honnest I don't like this action. I've always made sure all color
settings were right in the modeller and did'nt adjust them to look nice
in FlightGear in any way. Same goes for the F-16, T-37, T-38, Fokker
100, Fokker 70 and
Mathias Fröhlich wrote:
Erik,
On Thursday 19 March 2009 09:08:29 Erik Hofman wrote:
To be honnest I don't like this action. I've always made sure all color
settings were right in the modeller and did'nt adjust them to look nice
in FlightGear in any way. Same goes for the F-16, T-37, T-38,
On lundi 16 mars 2009, Melchior FRANZ wrote:
While we are at it, here some comments on tanker.nas:
There's a menu entry AI/MP-Tanker, which opens a small dialog where
you can request a tanker. It'll contact you and tell you something
like this:
MOBIL3 at 15000, heading 130 with 250 knots,
* gerard robin -- Thursday 19 March 2009:
With the usual AI tankers we have a lot of data regarding the Radar
x-shift y-shift in-range , rotation, v-offset, .. and so on
That tanker feature don't gives such information , it is missing ,
is it any valuable reason ?
That's not
On jeudi 19 mars 2009, Melchior FRANZ wrote:
* gerard robin -- Thursday 19 March 2009:
With the usual AI tankers we have a lot of data regarding the Radar
x-shift y-shift in-range , rotation, v-offset, .. and so on
That tanker feature don't gives such information , it is
* gerard robin -- Thursday 19 March 2009:
Then, do you mean that the old Radar Fashion will be removed,
what a pity.
I haven't planned that (yet). But in the long run it should get
removed. This was an early mechanism to get the brand-new AI
models on the screen (for the T38?), and that was OK
1 - 100 of 316 matches
Mail list logo