From: jcaesar@mediaone.net
To: <ml@qoole.com>
Reply-To: ml@qoole.com
Date: Sun, 1 Mar 1998 17:15:37 -0800
Subject: Re: Qoole 2.33test bug report

A microbrush is just that.. a very very very small brush, that is probably
too small for bsp to worry about cutting up.  It's only a warning, and
shouldn't really pose any problems, but will probably help fracture you bsp
tree a bit more than normal.  Until Qoole adds a find brush command, I'd do
the following:

Note the brush number after bsp.

Get and run QERadiant.  Save your Qoole as a .map and load into QERadiant.
Use the search menu to find the brush by number.

It should get hilighted and centered in the windows (if you have multiple
views).  Note where the brush is, quit QERadiant, go back to Qoole and
delete it (and restructure surrounding brushes if necessary).  Microbrushes
are usually caused by CSG.

Joel

-----Original Message-----
From: sun <sun@wanadoo.fr>
To: ml@qoole.com <ml@qoole.com>
Date: Sunday, March 01, 1998 3:24 PM
Subject: Qoole 2.33test bug report


>dunno if u guys find out about that, or if it is intended
>
>prefab u load with the 2.33test release doesn't have
>textures!..
>
>beside looks like 2.33test fixed some of the leak
>problems i was getting with 2.31
>2.31 .map bsping result in LEAK error
>2.33test .map bsping is ok...
>
>sounds good for future release :)
>
>another things what is a microbrush error ???
>(when u bsp)
>
>
>