Re: Changing iEngine::CreatePortalContainer signature

Problem is that the cullers don't keep superflous lists of objects,  
they just add them to their tree.
Obviously it's not really sane to add an invalid bbox to a spatial  
tree (the old kd-tree just gave them some magic bounding box, but I'm  
not really in favour of that tbh). So if we don't assume objects are  
valid upon Preparing them we'd have to build some kind of "currently  
invalid" list in the cullers to manage objects that cannot be culled  
and use different callbacks for those or such.

Anyway, given that such meshes are essentially only meshes that are  
currently being prepared I don't think that overhead is really worth it.

Zitat von res <[email protected]>:

> On 09.01.2014 17:07, Matthieu Kraus wrote:
>> Well, it would be an edge case if we had an empty (but valid) bbox for
>> such meshes located at their position - or well, at least from a
>> culling point of view, as we could actually test it for visibility
>> then. However as it stands now it pretty much is invalid, so I'm not
>> sure what to make out of it.
>
> What about skipping culling for meshes returning an invalid (max < min)
> or empty meshes? They could simply be treated invisible.
>
> -f.r.




------------------------------------------------------------------------------
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today. 
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk