well not if they changed its behavior... and you ran into the a combination which isn't supported.
i usually go the other way around, compile with the minimum SDK version you can. is there any reason you can't compile with the 2013 SDK for use in 2013? again, in this case if you want to use your plugin in 2014sp2 you need to use that SDK version. i also think you have your understanding of backward/forward compatibility flipped. On Wed, Oct 23, 2013 at 10:40 AM, Mathias N <[email protected]> wrote: > The plugin loads fine in 2014 SP2 even when compiled against the 2013SP1 > SDK; it is not forward but backward compatibility that appears to be broken. > > Although the only proper rundown of SDK backwards compatibility I can find > is from the 2011 SDK wiki, it states that "The Softimage SDK is backwards > compatible with previous versions of Softimage and XSI", with exceptions > for a few classes prior to 2010. The 2014 SDK similarly notes that "Some of > the custom ICE node classes may break backwards compatibilty as of > Softimage 2010", while making no mention of any new backward compatibility > issues. > > This would suggest that plugins compiled against the 2014sp2 SDK, > including use of the CICEAttributeDataArray class, should work in earlier > versions, provided they do not make use of any newly introduced methods. > Am I wrong? >
