|
Description
|
Simple suggestion. Basically any invisible prim (a prim which can be determined to have a fully transparent alpha map, or more easily a transparency of 100%) should not be rendered by the client except when highlight transparent is turned on.
As mentioned in VWR-172, spheres seem to have a larger than before performance hit in current versions, this occurs even when the spheres are fully transparent, meaning they are still rendered when they have no need to be.
There is a surprisingly large amount of in-world content that is actually invisible until needed, or is simply never needed (e.g detection volumes). There is no need to render these, in fact there's no need to even consider them for ANYTHING except if you are trying to edit them, in which case they could be downloaded/rezzed when you enable 'highlight transparent'.
|
Simple suggestion. Basically any invisible prim (a prim which can be determined to have a fully transparent alpha map, or more easily a transparency of 100%) should not be rendered by the client except when highlight transparent is turned on.
As mentioned in VWR-172, spheres seem to have a larger than before performance hit in current versions, this occurs even when the spheres are fully transparent, meaning they are still rendered when they have no need to be.
There is a surprisingly large amount of in-world content that is actually invisible until needed, or is simply never needed (e.g detection volumes). There is no need to render these at all; invisible faces could be removed, or entire objects ignored if they are fully invisible.
|
New Feature
Open
Major
Don't render invisible prims
