Yes, there has been a SDK change in 2014 regarding strands and point cloud in general.
I don't know if it's intentional or not but we first noticed the issue when exporting time with arnold went through the roof with strands and 2014. The good guys at SitoA looked into it and the were able to change their plugin so the export time went from bad to ok. They were helped by Ho Chung Nguyen of AD. We are still waiting on confirmation that the problem will be solved on the SDK side. cheers ! Luc Girard // SHED artiste 3D 1410, RUE STANLEY, 11E ÉTAGE MONTRÉAL (QUÉBEC) H3A 1P8 T 514 849-1555 F 514 849-5025 <http://WWW.SHEDMTL.COM> WWW.SHEDMTL.COM From: [email protected] [mailto:[email protected]] On Behalf Of Stephen Blair Sent: June-27-13 2:56 PM To: Ben Houston; [email protected] Subject: Re: Accessing Strands in Softimage 2014 SP is broken? Is there a workaround? Hi You mean it works for you in 2014 but not 2014 SP1 ? We something like that when we ran a plugin compiled against the 2013 SDK in Softimage 2014. After we recompiling against the 2014 SDK, the problem went away. On Thu, Jun 27, 2013 at 2:51 PM, Ben Houston <[email protected]> wrote: Hi, While developing Alembic for Softimage, we've come across what appears to be a serious issue with stands in Softimage 2014 SP1. When we try to export strands, we are finding that in 2014 SP1 the data is actually incorrect. It seems like the first value of the strand is replicates for the other stand nodes. This is when using the C++ API to read the 2D array of values for the stands. Was there an API change or is this a real bug? It seems like a bug given that this exact code works for other versions of Softimage. If it is a bug, is there a workaround? -- Best regards, Ben Houston Voice: 613-762-4113 Skype: ben.exocortex Twitter: @exocortexcom http://Exocortex.com - Passionate CG Software Professionals.
