I have some pics of a WIP map I want to post soon but I have a question about func_details since I'm now going around and working on them.

When turning something into a func_detail, is it better to combine several brushes into a single func_detail or to make each individual brush its own func_detail? Or does it make no difference whatsoever and it's just up to personal preference?

For example, if you your roof is made out of two pieces or if you have a set of stairs, should each individual stair be its own func_detail or can you safely make one entity out of the whole staircase?

Is doing it either way going to effect performance/lighting/anything else?

to the best of my knowledge func_detail can be done either way. I group similar stuff like I would func_detail all details for one building together.

Performance wise or lighting or anything else isn't really effected. Func_detail is just so vis doesnt use the detail to calculate visibility.

hopes this helps

For extreme optimization concerns, the less func_detail entities there are the better off you'll be.

We're talking extremely large and detailed maps, where you may be faced with MAX_ENTITIES errors, when the map contains over 4096 different entities (all entities). When this happens, your compile will fail. At that point, if you can still merge together func_detail entities within the same vis leaf, you should do so.

There won't be performance changes as long as the new func_detail doesn't cross over different vis leafs. If it does your optimization (hints and areaportals) will be overriden, and the entire func_detail will be rendered when you used to have each part separately before.

Clearly this is not going to happen to you, but I felt like giving the most complete answer.

As far as you're concerned, I would try and stick with per area based entities, where you'll have a easier time selecting a group of objects you may want to move as opposed to each segment of detail individually.

Thanks a lot, that seems about what I figured.