Hi Andy, In Andrews' code just calling the Softimage mesh methods once and saving that result for reuse would probably eliminate his performance issues.
What you are suggesting is the next level when you find that the data stored in the Softimage containers is not in a format where it can be accessed quickly. Great advice but there are easier things to fix in Andrew's code first IMO. Cheers. -- Brent From: [email protected] [mailto:[email protected]] On Behalf Of Andy Nicholas Sent: 29 July 2017 20:26 To: Official Softimage Users Mailing List. https://groups.google.com/forum/#!forum/xsi_list <[email protected]> Subject: Re: EdgeRing ALG for n-gons Hi Andrew, I believe what Brent is suggesting is to request the data from Softimage once, cache it in whatever way makes the most sense for your application, and then run your algorithms on that. When I wrote the “Taut” plugin for Softimage, I built all the adjacency information and stored it using STL containers (maps, etc.). It meant that I could optimise the data structures to Taut's functionality and it generally ran pretty fast. Andy On 29 Jul 2017, at 07:43, Andrew Prostrelov <[email protected]<mailto:[email protected]>> wrote: Can you tell a bit more about optimisation and efficient calls pls. I have lots of question about XSI objects and classes best practices. If i understand your suggestion right i should alwayse preffer XSI reference containers (EdgeRefArray etc) to value containers like CLongArray, CValueArray etc. Or not ? I also often use curMesh.GetEdges().GetItem() aproach to get one specific component instance with known index. I suppose this way also is slow. What should i do in this situation ? ------ Softimage Mailing List. To unsubscribe, send a mail to [email protected]<mailto:[email protected]> with "unsubscribe" in the subject, and reply to confirm.
------ Softimage Mailing List. To unsubscribe, send a mail to [email protected] with "unsubscribe" in the subject, and reply to confirm.
