- Fri Jan 19, 2007 11:21 am
#205801
The problem you're having is most likely due to your particular set-up and we would gladly help you get the plug-in running if you could provide more details. Since it works for everybody else, saying "it doesn't work" isn't enough for us to be able to track down the problem. The following information would be useful:
- system details: Windows version, Max version
- plug-in version; can you double check that you are indeed running 1.0.77 by going to Customize -> Preferences -> Maxwell? The version number should be displayed there.
- steps needed to reproduce the bug; did you try making a box in a new scene, setting Maxwell as the current renderer and hitting render? Does that break or do you need to do something more to trigger the problem?
- an example scene where you encounter the bug
PS: also, since it works for everybody else, your judgment of "release-worthiness" doesn't seem to stand.
So far, nobody has complained that the plug-in doesn't work at all. We wouldn't have released a plug-in that doesn't work at all. The last post in this thread before you is from before the new plug-in was released. We didn't come across this bug because it doesn't exist, as the plug-in was completely rewritten for the 1.0.47 release.subspark wrote:What scares me is how NL could release this plugin update without coming accross the bugs themselves. I'm sorry ladies and gentlemen but release 1.0.77 of the 3dsMax plugin was simply not worthy of release. Shame on NL. I can't render a thing letalone browse through my materials.
The problem you're having is most likely due to your particular set-up and we would gladly help you get the plug-in running if you could provide more details. Since it works for everybody else, saying "it doesn't work" isn't enough for us to be able to track down the problem. The following information would be useful:
- system details: Windows version, Max version
- plug-in version; can you double check that you are indeed running 1.0.77 by going to Customize -> Preferences -> Maxwell? The version number should be displayed there.
- steps needed to reproduce the bug; did you try making a box in a new scene, setting Maxwell as the current renderer and hitting render? Does that break or do you need to do something more to trigger the problem?
- an example scene where you encounter the bug
PS: also, since it works for everybody else, your judgment of "release-worthiness" doesn't seem to stand.