In the case of a Sphere drawn in WYSIWYG this is very simple: access the SphereвЂ™s Properties and reduce its вЂњbase complexityвЂќ by setting the Stacks & Segments values to a lower value of 6 or 8 this will result in a Blue Bounding Box now surrounding the object yes, the visual quality of the Sphere has decreased, but this is likely acceptable, especially if the object doesnвЂ™t need to be seen up-close. The solution, therefore, is to reduce the number of polygons that make up the object, while at the same time keeping it a single/cohesive object.

(Modern video cards are great at processing large numbers of polygons, but only if these are submitted for processing (by the software) at the same time (in a batch) as opposed to one-by-one.) Keeping the object as an actual Sphere is not ideal either though, because performance would be slightly improved if the unbroken/Mesh-Consolidated Sphere had a Blue Bounding Box. 12 Stacks & 12 Segments) its Bounding Box is Cyan if you then Break that Sphere into Surfaces (polygons), you will end up with a large number (264 to be exact) of Blue Bounding Boxes (one for each Surface/polygon that the Sphere was broken into) this may seem like a better option but it is not, because these polygons no longer form that single/cohesive sphere object, so each must be processed individually in order for the same sphere to appear on screen. For example, when you draw a Sphere with default options (i.e. As such, your aim should be to have a lot of Blue Bounding Boxes in your model, but for these not to be clumped together/вЂќdensely-packedвЂќ. Using this system, the model within a file may be visually-analyzed (inspected) in order to determine which objects are geometrically inefficient: the more complex an object, the more processing it requires вЂ“ which (it goes without saying and as with all things in computing) results in lower performance.

The complexity calculations are based on the number of polygons that make up objects (or LEDs in the case of LED Walls) and are an internal approximation of how much work is required to rasterize the object (i.e. In essence, an object with a Blue Bounding Box is less complex than one with a Cyan Bounding Box, which is, in turn, less-complex than one with a Green one, and so on вЂњthrough the spectrumвЂќ / through Yellow, Orange and Red. amount of polygons/elements it is made of) now only colours are used.

WYSIWYGвЂ™s Bounding Box system is actually much simpler to understand than it used to be, because where in the past colours and thickness used to represent objectsвЂ™ complexity (i.e. I will do this very soon, but in the meantime, here is the explanation (along with a bit more information than you yourself probably need, but I figured I may as well be thorough and add some more basic points, so less-experienced users can take advantage of it too). My bad that I never got around to updating the optimization articles that are linked in the thread you mentioned above.

Where to find cast wysiwyg models