the real shame is, that it was deceiving you... you got none of the advantages of the changes made to the SDK. from what i understand (which i am still a c++ n00b) it loads the sicppsdk.dll dynamically from the version of softimage which is loading the plugin and that library doesn't have the new features. the feature you were trying to use changed drastically it isn't the case that it just didn't exist and can be ignored.
BTW, you can use a build system like CMake ( https://vimeo.com/41179344 ) to make sure you are always compiling with a specific version of softimage more easily. On Wed, Oct 23, 2013 at 11:17 AM, Mathias N <[email protected]> wrote: > I made the move to the 2014SP2 SDK a while back hoping that some of the > problems I was encountering were bugs rather than me simply having no idea > what I was doing (Spoiler: it was the latter). Seeing as all my plugins > compiled against it also worked fine in 2011 I figured it would be > preferable to stick with it. Clearly I was mistaken. > > If doing so does not provide any benefit I guess I have no reason to use > the newer SDK. Unless 2014SP2 does indeed begin breaking 2013 SDK plugins, > in which case I'll have to compile and release multiple flavors. > Bit of a shame though, seeing as everything else seems to be working just > fine using the 2014SP2 SDK. > > > > > On Wed, Oct 23, 2013 at 7:58 PM, Steven Caron <[email protected]> wrote: > >> ya, what advantage where you hoping to attain by using the newer SDK? >> >> >> On Wed, Oct 23, 2013 at 10:54 AM, Mathias N <[email protected]> wrote: >> >>> Huh, so I guess I should stop using the 2014SP2 SDK for my 2011 plugins. >>> >>> Thanks for clearing that up. >>> >>> >
