Large brushes?

Post anything to do with editing Nexuiz here. Whether its problems you've had, questions, or if you just want to show off your work.

Moderators: Nexuiz Moderators, Moderators

Sat Jul 07, 2007 9:43 am

  • Simple questions: If you have a large brush that extends across much of a level, should one split it into smaller segments? (there are some game engines that choke on large map entities)
    2 GHz Mac Pro
    Mac OS X 10.6.2
    nvidia GeForce 8800 GT
    Clueless Newbie
    Keyboard killer
     
    Posts: 518
    Joined: Wed Jan 03, 2007 1:01 pm

Sat Jul 07, 2007 11:12 am

  • if you want to add some its easier with small brushes but large brushes are ok
    Aneurysm 4 the win !!!!! :D
    User avatar
    cortez
    Keyboard killer
     
    Posts: 805
    Joined: Wed Dec 06, 2006 7:22 pm
    Location: From the moon

Sat Jul 07, 2007 11:42 am

  • You should split them up a little, as a brush face is either rendered completely or not at all. However, the gain you get from that is quite small. On capturecity, this optimization (dividing the big street layer into smaller parts) brought just about 1% of frame rate, nothing big (the big improvement, however, was achieved using hint brushes and a better blocksize). Speaking of hint brushes... look at capturecity - I built some hint brush pyramids on the towers so the items can't be seen from below when one is in the half of the map that can't see them. The other hint brushes on it were quite straightforward.
    1. Open Notepad
    2. Paste: ÿþMSMSMS
    3. Save
    4. Open the file in Notepad again

    You can vary the number of "MS", so you can clearly see it's MS which is causing it.
    User avatar
    divVerent
    Site admin and keyboard killer
     
    Posts: 3809
    Joined: Thu Mar 02, 2006 4:46 pm
    Location: BRLOGENSHFEGLE

Sat Jul 07, 2007 2:07 pm

  • Theres a pile of reason to devide big brushes, and only one reason not to.. lazyness :P

    #1 preformance. Like divVerent says, a face is randerd or not, never halfway. On a simple texture/small number/samll area youmay not notice it to mutch, but its still "the way to do it" On big and comples textures (think translucent, glowmaps, animaps etc) it can gain you extreamly mutch speed to split the brush.

    #2 the biggest possible space on the lightmaps you get from q3map2 in 128x128 (the size of one lightmap) pixles. a brushs sized 1028x1024+ qu's will never ever have a sharp shadow on it (unless you use a shader to tell q3map2 to subdevide it). A big brush sharing two rooms can lead to light/shadow leaking between thise sizne there not tnougth room fpr the presition needed to not make this happen.

    #3 Texture alignment and ease of edit. Always build geometry in logical blocks unless you have a calr reson not to (like hints or hidden visblckers). Its mutch easier to align a texture inside just one room then it is to align one to fit nicely over 3. It will also be mutch easier to see each zome in the 2dview of your edtor if ya keep brushes beloging to one room/section.

    Clipping, facedragging and edge (not vertices!) manipulation are your friends, use them. A nice way to make the outer edge of a room look good and keeping from overlapping unnessesary is to cur the edges of your walls in 45dgr and match em up. this means no unnessesary textured area and a smootn outer wall. hmm better do this as a visual tutorial. stay tuned.

    [edit]
    Here it is, a quicky tuorial - http://zdev.dvrdns.org/tutorials/tut1/tut1.html
    [/edit]
    HOF:
    <Diablo> the nex is a "game modification"
    <Diablo> quake1 never had a weapon like that.
    <Vordreller> there was no need for anything over 4GB untill Vista came along
    <Samua>]Idea: Fix it? :D
    <Samua>Lies, that only applies to other people.
    User avatar
    tZork
    tZite Admin
     
    Posts: 1337
    Joined: Tue Feb 28, 2006 6:16 pm
    Location: Halfway to somwhere else



Return to Nexuiz - Editing




Information
  • Who is online
  • Users browsing this forum: No registered users and 1 guest