Hey Steve, i can run all samples without any problems (at least the ones i tried). You're right, they died during my first runs as well. But i changed some project settings, and they seem to work without any problems:
- multi byte characters - linked my crt as static so right now, everything is fine. I just encountered some strange errors when setting up some host memory, have to compare this with visual studio 2005 tomorrow. I also encounter some other problems (in terms of crashes when constructing the node) if i'm running my plugin in a debug session. So yeah, there might be something, i probably didn't step on it until *now*. I found out that when i allocate all of my memory during construction of my plugin, there are no crashes. Said, i need to compare this with 2005 tomorrow. Thomas > Thomas, > > The problems are devious and numerous. Plugins would randomly crash upon > connection in a script; the viewer would show banding and snow, and things > just didn’t work in multi-threaded mode. If you take any of the sample > nodes, for example, and try to compile them in either 2010 or 2008, then > instantly die. Compile them in 2005 and they work the first time. > > I now will use nothing but 2005 in any of my development, and things have > been *infinitely* better since I made that decision. > > Steve > > > From: [email protected] > [mailto:[email protected]] On Behalf Of Thomas > Obermaier > Sent: Thursday, May 19, 2011 11:46 AM > To: [email protected] > Subject: Re: [Nuke-dev] Visual Studio 2010, 2008, and 2005 > > 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. > > [Smile] > > > > > > _______________________________________________ > > Nuke-dev mailing list > > [email protected]<mailto:[email protected]>, > http://forums.thefoundry.co.uk/ > > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev > > > (CONFIDENTIALITY NOTICE: The information contained in this email may be > confidential and/or privileged. This email is intended to be reviewed by only > the individual or organization named above. If you are not the intended > recipient, or an authorized representative of the intended recipient, you are > hereby notified that any review, dissemination or copying of this email, > or the information contained herein is strictly prohibited. If you have > received this communication in error, please notify the sender by return email > and delete this email from your system. Thank You.) > -- NEU: FreePhone - kostenlos mobil telefonieren! Jetzt informieren: http://www.gmx.net/de/go/freephone _______________________________________________ Nuke-dev mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev
