Tutorial: Visible bboxes

[behind_you]

[Spike]

note that hull positions are not identical to bbox positions - anything clipping against world has a different bbox, which is a function of its absmin, the size of its bbox, and the hard-coded hull sizes of the qbsp+engine.

[GiffE]

[daemonicky]

[behind_you]

[dreadlorde]

[GiffE]

[mh]

As Spike said, there are two different types of bounding boxes in use in the engine - server-side and client-side (or more specifically, renderer-side).

Regarding the size of the server-side bounding-boxes, assuming you don't want gameplay changes, the golden rule is - don't mess with them.

Client-side you can do what you want. Adapt MDL bounding boxes to per-frame, derive brush model bounding boxes from the actual surface vertex positions, rotate and scale them, whatever you want. They're only used for view frustum culling and so long as the resulting box is still valid for use with that, they're your's to play with.

[behind_you]

[mh]

[behind_you]

[mh]

[behind_you]

[ceriux]

i dont think changing your bboxes for mapping purposes will matter. if you cant fit through a hole you wont be able to no matter what, that's all dependent on something in the mapping side of things, i think.

(just assuming that's your reasoning)

[metlslime]

1. you can't rotate bboxes in quakec; if you rotate the entity the box will stay un-rotated. They are literally "axis-aligned bounding boxes" which means they are always axis-aligned.

2. if you resize bboxes in quakec, it will work for entity-v-entity and traceline-v-entity collision, but entity-vs-world collision will still use one of the standard collision hull sizes.