Pibuz wrote:Ehi Dale: is there a way we can check if automatic instancing feature is actually working or not? I have the suspect it isn't, in one of my scenes..
There are some cases where automatic instancing may result in longer export times than the manual method that was used in previous SkIndigo versions. It is difficult to explain why. Basically, if you have lots of instances that only contain a relatively small number of faces, the efficiency gained with automatic instancing is reduced. Efficiency with auto-instancing is also affected with how groups and components are 'nested'. This was not the case with older SkIndigo versions (because typically, the user would 'instance' the top-level component and all sub components would be effectively 'exploded' during the export process)
For greatest export efficiency, try to minimize nested components. Take a look at a leaf component of a tree. You might have 1 trunk x 20 branches x 20 sub-branches x 20 leaves. However, if each leaf only contains two faces, you will have 8000 instances of the leaf but only two faces for each instance.
Now, what if the entire tree is a component and you have 100 copies of it? Now you have 800,000 instances of the leaf component (but only two faces per instance!)
To make export more efficient for this type of scene, you could consider exploding some of the nested components to increase the number of faces that are inside each instance.
To answer your basic question, I assure that instancing IS working with 3.2.2.
I hope this was helpful. A tutorial on this would be useful, I bet.