AW: [simpits-tech] Servo Driven Gauges and MFD/HUD data
Marc Weigert
simpits-tech@simpits.org
Sat, 8 Jun 2002 01:35:27 +0200
This is a multi-part message in MIME format.
------=_NextPart_000_0079_01C20E8C.C4AD3090
Content-Type: text/plain;
charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Hello Joseph,
thanks for your answer!
So it looks as if there is a vague chance that we will see this feature in
the future!
Is it so complicated for them to do this, or is it just a matter of focusing
on features that the broad simulation comunity will appreaciate?
Cheers,
Marc
To answer your question Marc, I asked him (G2I Guy) and his response was
there is no current way to display that data. We (myself and others) asked
that they make it available for output anyway and we'll figure out a way to
display it. So I don't know if it will be output or not. This guy (Claude
'shadow' Cavanaugh President and CEO of G2I) and his email
shadow@g2interactive.com seems real open to answering questions and has an
EPIC system himself and tells me they/he is currently working on a mode to
interface the EPIC and Cougar. So I hold out hope there will be MFD/HUD
data.
Crease-guard
------=_NextPart_000_0079_01C20E8C.C4AD3090
Content-Type: text/html;
charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2716.2200" name=3DGENERATOR>
<STYLE>@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in =
1.25in; }
P.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
COLOR: purple; TEXT-DECORATION: underline
}
SPAN.EmailStyle17 {
COLOR: windowtext; FONT-FAMILY: Arial
}
DIV.Section1 {
page: Section1
}
</STYLE>
</HEAD>
<BODY lang=3DEN-US vLink=3Dpurple link=3Dblue>
<DIV><FONT face=3DTahoma><FONT size=3D2><FONT face=3DArial><FONT =
color=3D#0000ff><SPAN=20
class=3D434440523-07062002><FONT face=3DTahoma color=3D#000000>Hello=20
Joseph,</FONT></SPAN></FONT></FONT></FONT></FONT></DIV>
<DIV><FONT face=3DTahoma><FONT size=3D2><FONT face=3DArial><FONT =
face=3DTahoma=20
color=3D#000000><SPAN=20
class=3D434440523-07062002></SPAN></FONT></FONT></FONT></FONT> </DIV=
>
<DIV><FONT face=3DTahoma><FONT size=3D2><FONT><FONT face=3DArial =
color=3D#0000ff><SPAN=20
class=3D434440523-07062002>thanks for your=20
answer!</SPAN></FONT></FONT></FONT></FONT></DIV>
<DIV><FONT face=3DTahoma><FONT size=3D2><FONT><FONT face=3DArial =
color=3D#0000ff><SPAN=20
class=3D434440523-07062002></SPAN></FONT></FONT></FONT></FONT> </DIV=
>
<DIV><FONT face=3DTahoma><FONT size=3D2><FONT><FONT face=3DArial =
color=3D#0000ff><SPAN=20
class=3D434440523-07062002>So it looks as if there is a vague chance =
that we will=20
see this feature in the future! =
</SPAN></FONT></FONT></FONT></FONT></DIV>
<DIV><FONT face=3DTahoma><FONT size=3D2><FONT><FONT face=3DArial =
color=3D#0000ff><SPAN=20
class=3D434440523-07062002></SPAN></FONT></FONT></FONT></FONT> </DIV=
>
<DIV><FONT face=3DTahoma><FONT size=3D2><FONT><FONT face=3DArial =
color=3D#0000ff><SPAN=20
class=3D434440523-07062002>Is it so complicated for them to do this, or =
is it just=20
a matter of focusing on features that the broad simulation comunity will =
appreaciate?</SPAN></FONT></FONT></FONT></FONT></DIV>
<DIV><FONT face=3DTahoma><FONT size=3D2><FONT><FONT face=3DArial =
color=3D#0000ff><SPAN=20
class=3D434440523-07062002></SPAN></FONT></FONT></FONT></FONT> </DIV=
>
<DIV><FONT face=3DTahoma><FONT size=3D2><FONT><FONT face=3DArial =
color=3D#0000ff><SPAN=20
class=3D434440523-07062002>Cheers,</SPAN></FONT></FONT></FONT></FONT></DI=
V>
<DIV><FONT face=3DTahoma><FONT size=3D2><FONT><FONT face=3DArial =
color=3D#0000ff><SPAN=20
class=3D434440523-07062002></SPAN></FONT></FONT></FONT></FONT> </DIV=
>
<DIV><FONT face=3DTahoma><FONT size=3D2><FONT><FONT face=3DArial =
color=3D#0000ff><SPAN=20
class=3D434440523-07062002>Marc</SPAN></FONT></FONT></DIV>
<DIV><BR></DIV></FONT></FONT>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
<DIV class=3DSection1>
<P class=3DMsoNormal><FONT face=3D"Courier New" size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'">To answer your =
question=20
Marc, I asked him (G2I Guy) and his response was there is no current =
way to=20
display that data. We (myself and others) asked that they make =
it=20
available for output anyway and we’ll figure out a way to =
display it. So=20
I don’t know if it will be output or not. This guy (Claude =
'shadow'=20
Cavanaugh President and CEO of G2I) and his email <A=20
href=3D"mailto:shadow@g2interactive.com">shadow@g2interactive.com</A> =
seems real=20
open to answering questions and has an EPIC system himself and tells =
me=20
they/he is currently working on a mode to interface the EPIC and =
Cougar. =20
So I hold out hope there will be MFD/HUD data.</SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3D"Courier New" size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier =
New'"></SPAN></FONT> </P>
<P class=3DMsoNormal><FONT face=3D"Courier New" size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier =
New'">Crease-guard</SPAN></FONT></P></DIV></BLOCKQUOTE></BODY></HTML>
------=_NextPart_000_0079_01C20E8C.C4AD3090--