Message-ID: <3436D883.658D@geocities.com>
Date: Sun, 05 Oct 1997 13:00:03 +1300
From: Craig Rennie <carrac@geocities.com>
Reply-To: carrac@geocities.com
X-Mailer: Mozilla 3.0 (Win95; I)
MIME-Version: 1.0
Newsgroups: rec.games.computer.quake.editing
Subject: Re: Poly count affected by VIS?
References: <3431C5DF.5737E118@vanderbilt.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: ras5.wgtn.comnet.co.nz
Lines: 33
Path: clanworld.com!news.webspan.net!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!howland.erols.net!math.ohio-state.edu!uwm.edu!spool.mu.edu!newsspool.sol.net!munnari.OZ.AU!comp.vuw.ac.nz!comnet.co.nz!ras5.wgtn.comnet.co.nz
Xref: clanworld.com rec.games.computer.quake.editing:8917

Taylor Strait wrote:
> 
>     Hey folks, here's my problem.  The level i'm making is not having a
> good time with the Quake engine's tendancy to pre-render around corners,
> etc... My average poly count is 1000.  I have a fair amount of 90'
> angles but unVISed quake still renders them.  It chokes the hell out of
> my monster3d.  When I VIS it, will it be playable or am I stuck to
> actually simplifing my level?
> 
Yes, it will be far more playable, because VIS takes out all polys
which  will never be seen, and calculates which should be visible from
any given point.
(I think, pretty sure about this) :-)
plus try, "R_DRAWORDER 1" to see what is being drawn.


>     Also, is there a way to make REAL glass without creating a spike
> shooter?  (and using func_wall?)

Try QuakeLab:Editing for an example of this, I think its here, havent
been there for a while.

> 
> If you could reply via email or both i'd appreciate it...
> 
> Taylor
> 
>     ---------------------------------------------------------------
> 
>                                Name: vcard.vcf
>              Part 1.2          Type: text/x-vcard
>                            Encoding: 7bit
>                         Description: Card for Taylor Strait
