SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Technology Stocks : Intel Corporation (INTC)
INTC 36.78+2.7%Nov 26 3:59 PM EST

 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  
To: Scumbria who wrote (76566)3/17/1999 11:24:00 AM
From: Haim Barad  Read Replies (2) of 186894
 
Depth complexities of 100 are very rare. In fact, good scene management (CPU) will go a long way to keeping the depth complexity low (of course, this depends upon content). Also if a SW geometry engine is not in front of the HW, then all the content (even backfacing and completely clipped primitives) will be sent over the bus to the HW. This exacerbation of bus traffic over a SW geometry engine isn't a clear win for HW engines. It's going to be content driven.

Certainly, it's not a clear case that HW geometry engines will completely replace SW engines. Many SW vendors will not use a "standard" lighting algorithm and prefer to light their own vertices. There's other issues as well (e.g. specialized higher order surface rendering, etc) that HW will be slow to adapt. Certainly it'll come with time, but usage by SW vendors will be much slower.

In any case, this is probably not the place for a SW/HW debate on geometry engines. I can certainly see pros/cons on both sides.

Haim
Report TOU ViolationShare This Post
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext