* Norman Vine -- Thursday 17 July 2003 06:09:
Hmm, we used to be able to print the position on demand.
but I don't see a key binding for that anymore
The scripting test outputs lon/lat/alt: Shift-C
m.
___
Flightgear-devel mailing list
[EMAIL
Jim Wilson wrote:
These changes should preserve previous functionality (with the exception of a
couple bug fixes).
I've put it in CVS.
Thanks.
Erik
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
I built a c152 directory inside data/aircraft, and put the c152.xml
there. I put the engine file (lycoming_O-235-L2C.xml) and the prop
file, (c152-prop.xml) both in the data/engine directory. Is this
correct?
Yes. You also need a c152-set.xml file, which you'll have to make by hand.
I
David Culp wrote:
I built a c152 directory inside data/aircraft, and put the c152.xml
there. I put the engine file (lycoming_O-235-L2C.xml) and the prop
file, (c152-prop.xml) both in the data/engine directory. Is this
correct?
Yes. You also need a c152-set.xml file, which you'll
This was an outstanding find. I did have a main panel map that John sent me a
while back, but this has the whole flight deck in one pdf. Now if I could
only have (for free :-)) the pages that reference each of the balloon keys in
the diagrams.
4 megabyte file:
Jim Wilson wrote:
Are you using ac3d or blender?
ac3d.
Ah ok.
The tips helped a lot:
http://www.a1.nl/~ehofman/fgfs/gallery/fokker/
It's starting to look quite good now.
Erik
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
Norman Vine [EMAIL PROTECTED] said:
Erik Hofman writes:
http://www.a1.nl/~ehofman/fgfs/gallery/fokker/
It's starting to look quite good now.
Coming along nicely
This is really going to be a nice one.
nit
It is hard to tell but it almost looks as if there is
something going
David Culp wrote:
Part of the problem is that the first version of Aero-Matic had a bug that
gave prop thrust values off by a decimal place. The first six values under
C_THRUST should be shifted one decimal place to the right. Or, you can get a
new prop file from Aero-Matic, which is now
Matt Fienberg wrote:
David Culp wrote:
Part of the problem is that the first version of Aero-Matic had a bug that
gave prop thrust values off by a decimal place. The first six values under
C_THRUST should be shifted one decimal place to the right. Or, you can get a
new prop file
I'm assuming you meant divide by 10 with a shift of the decimal point to
the left... ;)
Yep, that's what I meant to say. 0.9 should be changed to 0.09
Dave
--
David Culp
[EMAIL PROTECTED]
Norman Vine [EMAIL PROTECTED] wrote:
It is hard to tell but it almost looks as if there is
something going on with the normals on the wing
panels. ie the shaddowing doesn't quite seem
consistant with that on the fusalage.
I've seen similar effects with FlightGear in the past - after
I'm working my way through some of the UK aerodromes, and have hit some problems
agreeing ANY of the decimal coordinates in the FG files with the DMS coordinates given
in the UK AIP.
For instance, London Gatwick (EGKK) has ARP at N510853 W0001125, which by my
calculations comes out as
How much of real life potential scenery do you thing is copyrighted ? I
know one good example of that, it's the Eiffel Tower (in Paris, for those
who wouldn't know) by night. It has had a lighting system since new year
2000, and I think you have to pay royalties if you redistribute images of
the
Hello all,
could I suggest that the FlightGear/Input/Joysticks/Deafult/joystick.xml axis
2 throttle binding is amended to that it operates on
/autopilot/control-overrides/throttle instead of having eight separate
entries for up to eight engines?
First of all, eight isn't enough;)
And
On Wed, 09 Jul 2003 10:27:42 +1000
Bernie Bright [EMAIL PROTECTED] wrote:
Perhaps we need separate low poly-count models suitable for use as AI
aircraft. FS2k2 supports such a feature. Such models wouldn't need 3D
cockpits or animations, although retracting landing gear and spinning
props
On Thursday 17 July 2003 18:30, Jorge Van Hemelryck wrote:
How much of real life potential scenery do you thing is copyrighted ? I
know one good example of that, it's the Eiffel Tower (in Paris, for those
who wouldn't know) by night. It has had a lighting system since new year
2000, and I
On Thu, 17 Jul 2003 19:23:23 +0100,
Lee Elliott [EMAIL PROTECTED] wrote in message
[EMAIL PROTECTED]:
On Thursday 17 July 2003 18:30, Jorge Van Hemelryck wrote:
How much of real life potential scenery do you thing is
copyrighted ? I know one good example of that, it's the Eiffel Tower
On 16 Jul 2003 18:11:06 +0100,
Christopher S Horler [EMAIL PROTECTED] wrote in message
[EMAIL PROTECTED]:
An alternative reason for keeping it is the KLM stewardesses
..you shag 'em using FG??? ;-)
--
..med vennlig hilsen = with Kind Regards from Arnt... ;-)
...with a number of polar bear
Jim Wilson wrote:
I'd guess that there are 2 sided polys in there. Look at the whiteness on the
wing root (in the shaded area) and what should be the shaded side of the tail
here: http://www.a1.nl/~ehofman/fgfs/gallery/fokker/002.jpg
You know what, I had to flip the normals on the horizontal
Tried to look but the pdf file won't open once I downloaded it.
On Thu, 2003-07-17 at 14:27, Jim Wilson wrote:
This was an outstanding find. I did have a main panel map that John sent me a
while back, but this has the whole flight deck in one pdf. Now if I could
only have (for free :-)) the
Jorge Van Hemelryck wrote:
... I look forward to being able to fly through our own version
of it.
After the posting here of the Eifel tower fly-through, I tried to
duplicate the maneuver in MSFS. Their tower has solid sides with
transparency in the bitmap and thus one cannot fly under it :(
Curtis L. Olson writes:
Make default visibility exactly 10 miles.
Six statue miles is the generally-accepted cutoff for good VFR.
Terminal area forecasts (TAF's) don't bother with anything over that,
and just report P6SM (plus six statue miles).
All the best,
David
--
David Megginson,
On Thu, 17 Jul 2003, Jorge Van Hemelryck wrote:
How much of real life potential scenery do you thing is copyrighted ? I
know one good example of that, it's the Eiffel Tower (in Paris, for those
who wouldn't know) by night. It has had a lighting system since new year
2000, and I think you have
David Megginson writes:
Curtis L. Olson writes:
Make default visibility exactly 10 miles.
Six statue miles is the generally-accepted cutoff for good VFR.
Terminal area forecasts (TAF's) don't bother with anything over that,
and just report P6SM (plus six statue miles).
Nice to know
David Culp wrote:
Part of the problem is that the first version of Aero-Matic had a bug that
gave prop thrust values off by a decimal place. The first six values under
C_THRUST should be shifted one decimal place to the right. Or, you can get a
new prop file from Aero-Matic, which is now
Christopher S Horler [EMAIL PROTECTED] said:
Tried to look but the pdf file won't open once I downloaded it.
That's strange. Works for me with xpdf 1.00 and linux acroread 5.0.5. File
size is 4012610.
Best,
Jim
On Thu, 2003-07-17 at 14:27, Jim Wilson wrote:
This was an outstanding
Small patch to expose the localizer property (e.g., true for ILS localizer).
Best,
Jim
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Small patch to expose the localizer property (e.g., true for ILS localizer).
Opps...
here's the link:
http://www.spiderbark.com/fgfs/navcom-loc.diff
Best,
Jim
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
I have implimented a first stab at an instant replay system and have
just commited it to CVS. The system continuously records your flight
data and allows you to play back your flight.
Saving flight data at full resolution can quickly burn up a lot of
RAM, so at the moment, only the most recent
On Friday 18 July 2003 04:06, Curtis L. Olson wrote:
I have implimented a first stab at an instant replay system and have
just commited it to CVS. The system continuously records your flight
data and allows you to play back your flight.
Saving flight data at full resolution can quickly burn
Lee Elliott writes:
That's a nice addition - sounds neat:)
I was just about to turn in for the night, and I did an update
earlier this evening, but I think I'll get this now:)
Hmm... I've been using the 'r' key for reheat but that's not a
problem - was a consensus reached on a scheme for
When we were developing the Multiplayer code, we tested a crude but
simple replay mechanism.
Using tcpdump we captured the multiplayer broadcast packets to a file.
We then used a simple program that read the captured data (used libpcap)
and put the packets back on the network as if Flightgear had
McCreanor, Duncan writes:
When we were developing the Multiplayer code, we tested a crude but
simple replay mechanism.
Using tcpdump we captured the multiplayer broadcast packets to a file.
We then used a simple program that read the captured data (used libpcap)
and put the packets back on
On Friday 18 July 2003 04:06, Curtis L. Olson wrote:
I have implimented a first stab at an instant replay system and have
just commited it to CVS. The system continuously records your flight
data and allows you to play back your flight.
Saving flight data at full resolution can quickly burn
I just did a cvs update in the process of updating some uiuc files, e.g.
the recorder files which had some issues and I want to put the new ones on
the fgfs cvs.
In the process of doing the updates, I have found that the two chase views
we had are now ***very*** different. There's a lag
35 matches
Mail list logo
