🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: alt.comp.periphs.videocards.nvidia
Article #115

Re: Multitexture on V4/V5

#115
From: Freon
Date: Fri, 26 Nov 1999 00:00
38 lines
2706 bytes
Sebastian Kaliszewski <Sebastian.Kaliszewski@softax.com.pl> wrote in message
news:81lod5$vlk$1@euler.softax.local...
> Could you, please, first read my letter, before replying?
> If chips share memory the SHARE textures, too. There is no point in
> duplicating exactly the same data if memory is shared.
>
> That's the point. If they USED shared DDR instead of duplicated non-DDR
> they'd have cheaper solution.

Again, they cant share the textures.  Each chip has to work from it's own
set.
This is the way it was with Voodoo2 and is still the way with Voodoo5.
If there was a better way, they would have done it by now.  There has got to
be a good reason for why they cant share.

> > but would also severly limit the
> >scalability of the chipset.
>
> They simply waste memory. Now they are going too sell 64MB cards
screasming:
> Wow! 64MB RAM card! Average Joe would go for it and buy it, even if
cheaper
> card with ~40MB memory would be in all aspects better.

Nothing you said here addresses the fact that even if they could "share" it
would severely limit the scalability of the chipset.  The whole point of
VSA-100 is the ability to scale.
There is no "waste" of memory if the card is using that memory to achieve
such high fillrates.
Besides, they will be screaming xxxMpixels/sec, not 64MB RAM.

> At 1280x1024x32 with tripple buffer 24 MB of that memory is wasted for
duplicated textures. At
> lower resolutions even more is wasted.

The resolution has nothing to do with how much texture RAM is being used,
the game does.
Technical Details
Message-ID: <383f2965.0@news.mocc.net>
Path: arc1-ca.pugleaf.net!unknown!not-for-mail
References: <383930cf.8748501@news.freeserve.net> <383832F7.95FE67D7@bigred.unl.edu> <uh2ogcnmr4r.fsf@bcarhad6.ca.nortel.com> <3839adb0.9757660@63.211.125.80> <3839deba.0@news.mocc.net> <384002eb.9183814@63.211.125.80> <383b326d.0@news.mocc.net> <81giki$sce$1@euler.softax.local> <383cb50e.0@news.mocc.net> <81lod5$vlk$1@euler.softax.local>

Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: feaeb,b04d7da264d0bc06
X-Google-Attributes: gidfeaeb,public
X-Google-Thread: f4bb2,b04d7da264d0bc06
X-Google-Attributes: gidf4bb2,public
X-Google-Thread: 1045b9,b04d7da264d0bc06
X-Google-Attributes: gid1045b9,public
X-Google-Thread: 10a47c,b04d7da264d0bc06
X-Google-Attributes: gid10a47c,public
From: "Freon" <nothanks@none.com>
Subject: Re: Multitexture on V4/V5
Date: 1999/11/26
Message-ID: <383f2965.0@news.mocc.net>
X-Deja-AN: 553478629
References: <383930cf.8748501@news.freeserve.net> <383832F7.95FE67D7@bigred.unl.edu> <uh2ogcnmr4r.fsf@bcarhad6.ca.nortel.com> <3839adb0.9757660@63.211.125.80> <3839deba.0@news.mocc.net> <384002eb.9183814@63.211.125.80> <383b326d.0@news.mocc.net> <81giki$sce$1@euler.softax.local> <383cb50e.0@news.mocc.net> <81lod5$vlk$1@euler.softax.local>
X-Trace: 26 Nov 1999 17:44:21 -0700, 206.27.158.51
X-MSMail-Priority: Normal
X-Priority: 3
Newsgroups: alt.comp.periphs.videocards.nvidia,comp.sys.ibm.pc.hardware.chips,3dfx.products,comp.sys.ibm.pc.hardware.video
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300