Hey Thomas, are you making much use of the STL in your plugin? that seems to introduce many of the issues.
-- Colin Doncaster Peregrine Labs www.peregrinelabs.com On 2011-05-19, at 2:45 PM, Thomas Obermaier wrote: > Hi Steve, > > can you explain me what you tried exactly? I'm working on a (more or less > heavy) Nuke plugin right now, doing it with VC2010 and everything is still > fine. > > Don't want to run into troubles though, but it looks good right now. The only > thing that might bug around (IMO) is memory management. However, i don't have > problems with that. (now...) > > just curious, > Thomas > > > > Am 09.05.2011 17:45, schrieb Steve3D: >> >> For going on three weeks now, I've been experimenting with various Visual >> Studio versions in doing Nuke Plugin development. That entire time has been >> spent trying to track down various and sundry 0x0000000000000000 and >> 0xFFFFFFFFFFFFFF invalid memory references from inside Nuke. >> >> Here's my final verdict: >> >> You can't do Nuke Plugin development with anything other than Visual Studio >> 2005. >> >> To use a Tron-Ism... End of Line. >> >> >> >> _______________________________________________ >> Nuke-dev mailing list >> Nuke-dev@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/ >> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev > > _______________________________________________ > Nuke-dev mailing list > Nuke-dev@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/ > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev
_______________________________________________ Nuke-dev mailing list Nuke-dev@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev
