When you said dotNet, I just puked a lil bit. Thanks, Jason!
Wohooow!
awsome!!!
-R
Hey guys –
Thanks for the quick feedback:
@jeddie:
I have enabled the Issue Tracking on the Google Code page – we don’t have a public SVN repo yet, so thats why we don’t have the code online but I’ll talk to my supervisor when I get into work about it.
I updated the KnownIssues page with your changes – I noticed you posted comments on there also, Thanks! Much appreciated.
I deprecated the Blur Tools download until this afternoon, I can fix those install paths and the plugin.ini config, the Py3dsMax installers should be working fine.
I’ll talk to our other programmer Matt about the system32 install on Vista x64, but we don’t run Vista at work – so we might not support that…may have to look into getting you the code.
This is great news. Glad to see progress on this project, I look forward to trying it out this weekend.
I would REALLY like to see this open-sourced so we can all contribute to making this a rock solid plugin. Plus it is very risky for our studio to build production tools around plugins we don’t have source code for. We can’t risk being left high and dry when new version of max comes out and we have to wait the plugin to be re-compiled. This is even more of an issue with beta testing 3dsmax versions.
Also, do you know if there are still licensing issues with Qt/PyQT on windows? Is a commercial license still required?
I’d be willing to get wxPython integrated as alternative since I have already done some work on this.
Thanks for sharing,
-James
New to Maxscript and such. I am a little confused as to where these files should be installed to. The root to my 3dsmax is C:\Program Files\Autodesk\3ds Max 2009 so where should I install downloads to. BTW I have 64 bit version.
Huzah! :bowdown:
Oh Hell Yeah!!!
I look forward to digging into this in hours #25-32 of my day.
(I just need to finish a time re-mapping script I am working on first)
Seriously this just kicks ass…can’t wait till I wrap up the current project just to explore this.
EDIT: Who am I kidding? F the project, I’m digging into it now!
Thanks for sharing… BLUR rocks :bowdown:
Is there a eta on a probable max2010 release? Then I could try it on 2009 now, and move over when a 2010 release appears.
Greatly admire the stuff you guys share, it’s worth quite a lot!
-Johan
@ Irishlad
You’re going to want to set C:\Program Files\Autodesk\3ds Max 2009 as your 3dsMax install path, and wherever you installed your Python 26 x64 as your python path (most likely c:\python26)
This will install plugins and scripts into your 3ds Max 2009 directory and register them to your C:\Program Files\Autodesk\3ds Max 2009\plugin.ini file. However, with 3dsMax 2009, they changed the default configs I think to store/load the plugin.ini information in your users directory – if thats the case for your setup, you’ll need to add a line to wherever that plugin.ini file underneath [Directories] that says:
blur=C:\Program Files\Autodesk\3ds Max 2009\plugins\blur
We at Blur just set it back to the way it always ran, so our installer doesn’t support that new issue yet.
I can’t give you a definitive answer on that since we don’t run 2010 in the studio, its not a high priority to get it to work internally…however, if the only change that I need to run to get it to work for 2010 is to compile with MSVC++ 2008, then it should work – I am going to give that a test run on Monday and hand it off to a friend w/ 2010 to see if it works.