[simpits-tech] RE: [simpits-tech]MFD/HUD data
Chris
simpits-tech@simpits.org
Tue, 11 Jun 2002 05:33:17 -0400
This is a multi-part message in MIME format.
------=_NextPart_000_002D_01C21109.7D76A2E0
Content-Type: text/plain;
charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Thanks Mark,
Both you and Erwin have given me a better perspective!!
v/r
Chris Crowley
-----Original Message-----
From: simpits-tech-admin@simpits.org
[mailto:simpits-tech-admin@simpits.org]On Behalf Of Mark Doran
Sent: Sunday, June 09, 2002 4:56 PM
To: simpits-tech@simpits.org
Subject: [simpits-tech] RE: [simpits-tech]MFD/HUD data
I work in a group that does software performance work for a living.
Please, please don't ask G2 for multimon support for anything other than
out the window view fields and then only if you feel you must. There are
video cards coming that will make multimon support less taxing on the host
computer but that doesn't make it "free" in terms of performance impact.
Roughly speaking, each added video card/head in the host system eats 10%
performance overhead just to get it running under windows multimon.
Erwin's idea to shoot the data across the network to a second (or series
of) machine(s) makes a lot more sense as we can already see with the current
F4glass implementation. That app alone eats quite a bit of CPU budget just
to render the moving gauges. You really don't want that CPU budget burden
eating MIPS from the box trying to run the actual game engine unless you
have to.
For my 2c's - I think it's much more important to get MFDs rendered on
separate screens than it is to get wide fields of view (much as I'd like
that too).and while we are at it, actually I think the best way to do wider
viewfields without nailing the host computer is to ship the extra screens
out across the network for rendering as well. Remember Fighter Duel?? It
did a pretty good job of this and you could use eight or nine systems to get
a pretty much 360 degree view. Poor man's distributed processing. "Last
generation" cast off computers may pretty good display mules.
Cheers,
Mark.
-----Original Message-----
From: simpits-tech-admin@simpits.org
[mailto:simpits-tech-admin@simpits.org] On Behalf Of Erwin Neyt
Sent: Sunday, June 09, 2002 9:22 AM
To: simpits-tech@simpits.org
Subject: [simpits-tech] RE: [simpits-tech]MFD/HUD data
Multi monitor support will have a lot more impact on the code. Added bonus
to the sh.mem. solution is that you can use networked PC's (and off-load the
Falcon PC) to display the MFD's. Also the HUD and RWR are redundant pages,
so they are available too.
Also multi monitor support is often mentioned in the context of multiple
OTW windows, which is nice but will hurt FPS badly (see
http://www.eagle9.nl/redir2.asp?lokatie=/main/Programming/Doxs/default.asp)
I rather see they alter the MP code, and add an option to run a second PC in
'slave' mode.
Erwin.
-----Original Message-----
From: Chris [mailto:ccrowley@mccrowley.com]
Sent: Sunday, 09 June, 2002 14:27
To: simpits-tech@simpits.org
Subject: RE: [simpits-tech] Servo Driven Gauges and MFD/HUD data
If the G2I plan is to provide multi monitor support, couldn't there be
one view with MFD's that are rendered all the time, and others (HUD Mode)
without? I probably don't understand what G2 means by multi montor support.
I am just curious (not impatient) and trying to be helpful, I am not
even close to being able to make use of this. Thanks for your hard work
Erwin and by the way I am very impressed with your software!!!
Chris Crowley
-----Original Message-----
From: simpits-tech-admin@simpits.org
[mailto:simpits-tech-admin@simpits.org]On Behalf Of Erwin Neyt
Sent: Sunday, June 09, 2002 4:36 AM
To: simpits-tech@simpits.org
Subject: RE: [simpits-tech] Servo Driven Gauges and MFD/HUD data
Problem is that if the MFD's are not onscreen, they will not be
rendered at all.
What we want is MFD data which is rendered all the time (for example
we we're in HUD only mode)
Erwin.
BTW. I can't say much but I am in contact with G2I concerning this
subject. Please be patient.
-----Original Message-----
From: Chris [mailto:ccrowley@mccrowley.com]
Sent: Saturday, 08 June, 2002 12:31
To: simpits-tech@simpits.org
Subject: RE: [simpits-tech] Servo Driven Gauges and MFD/HUD data
Why is this feature so complicated? The MFDs show up in the Black
boxes that are located in the "virtual cockpits". If you have ever looked at
the virtual cockpit graphics, all of the gauges are blacked out so the
software can generate the flight info in the black areas. Somehow a function
places them in a position that is "cut out" for them. It varies from virtual
cockpit to virtual cockpit, or even from view to view.
Now if they are adding multiple monitor capability, why not have a
view that is just the LEFT and one that is just the right MFD? This would be
simpler than pulling the raw data out of the code.
This is a question, I am sure its more complicated than that.
Chris Crowley
(Building Viper Pit)
-----Original Message-----
From: simpits-tech-admin@simpits.org
[mailto:simpits-tech-admin@simpits.org]On Behalf Of Marc Weigert
Sent: Friday, June 07, 2002 7:35 PM
To: simpits-tech@simpits.org
Subject: AW: [simpits-tech] Servo Driven Gauges and MFD/HUD data
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_002D_01C21109.7D76A2E0
Content-Type: text/html;
charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word"><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3DWord.Document name=3DProgId>
<META content=3D"MSHTML 5.50.4916.2300" name=3DGENERATOR>
<META content=3D"Microsoft Word 10" name=3DOriginator><LINK=20
href=3D"cid:filelist.xml@01C20FBD.6397BF00" rel=3DFile-List><!--[if gte =
mso 9]><xml>
<o:OfficeDocumentSettings>
<o:DoNotRelyOnCSS/>
</o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:WordDocument>
<w:SpellingState>Clean</w:SpellingState>
<w:GrammarState>Clean</w:GrammarState>
<w:DocumentKind>DocumentEmail</w:DocumentKind>
<w:EnvelopeVis/>
<w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel>
</w:WordDocument>
</xml><![endif]-->
<STYLE>@font-face {
font-family: Tahoma;
}
@font-face {
font-family: Lucida Console;
}
@font-face {
font-family: Lucida Sans Unicode;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; =
mso-header-margin: .5in; mso-footer-margin: .5in; mso-paper-source: 0; }
P.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-style-parent: ""; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"
}
LI.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-style-parent: ""; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"
}
DIV.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-style-parent: ""; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"
}
A:link {
COLOR: blue; TEXT-DECORATION: underline; text-underline: single
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline; text-underline: single
}
A:visited {
COLOR: purple; TEXT-DECORATION: underline; text-underline: single
}
SPAN.MsoHyperlinkFollowed {
COLOR: purple; TEXT-DECORATION: underline; text-underline: single
}
P.MsoAutoSig {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-pagination: widow-orphan; mso-fareast-font-family: "Times New Roman"
}
LI.MsoAutoSig {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-pagination: widow-orphan; mso-fareast-font-family: "Times New Roman"
}
DIV.MsoAutoSig {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-pagination: widow-orphan; mso-fareast-font-family: "Times New Roman"
}
SPAN.emailstyle17 {
COLOR: windowtext; FONT-FAMILY: Arial; mso-style-name: emailstyle17; =
mso-ascii-font-family: Arial; mso-hansi-font-family: Arial; =
mso-bidi-font-family: Arial
}
SPAN.EmailStyle18 {
FONT-WEIGHT: normal; COLOR: blue; FONT-STYLE: normal; FONT-FAMILY: =
"Lucida Console"; TEXT-DECORATION: none; text-underline: none; =
mso-ascii-font-family: "Lucida Console"; mso-hansi-font-family: "Lucida =
Console"; mso-style-type: personal-reply; mso-style-noshow: yes; =
mso-ansi-font-size: 10.0pt; mso-bidi-font-size: 10.0pt; =
text-line-through: none
}
SPAN.SpellE {
mso-style-name: ""; mso-spl-e: yes
}
SPAN.GramE {
mso-style-name: ""; mso-gram-e: yes
}
DIV.Section1 {
page: Section1
}
</STYLE>
<!--[if gte mso 10]>
<style>
/* Style Definitions */=20
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-parent:"";
mso-padding-alt:0in 5.4pt 0in 5.4pt;
mso-para-margin:0in;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:10.0pt;
font-family:"Times New Roman";}
</style>
<![endif]--></HEAD>
<BODY lang=3DEN-US style=3D"tab-interval: .5in" vLink=3Dpurple =
link=3Dblue>
<DIV><SPAN class=3D840463209-11062002><FONT face=3DArial color=3D#0000ff =
size=3D2>Thanks=20
Mark,</FONT></SPAN></DIV>
<DIV><SPAN class=3D840463209-11062002><FONT face=3DArial color=3D#0000ff =
size=3D2>Both=20
you and Erwin have given me a better perspective!!</FONT></SPAN></DIV>
<DIV><SPAN class=3D840463209-11062002><FONT face=3DArial color=3D#0000ff =
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D840463209-11062002><FONT face=3DArial color=3D#0000ff =
size=3D2>v/r</FONT></SPAN></DIV>
<DIV><SPAN class=3D840463209-11062002><FONT face=3DArial color=3D#0000ff =
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D840463209-11062002><FONT face=3DArial color=3D#0000ff =
size=3D2>Chris=20
Crowley</FONT></SPAN></DIV>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
<DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
size=3D2>-----Original Message-----<BR><B>From:</B>=20
simpits-tech-admin@simpits.org =
[mailto:simpits-tech-admin@simpits.org]<B>On=20
Behalf Of </B>Mark Doran<BR><B>Sent:</B> Sunday, June 09, 2002 4:56=20
PM<BR><B>To:</B> simpits-tech@simpits.org<BR><B>Subject:</B> =
[simpits-tech]=20
RE: [simpits-tech]MFD/HUD data<BR><BR></FONT></DIV>
<DIV class=3DSection1>
<P class=3DMsoNormal><FONT face=3D"Lucida Console" color=3Dblue =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Lucida =
Console'">I work in=20
a group that does software performance work for a=20
living.<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3D"Lucida Console" color=3Dblue =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Lucida =
Console'"><o:p> </o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3D"Lucida Console" color=3Dblue =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Lucida =
Console'">Please,=20
please don’t ask G2 for <SPAN class=3DSpellE>multimon</SPAN> =
support for=20
anything other than out the window view fields and then only if you =
feel you=20
must.<SPAN style=3D"mso-spacerun: yes"> </SPAN>There are video =
cards=20
coming that will make <SPAN class=3DSpellE>multimon</SPAN> support =
less taxing=20
on the host computer but that doesn’t make it “free” =
in terms of performance=20
impact.<SPAN style=3D"mso-spacerun: yes"> </SPAN>Roughly =
speaking, each=20
added video card/head in the host system eats 10% performance overhead =
just to=20
get it running under windows <SPAN=20
class=3DSpellE>multimon</SPAN>.<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3D"Lucida Console" color=3Dblue =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Lucida =
Console'"><o:p> </o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3D"Lucida Console" color=3Dblue =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Lucida =
Console'">Erwin’s=20
idea to shoot the data across the network to a second (or series of)=20
machine(s) makes a lot more sense as we can already see with the =
current=20
F4glass implementation.<SPAN style=3D"mso-spacerun: yes"> =
</SPAN>That app=20
alone eats quite a bit of CPU budget just to render the moving =
gauges.<SPAN=20
style=3D"mso-spacerun: yes"> </SPAN>You really don’t want =
that CPU budget=20
burden eating MIPS from the box trying to run the actual game engine =
unless=20
you have to.<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3D"Lucida Console" color=3Dblue =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Lucida =
Console'"><o:p> </o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3D"Lucida Console" color=3Dblue =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Lucida =
Console'">For my=20
2c’s – I think it’s much more important to get <SPAN =
class=3DSpellE>MFDs</SPAN>=20
rendered on separate screens than it is to get wide fields of view =
(much as=20
I’d like that too)…and while we are at it, actually I =
think the best way to do=20
wider <SPAN class=3DSpellE>viewfields</SPAN> without nailing the host =
computer=20
is to ship the extra screens out across the network for rendering as=20
well.<SPAN style=3D"mso-spacerun: yes"> </SPAN>Remember Fighter=20
Duel??<SPAN style=3D"mso-spacerun: yes"> </SPAN>It did a pretty =
good job=20
of this and you could use eight or nine systems to get a pretty much =
360=20
degree view.<SPAN style=3D"mso-spacerun: yes"> </SPAN>Poor =
man’s=20
distributed processing.<SPAN style=3D"mso-spacerun: yes"> =
</SPAN>“Last=20
generation” cast off computers may pretty good display <SPAN=20
class=3DGramE>mules.</SPAN><o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3D"Lucida Console" color=3Dblue =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Lucida =
Console'"><o:p> </o:p></SPAN></FONT></P>
<DIV>
<P class=3DMsoAutoSig><FONT face=3D"Lucida Sans Unicode" color=3Dblue =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Lucida Sans =
Unicode'; mso-no-proof: yes">Cheers,<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoAutoSig><FONT face=3D"Lucida Sans Unicode" color=3Dblue =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Lucida Sans =
Unicode'; mso-no-proof: yes"><o:p> </o:p></SPAN></FONT></P>
<P class=3DMsoAutoSig><FONT face=3D"Lucida Sans Unicode" color=3Dblue =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Lucida Sans =
Unicode'; mso-no-proof: yes">Mark.<o:p></o:p></SPAN></FONT></P></DIV>
<P class=3DMsoNormal><FONT face=3D"Lucida Console" color=3Dblue =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Lucida =
Console'"><o:p> </o:p></SPAN></FONT></P>
<DIV=20
style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: blue =
1.5pt solid; PADDING-TOP: 0in; BORDER-BOTTOM: medium none">
<P class=3DMsoNormal><FONT face=3DTahoma size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">-----Original=20
Message-----<BR><B><SPAN style=3D"FONT-WEIGHT: bold">From:</SPAN></B>=20
simpits-tech-admin@simpits.org [mailto:simpits-tech-admin@simpits.org] =
<B><SPAN style=3D"FONT-WEIGHT: bold">On Behalf Of </SPAN></B>Erwin=20
Neyt<BR><B><SPAN style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> Sunday, =
June 09,=20
2002 9:22 AM<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B>=20
simpits-tech@simpits.org<BR><B><SPAN=20
style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> [simpits-tech] RE:=20
[simpits-tech]MFD/HUD data</SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt"><o:p> </o:p></SPAN></FONT></P>
<DIV>
<P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">Multi =
monitor support=20
will have a lot more impact on the code. Added bonus to the sh.mem. =
solution=20
is that you can use networked PC's (and off-load the Falcon PC) to =
display the=20
MFD's. Also the HUD and RWR are redundant pages, so they are available =
too.</SPAN></FONT><o:p></o:p></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt"> <o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">Also multi =
monitor=20
support is often mentioned in the context of multiple OTW windows, =
which is=20
nice but will hurt FPS badly (see <A=20
=
href=3D"http://www.eagle9.nl/redir2.asp?lokatie=3D/main/Programming/Doxs/=
default.asp">http://www.eagle9.nl/redir2.asp?lokatie=3D/main/Programming/=
Doxs/default.asp</A>)=20
I rather see they alter the MP code, and add an option to run a second =
PC in=20
'slave' mode.</SPAN></FONT><o:p></o:p></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt"> <o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Erwin.</SPAN></FONT><o:p></o:p></P></DIV>
<BLOCKQUOTE=20
style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 3pt; PADDING-BOTTOM: 0in; MARGIN: 5pt 0in 5pt =
3pt; BORDER-LEFT: blue 1.5pt solid; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none">
<P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><FONT =
face=3DTahoma=20
size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">-----Original=20
Message-----<BR><B><SPAN style=3D"FONT-WEIGHT: =
bold">From:</SPAN></B> Chris=20
[mailto:ccrowley@mccrowley.com]<BR><B><SPAN=20
style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> Sunday, 09 June, 2002=20
14:27<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B>=20
simpits-tech@simpits.org<BR><B><SPAN=20
style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> RE: [simpits-tech] =
Servo=20
Driven Gauges and MFD/HUD data<o:p></o:p></SPAN></FONT></P>
<DIV>
<P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">If the =
G2I plan is=20
to provide multi monitor support, couldn't there be one view with =
MFD's that=20
are rendered all the time, and others (HUD Mode) without? I =
probably=20
don't understand what G2 means by multi montor support.=20
</SPAN></FONT><o:p></o:p></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt"> <o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">I am just =
curious=20
(not impatient) and trying to be helpful, I am not even close to =
being able=20
to make use of this. Thanks for your hard work Erwin and by the way =
I am=20
very impressed with your =
software!!!</SPAN></FONT><o:p></o:p></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt"> <o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">Chris=20
Crowley</SPAN></FONT><o:p></o:p></P></DIV>
<BLOCKQUOTE=20
style=3D"MARGIN-TOP: 5pt; MARGIN-BOTTOM: 5pt; MARGIN-RIGHT: =
0in"><P=20
class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><FONT =
face=3DTahoma size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">-----Original=20
Message-----<BR><B><SPAN style=3D"FONT-WEIGHT: =
bold">From:</SPAN></B>=20
simpits-tech-admin@simpits.org=20
[mailto:simpits-tech-admin@simpits.org]<B><SPAN=20
style=3D"FONT-WEIGHT: bold">On Behalf Of </SPAN></B>Erwin =
Neyt<BR><B><SPAN=20
style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> Sunday, June 09, 2002 =
4:36=20
AM<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B>=20
simpits-tech@simpits.org<BR><B><SPAN=20
style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> RE: [simpits-tech] =
Servo=20
Driven Gauges and MFD/HUD data</SPAN></FONT><o:p></o:p></P>
<DIV>
<P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">Problem =
is that=20
if the MFD's are not onscreen, they will not be rendered at=20
all.</SPAN></FONT><o:p></o:p></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =
style=3D"FONT-SIZE: =
12pt"> <o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">What we =
want is=20
MFD data which is rendered all the time (for example we we're in =
HUD only=20
mode)</SPAN></FONT><o:p></o:p></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =
style=3D"FONT-SIZE: =
12pt"> <o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Erwin.</SPAN></FONT><o:p></o:p></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =
style=3D"FONT-SIZE: =
12pt"> <o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">BTW. I =
can't say=20
much but I am in contact with G2I concerning this =
subject. Please be=20
patient.</SPAN></FONT><o:p></o:p></P></DIV>
<BLOCKQUOTE=20
style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; =
BORDER-TOP: medium none; PADDING-LEFT: 3pt; PADDING-BOTTOM: 0in; MARGIN: =
5pt 0in 5pt 3pt; BORDER-LEFT: blue 1.5pt solid; PADDING-TOP: 0in; =
BORDER-BOTTOM: medium none">
<P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><FONT =
face=3DTahoma=20
size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">-----Original=20
Message-----<BR><B><SPAN style=3D"FONT-WEIGHT: =
bold">From:</SPAN></B>=20
Chris [mailto:ccrowley@mccrowley.com]<BR><B><SPAN=20
style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> Saturday, 08 June, =
2002=20
12:31<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B>=20
simpits-tech@simpits.org<BR><B><SPAN=20
style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> RE: =
[simpits-tech] Servo=20
Driven Gauges and MFD/HUD data<o:p></o:p></SPAN></FONT></P>
<DIV>
<P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">Why =
is this=20
feature so complicated? The MFDs show up in the Black boxes that =
are=20
located in the "virtual cockpits". If you have ever looked at =
the=20
virtual cockpit graphics, all of the gauges are blacked out so =
the=20
software can generate the flight info in the black areas. =
Somehow a=20
function places them in a position that is "cut out" for them. =
It varies=20
from virtual cockpit to virtual cockpit, or even from view to=20
view.</SPAN></FONT><o:p></o:p></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
style=3D"FONT-SIZE: =
12pt"> <o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">Now =
if they are=20
adding multiple monitor capability, why not have a view that is =
just the=20
LEFT and one that is just the right MFD? This would be simpler =
than=20
pulling the raw data out of the =
code.</SPAN></FONT><o:p></o:p></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
style=3D"FONT-SIZE: =
12pt"> <o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">This =
is a=20
question, I am sure its more complicated than that.=20
</SPAN></FONT><o:p></o:p></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
style=3D"FONT-SIZE: =
12pt"> <o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">Chris =
Crowley</SPAN></FONT><o:p></o:p></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">(Building Viper=20
Pit)</SPAN></FONT><o:p></o:p></P></DIV>
<BLOCKQUOTE=20
style=3D"MARGIN-TOP: 5pt; MARGIN-BOTTOM: 5pt; MARGIN-RIGHT: =
0in">
<P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><FONT =
face=3DTahoma=20
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">-----Original=20
Message-----<BR><B><SPAN style=3D"FONT-WEIGHT: =
bold">From:</SPAN></B>=20
simpits-tech-admin@simpits.org=20
[mailto:simpits-tech-admin@simpits.org]<B><SPAN=20
style=3D"FONT-WEIGHT: bold">On Behalf Of </SPAN></B>Marc=20
Weigert<BR><B><SPAN style=3D"FONT-WEIGHT: =
bold">Sent:</SPAN></B> Friday,=20
June 07, 2002 7:35 PM<BR><B><SPAN=20
style=3D"FONT-WEIGHT: bold">To:</SPAN></B>=20
simpits-tech@simpits.org<BR><B><SPAN=20
style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> AW: =
[simpits-tech] Servo=20
Driven Gauges and MFD/HUD data</SPAN></FONT><o:p></o:p></P>
<DIV>
<P class=3DMsoNormal><FONT face=3DTahoma color=3Dblack =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Tahoma">Hello=20
Joseph,</SPAN></FONT><o:p></o:p></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
style=3D"FONT-SIZE: =
12pt"> <o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt; COLOR: blue; FONT-FAMILY: =
Arial">thanks for=20
your answer!</SPAN></FONT><o:p></o:p></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
style=3D"FONT-SIZE: =
12pt"> <o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt; COLOR: blue; FONT-FAMILY: Arial">So =
it looks=20
as if there is a vague chance that we will see this feature in =
the=20
future! </SPAN></FONT><o:p></o:p></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
style=3D"FONT-SIZE: =
12pt"> <o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt; COLOR: blue; FONT-FAMILY: Arial">Is =
it so=20
complicated for them to do this, or is it just a matter of =
focusing on=20
features that the broad simulation comunity will=20
appreaciate?</SPAN></FONT><o:p></o:p></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
style=3D"FONT-SIZE: =
12pt"> <o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt; COLOR: blue; FONT-FAMILY: =
Arial">Cheers,</SPAN></FONT><o:p></o:p></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
style=3D"FONT-SIZE: =
12pt"> <o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt; COLOR: blue; FONT-FAMILY: =
Arial">Marc</SPAN></FONT><FONT=20
face=3DTahoma size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma"><o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3DTahoma size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma"><o:p> </o:p></SPAN></FONT></P></DIV>
<BLOCKQUOTE=20
style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; =
BORDER-TOP: medium none; PADDING-LEFT: 3pt; PADDING-BOTTOM: 0in; MARGIN: =
5pt 0in 5pt 3pt; BORDER-LEFT: blue 1.5pt solid; PADDING-TOP: 0in; =
BORDER-BOTTOM: medium none">
<P class=3DMsoNormal><FONT face=3D"Courier New" =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'">To =
answer your=20
question Marc, I asked him (G2I Guy) and his response was =
there is=20
no current way to display that data. We (myself and =
others)=20
asked that they make it available for output anyway and =
we'll figure=20
out a way to display it. So I don't know if it will be =
output=20
or not. This guy (Claude 'shadow' Cavanaugh President =
and CEO=20
of G2I) and his email <A=20
=
href=3D"mailto:shadow@g2interactive.com">shadow@g2interactive.com</A>=20
seems real open to answering questions and has an EPIC =
system=20
himself and tells me they/he is currently working on a mode =
to=20
interface the EPIC and Cougar. So I hold out hope =
there will=20
be MFD/HUD data.</SPAN></FONT><o:p></o:p></P>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
style=3D"FONT-SIZE: =
12pt"> <o:p></o:p></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><o:p></o:p></P></BLOCKQUOTE></BLOCKQUOTE>=
</BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></DIV></DIV></BLOCKQUOTE></BODY></=
HTML>
------=_NextPart_000_002D_01C21109.7D76A2E0--