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]
* Josh Babcock -- Monday 24 May 2004 19:34:
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.
I have not had much luck with it.
Unfortunately, the ones that I have demonstrated aren't perfect
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 -- Sunday 23 May 2004 01:50:
http://members.aon.at/mfranz/textarc.png (27kB)
Show-off.
hehe :-)
That's cool. You think it would work for this?
http://www.dfrc.nasa.gov/gallery/photo/XB-70/HTML/ED97-44244-1.html
All the instruments in this blurry photo? That's boring. No
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)
* Roy Vegard Ovesen -- Saturday 22 May 2004 00:39:
On Friday 21 May 2004 23:41, Melchior FRANZ wrote:
I uploaded a new version that contains a weird ASI with non-linear
mapper #n. Looks strange. No idea what they had in mind.
I guess that when one wants to monitor for example the approach
* 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. :-]
* 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
* 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 angle that represents the scale value of 10% RPM.
I can
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
* 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, very cool. The best cockpit
* Roy Vegard Ovesen -- Wednesday 19 May 2004 22:22:
http://home.tiscali.no/rvovesen/fuel.png (19,964 bytes)
Nice! With the MetaPost user number at least doubling within just one day
I'd say that this is now the preferred way to make instrument faces. ;-)
* Melchior FRANZ -- Thursday 20 May 2004 09:37:
What I would [...]:
(1) [...]
(2) [...]
(2) [...]
(3) [...]
And finally:
(7) learn to count
m.
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
* Josh Babcock -- Thursday 20 May 2004 01:01:
On Tuesday 18 May 2004 19:09, Melchior FRANZ wrote:
http://members.aon.at/mfranz/tach.mp (1.9kB)
[instrument faces created with MetaPost]
Ok, this stuff looks really cool, but I am encountering a pretty steep learning
curve with MetaPost.
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 be written as 254/254/254 ... white enough (who needs true
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,
* 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 labeled from 0 to 140, with a lot of colored marks around
100.
* 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 RPM? ... too high), but ...
Those
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
* 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 in YASim, so the
values don't
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
* Vivian Meazza -- Thursday 20 May 2004 17:00:
[turbine RPM]
They go from idle to max, isn't that enough?
no
m.
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
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 I saw them on the cockpit photo. Also, the
program
29 matches
Mail list logo