From: "Thomas, R. (Russel) COGHB" To: "'ml@qoole.com'" Reply-To: ml@qoole.com Date: Tue, 13 Jan 1998 13:21:35 +0200 Subject: RE: q2 radiosity and comp'ing in general gawd, 2 days? is there a medium solution for checking your maps as you go along? Imean, say after the 2 day compile time you see something you don't like so you change it. to see if your changes are cool or not you have to wait another 2 days? arhgh. I know what you mean about no radiosity. I tried just bsp and vis and got a fullbright map. Is that how you preview all your maps? cos that compile time bites. _yoda <"patience? bah!"> > -----Original Message----- > From: christer dahl [SMTP:christer.dahl@sa.erisoft.se] > Sent: Tuesday, January 13, 1998 12:50 PM > To: ml@qoole.com > Subject: Re: q2 > > > hi all, > > > > dumb question time : what the hell is radiosity and why does it take > the > > longest of the three processes? > > Not a dumb question. > > Radiosity is a way of computing lights and shadows from the light > source, compare > it with raytracing that computes it from the viewers eye. > It also computes the amount of secondary light that is emitted from > the > textures, and > that is what makes it so nice in quake2. > > Without radiosity your map will be all lit up without shadows or > completely dark, depending on if you VISed the map or not. > > As long as your map is small and not that complex, the radiosity will > take the longest > time, but dealing with large complex maps with a variety of structures > and textures the VISing will take by far the longest time when > compiling. > > My last map took me 50 minutes of radiosity, 4 minutes of qbsp and 2 > days for VISing > on a 200mmx, 64mb ram > > /AwfulSwede