Hey, can you say more / do you have a link about this? I mean, for what reason are BSP trees phased out, and what are they replaced with? (quad/oct tree? AABB trees? or something entirely different?)
Hey, can you say more / do you have a link about this? I mean, for what reason are BSP trees phased out, and what are they replaced with? (quad/oct tree? AABB trees? or something entirely different?)
More memory, bandwidth and cache means that more of your solutions are per-pixel instead of per-vertex and you can tolerate overdraw if it means you get to have higher polycount models. Likewise, the environment collision that was leveraged by the BSP process reduced the number of tests against walls, but introduced edge cases and hindered general-purpose physics features. Scaling physics leads in the direction of keeping the detailed collision tests at their original, per-poly detail, but doing things with sorting or tree structures to get a broadphase that filters the majority of tests against AABB or sphere bounds.
On a Wii(original Wii) 3D action game I helped ship, we just rendered the whole level at once, using only the most basic frustum culling technique; the hardware did the lifting, mostly through the z-buffer.
On top of my head as I remember it.. one of the reasons for Quake's use of a bsp was to allow back to front rendering of the world geometry without the use of a zbuffer. This was required to get decent performance with the software rasterizer.
I'm not 100% sure what's most commonly used these days, but for a large open world requiring data streaming, I could see the use for something like an octree and even portals.