Article View: comp.sys.ibm.pc.games.action
Article #7293Re: Which 3D accelerator card to get: Diamond or Creative Lab?
From: we... Werner Punz
Date: Mon, 02 Oct 1995 00:00
Date: Mon, 02 Oct 1995 00:00
27 lines
1686 bytes
1686 bytes
pa...@clandcen.co.nz (Paul Lush) wrote: >In <442s49$g...@newsbf02.news.aol.com> john...@aol.com (JohnDonld) writes: >>Sure, Nvidia is using a cheat to get around rendering polygons. The card >>is meant to be a low cost game board! Creative's board cost more but you >>are also geting over 2x the polygon performance. You get what you pay >>for. Creative's board offers the best performance and also has the most >>support! Creative made over $1.2 Billion last year and they will not >>offer you inferior technology. I don't know anything about the 3d Blaster but I read an article about the NVidia chip used in the diamond Card here is a short summary: Video Acceleration Sound hardware 3d Accleration on curved basis Textures held in Computer RAM No hardware Z-Buffer !!!!!!!!!! Can use video as textures. I think the lack of a Z Buffer costs lots of performanc. I still don't know what to think about this chip. And since most of the new 3d games will be windows based due to a lack of a standard api the curved 3d acceleration is pretty useless. Werner Punz we...@inflab.uni-linz.ac.at
Technical Details
Message-ID:
<44p7ho$bs1@alijku06.edvz.uni-linz.ac.at>Path:
mbox-mo1.pugleaf.net!unknown!not-for-mailReferences:
<442h5n$84n@epx.cis.umn.edu> <442s49$g3k@newsbf02.news.aol.com> <usAbwABMBh107h@clandcen.co.nz>Show Full Headers
Complete Article Headers
From: we...@inflab.uni-linz.ac.at (Werner Punz) Subject: Re: Which 3D accelerator card to get: Diamond or Creative Lab? Date: 1995/10/02 Message-ID: <44p7ho$bs1@alijku06.edvz.uni-linz.ac.at> X-Deja-AN: 116899227 references: <442h5n$84n@epx.cis.umn.edu> <442s49$g3k@newsbf02.news.aol.com> <usAbwABMBh107h@clandcen.co.nz> organization: Johannes Kepler University Linz reply-to: we...@inflab.uni-linz.ac.at newsgroups: comp.sys.ibm.pc.games.action MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit