X-Virus-Scanned: clean according to Sophos on Logan.com Return-Path: Sender: To: lml@lancaironline.net Date: Thu, 23 Aug 2007 11:14:37 -0400 Message-ID: X-Original-Return-Path: Received: from mx3.pshift.com ([216.57.116.8] verified) by logan.com (CommuniGate Pro SMTP 5.1.11) with ESMTP id 2280152 for lml@lancaironline.net; Thu, 23 Aug 2007 09:25:32 -0400 Received-SPF: none receiver=logan.com; client-ip=216.57.116.8; envelope-from=colyncase@earthlink.net Received: from ccaselt2 (unverified [216.57.118.64]) by mx3.pshift.com (Vircom SMTPRS 4.4.568.54) with SMTP id for ; Thu, 23 Aug 2007 09:24:44 -0400 Received-SPF: none (mx3.pshift.com: domain of colyncase@earthlink.net does not designate any permitted senders) X-Modus-BlackList: 216.57.118.64=OK;colyncase@earthlink.net=OK X-Modus-RBL: 216.57.118.64=Excluded X-Modus-Trusted: 216.57.118.64=NO X-Modus-Audit: FALSE;0;0;0 X-Original-Message-ID: <001e01c7e589$054b7520$0302a8c0@nvidia.com> From: "Colyn Case on earthlink" X-Original-To: "Lancair Mailing List" References: Subject: Re: [LML] Re: fallability in the digital age X-Original-Date: Thu, 23 Aug 2007 09:25:06 -0400 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_001B_01C7E567.7DFE52C0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.3138 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138 This is a multi-part message in MIME format. ------=_NextPart_000_001B_01C7E567.7DFE52C0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Brent, thanks for the interesting and informative post. I have to disagree that you would emit detailed terrain for lack of = processing resources. At this point, the amount of 3d processing power = available in a single chip is huge. (disclaimer: I'm a chip architect = for nVidia) The chips we are currently making are designed to render = each presented frame multiple times for special effects, and we do this = at large screen sizes at 100+ fps in benchmark conditions. Managing = 60fps for typical cockpit screen resolutions is not really a challenge = anymore. Granted the host cpu and storage required to make it look = pretty are non-trivial. The second point you make, about confusing the pilot with something = that might look like a symbol seems to imply that vfr pilots would be = the most confused of all. ....and yes that happens. So I think it's going to happen and someone will do a decent job of = it. Notwithstanding, I have one column of vac powered gyros and one = column of electric powered gyros, for now. Colyn ------=_NextPart_000_001B_01C7E567.7DFE52C0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Brent,

thanks for the = interesting and=20 informative post.

I have to disagree = that you=20 would emit detailed terrain for lack of processing = resources. At=20 this point, the amount of 3d processing power available in a single chip = is=20 huge. (disclaimer: I'm a chip architect for nVidia) The = chips we are=20 currently making are designed to render each presented frame multiple = times for=20 special effects, and we do this at large screen sizes at 100+ fps in = benchmark=20 conditions. Managing 60fps for typical cockpit screen = resolutions is=20 not really a challenge anymore. Granted the host cpu and = storage=20 required to make it look pretty are non-trivial.

The second point you = make, about=20 confusing the pilot with something that might look like a symbol seems = to imply=20 that vfr pilots would be the most confused of all. ....and = yes that=20 happens.

So I think it's = going to happen=20 and someone will do a decent job of it.

Notwithstanding, I = have one=20 column of vac powered gyros and one column of electric powered gyros, = for=20 now.

Colyn

------=_NextPart_000_001B_01C7E567.7DFE52C0--