PDA

View Full Version : VS2008 - Maya2009 devkit troubles

technicallySpeaking
07-18-2009, 11:06 PM
Hello to all who read this:

Before you reply, please note I do not know C++, but I can figure some stuff on my own so try to help if you can. Also I am semi-new to Maya and this is my first forum post ever. So with that, here's my dilemma:

I want to use the multiWayConstraint on Maya 2009 but when I downloaded it and set it up Maya notified me that the plug-in was compiled against an older version of Maya. Fair enough I did a little research and discovered VC 2008 is the compiler(?) for the Windows API(?). Also I have 2 .cpp source files and the header for the plug-in. I downloaded a 90-day trial of VS2008, I unpacked the devkit and placed the appropriate files in their respective directories in order for VS to recognize the template. All seemed well until I tried to start a new project on VS, I have the Maya icon but when I go to create a new project... it fails and does nothing. I downloaded VC 2008 express w/ SP1 but I don't see the template on there so now I am at a loss.

If you know what is happening and it's a easy fix by all means please explain. Or if you have the plug-in compliled for 2009 that would be awesome too. I see a "Template hotfix" next to the windows 32 compiler info, and I don't know if the software came with that so if someone knows where to get that as well it would be greatly appreciated. Thanks in advance for any help!
cbamber85
07-20-2009, 01:02 AM
Open the wizard vsz file and change the 'Wizard' line to: Wizard=VsWizard.VsWizardEngine.9.0Remember, what you are doing may not work anyway, because the node may use API commands that have been depreciated. Only one way to find out though...
technicallySpeaking
07-20-2009, 05:27 PM
Thanks cbamber85,

The code change worked and thought I could figure it out from there but it's far more complicated than I thought. I appreciate the attempt though. Maybe somebody else who has this problem will benefit from this thread. Just for further reference what are the chances the API commands have changed? I believe the node is just a few years old (2007ish?). I might hold on to it just in case I beef up on my C++, maybe that's wishful thinking. Anyway, good luck with the job hunt, I will be doing the same this time next year.
cbamber85
07-21-2009, 08:59 AM
The chances aren't high that any commands have been depreciated to be honest.

Read through the API Guide in Developer Resources in the Help file, it's a gentle introduction to doing all the common API tasks. And learning to build tools in Maya makes you very employable. :)
mercuito
07-25-2009, 02:34 AM
This might save you some time, I've already compiled for win32, and win64 for maya 2009. I wouldnt really consider this a proper multiway constraint tho.. seems buggy for me.

I had to take docs and example scenes out to reduce file size, i assume you already have those
JimmyM
09-15-2009, 06:43 AM
Thanks for posting the thread. I had the same problem after installing the Visual C++ 2008 Express Edition. I struggled the whole night trying to make it work; Only to find out it was only one Line. It works like a bomb, thank you very much
Robert Bateman
09-15-2009, 11:05 AM
Remember, what you are doing may not work anyway, because the node may use API commands that have been depreciated.
I started playing with the API circa 98/99 ish. Since that date there have been precisely 2 occasions when i needed to change code due to an API upgrade.

1. When the added REQUIRE_IOSTREAM (not actually a code change)
2. When they changed the phase variable on the turbulence field from a float to a vec3.

That's it in the last 10 years. I'd be extremely surprised if you couldn't compile the code as is - especially for something so recent that shouldn't be using any deprecated methods anyway.

If autodesk gets their way, it looks like they'll be fecking that stability up for everyone in the next release though :(
CGTalk Moderation
09-15-2009, 11:05 AM
This thread has been automatically closed as it remained inactive for 12 months. If you wish to continue the discussion, please create a new thread in the appropriate forum.