Jump to content

Home

Auto-clip


JeeMonkey

Recommended Posts

hey all, if i am bothering people by posting too many questions plz tell me. i dont want to offend anyone.

 

[QUESTIONS]

1) how do i auto-clip a model in gtk radient 4.0??

 

[NOTES]

*i do not care about the damn size of the model tell me anyway.

*i searched the forums for this answer already and could not find it

Link to comment
Share on other sites

I'm glad you don't care about the damned size of the model, really I am...not!

 

Auto-clipping is very buggy on anything but the largest of triangles. Imagine trying to make tons of tiny little triangular clip brushes for your model 1 unit thick manually....the compiler basically does that! And as well all know, not following the grid causes...yes that's right, borked brushes. The result? You end up with invisible clip brushes near the model (if you're lucky) or across your entire map (the most common occurance).

 

Nevertheless if you're still adament to ignore advice from people who have been mapping far longer than you and ignore the advice of the creator of Q3Map2 (yes even he's advised against anything but the largest of models) Then simply add a key/value pair of spawnflags/2. Oh and I've said spawnflags two before.

Link to comment
Share on other sites

Well I was there in the last thread this was mentioned where you posted and judging from if size was irrelevant you wouldn't say it (little psyche thing).

 

I assume based on the way things are said and if you can read your own post and NOT assume you mean a small model then you should be a politician.

Link to comment
Share on other sites

Autoclip creates one clip brush for every surface, each brush being eight units thick. Why it is not two (the minimum) I do not know. Eight units is eight inches, if that, so even if Q3Map2 creates some clip brushes that make a fat collision model, you probably won't notice in game. Hell, I know I couldn't get it much better than eight units doing it myself.

Link to comment
Share on other sites

Because Q3Map2 autoclipping is a nasty, nasty hack that enjoys the smell of garbage data. Phantom blocks of clip, out in the middle of nowhere, are not an uncommon side effect of autoclipping a model that has a varying mesh density. Unless your model consists of a fairly uniform triangle size, chances are Q3Map2 will find a way to screw up the clip.

 

The moral of the story: it's on the to-do list, but it's a task that would involve actual work--so chances are ydnar won't rewrite autoclip for a good while. Until that day, only use it on terrain (and even then, don't expect miracles).

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...