Jon S Berndt wrote:
FWIW, Gimp has a script that creates text arcs that I have considered
using if I ever get a chance to make some instruments.
Jon
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
On Sat, 22 May 2004 18:50:19 -0500, Jon wrote in message
[EMAIL PROTECTED]:
* Jon S Berndt, Fri May 21 16:44:16 CDT 2004:
FWIW, Gimp has a script that creates text arcs that I have
considered using if I ever get a chance to make some instruments.
Gimp is always a good choice.
Jon Berndt said:
* Jon S Berndt, Fri May 21 16:44:16 CDT 2004:
FWIW, Gimp has a script that creates text arcs that I have considered
using if I ever get a chance to make some instruments.
Gimp is always a good choice. However ...
http://members.aon.at/mfranz/textarc.png (27kB)
* Jon S Berndt, Fri May 21 16:44:16 CDT 2004:
FWIW, Gimp has a script that creates text arcs that I have considered
using if I ever get a chance to make some instruments.
Gimp is always a good choice. However ...
http://members.aon.at/mfranz/textarc.png (27kB)
m. :-]
Show-off.
On Thursday 20 May 2004 12:01, Melchior FRANZ wrote:
BTW: this is my little transparency trick: in my fgfs.mp library file I
have this:
color foreground, transparent;
background:=black;
transparent:=white;
white:=255/256white;
foreground:=white;
which lets white actually
On Thursday 20 May 2004 18:34, Melchior FRANZ wrote:
OK, here's a new version, just so you can see how easy instrument face
creation with MetaPost is. Note that there's a function @() defined, that
maps the real instrument angles to MetaPost angles. So I could directly
input all the values as
FWIW, Gimp has a script that creates text arcs that I have considered
using if I ever get a chance to make some instruments.
Jon
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
On Friday 21 May 2004 23:41, Melchior FRANZ wrote:
* Roy Vegard Ovesen -- Friday 21 May 2004 23:26:
This @() function proved to be very powerfull and it made creating scales
very easy.
I changed this to a unary operator #. So one can now write #10 and metapost
will replace this by the
On Thursday 20 May 2004 08:13, Melchior FRANZ wrote:
Looks like Maik's rotor RPM numbers are off
(442 RPM). I can't make sense of the dual tacho.
What doesn't make sense?
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
Melchior FRANZ said:
* Jim Wilson -- Thursday 20 May 2004 01:46:
Melchior FRANZ said:
Here's a small MetaPost file that I used to make the Bo105 rotor tacho
(which is totally made up; need some expert advice first):
Check out:
http://www.airliners.net/open.file/438320/L/
Hey,
Melchior FRANZ wrote
* Jim Wilson -- Thursday 20 May 2004 15:18:
The rotor can exceed the drive shaft speed (e.g. autorotation). Is
that what you are asking?
No, I couldn't see where 442 would fit into that scale, and
what 140 should stand for (140 RPM? ... too low; or 14000
On Thursday 20 May 2004 14:02, Melchior FRANZ wrote:
* Al West -- Thursday 20 May 2004 14:43:
On Thursday 20 May 2004 08:13, Melchior FRANZ wrote:
Looks like Maik's rotor RPM numbers are off
(442 RPM). I can't make sense of the dual tacho.
What doesn't make sense?
The ticks are
Melchior FRANZ wrote:
hh ... now that makes sense. I couldn't read the word PERCENT. I guess
one needs to be native English speaker to be able to decipher that. OK, I'll
do this instrument now -- only the rotor hand, though, because there's no
turbine RPM in YASim (?). Maybe I'll make the
Melchior FRANZ wrote
* Vivian Meazza -- Thursday 20 May 2004 16:07:
Melchior FRANZ wrote
only the rotor hand, though, because there's no turbine RPM
in YASim (?). Maybe I'll make the turbine RPM up with Nasal ...
[...]
N1 N2 ?
Yes, but there's no way to start/stop the turbines
14 matches
Mail list logo
