[Gtkradiant] Minimum grid size and disappearing brushes
meridanox at gmail.com
Mon Mar 7 22:17:52 CST 2011
While I agree that it's often "best practice" to work on as large of a
grid size as possible and snap to nearest integers, it isn't and
shouldn't be a requirement. Neither Radiant or Q3Map2 snap vertices to
integers. There are situations where greater levels of precision are
desired, in the case of rotated brushes, working with patches, and as
mentioned decals. As long as such geometry is converted to detail it
doesn't hamper anything.
On Mon, Mar 7, 2011 at 10:27 PM, Nerius Landys <nlandys at gmail.com> wrote:
> I'm uneasy following what is "recommended" here. I don't think we're
> going to change the grid stuff.
> In fact, I believe that most things are snapped to integer or
> something like that. In all the maps I make, I try to make sure that
> vertices are on integer coordinates, and if that's not possible, I
> make sure that the integers that specify the planes in the .map format
> are integer.
> I noted this "bug" down and will look into it later but I'm afraid
> that probably no action will be taken to address this.
> On Mon, Mar 7, 2011 at 10:20 AM, Obsidian <meridanox at gmail.com> wrote:
>> Reported by cityy.
>> "I usually work with netradiant/1.5 and if I open a map made in
>> netradiant in 1.6 all brushes that are 0.125units in height get
>> This is probably due to minimum grid size and precision.
>> 1.5/NetRadiant has a minimum grid size of 0.125 units while 1.4/1.6 is
>> A minimum grid size of 0.125 is useful for the placement of decals. At
>> 0.25, they can still appear to float off the surface at oblique
>> angles. Recommend adopting 1.5 behaviour.
>> Gtkradiant mailing list
>> Gtkradiant at zerowing.idsoftware.com
More information about the Gtkradiant