Page 1 of 2
Update preview in material editor doesn't work
Posted: Mon Jul 28, 2008 5:01 pm
by jespi
Hello,
When trying to update maxwell's material preview inside material editor nothing happens. If i import a maxwell material i can see the preview but when i change any parameter preview does not change. Any thoughs?
Thanks,
jose espizua
Posted: Mon Jul 28, 2008 6:19 pm
by Bogdan Coroi
Make sure you have the 3dsmax renderer set to MaxwellRender.
Posted: Mon Jul 28, 2008 6:29 pm
by jespi
Do you mean in F10 common SetUp->asign renderer->maxwellrender? Yes , i have maxwell render as my default renderer.
Thanks
Posted: Mon Jul 28, 2008 6:33 pm
by Bogdan Coroi
Yes, I was talking about F10.
MXCL starts when trying to render a scene?
Posted: Mon Jul 28, 2008 6:45 pm
by jespi
yes,i can render. Also no problem with sky preview.
Posted: Tue Jul 29, 2008 3:11 am
by Bubbaloo
Could it be looking for a preview scene that doesn't exist? Or a preview scene that is not properly set up?
Posted: Tue Jul 29, 2008 12:38 pm
by Bogdan Coroi
If you press the MXED button from the Embedded MaxwellMaterial, does it open MXED?
Posted: Tue Jul 29, 2008 12:42 pm
by jespi
Thanks for the replys. I've decided to reinstall operative system because i was experimenting a few more issues. In a few hours I let you know if i can solve the problem.
Thanks a lot,
josé
Posted: Tue Jul 29, 2008 4:58 pm
by jespi
Well, still does not work after reinstall windows and 3dsmax...
To Bogdam: Yes, if i press mxm button MXED is opened and i can make the preview within MXED.
To Bubba: I have checked the route and changed the preview scene to Tom's stage 1 and same problem.
Posted: Tue Jul 29, 2008 5:47 pm
by Bogdan Coroi
The only possible problem I see here is that you don't have write permissions in the directory where the scene preview is.
When trying to make the preview, the plug-in reads the preview scene and creates a temporary file in the same directory. Here, if it can't create the file, when pressing the Preview button you'll only see the mouse cursor changing to HourGlass and back to Array, but no preview. Since the plug-in is embedded in 3dsmax, you have to make sure it has write access in the directory where the preview scene is. From your signature I see that you're running Vista. AFAIK, you can't write in \Program Files\ unless you have Administrator rights. Make sure you run 3dsmax as Administrator (Right click on the icon->Run as Administrator AFAIK).
Posted: Tue Jul 29, 2008 6:19 pm
by Fernando Tella
Maybe you have assigned Maxwell Render as render engine for production but not for material editor; usually the option is linked but you could have changed that.
Posted: Tue Jul 29, 2008 6:20 pm
by jespi

O.K Bogdan running 3ds max as an administrator made the job. I'm new to vista but this permission issue is annoying me, why if my account has administrator privilegies must i run the software as an administrator.
Thanks so much for your support.
Posted: Tue Jul 29, 2008 6:24 pm
by Fernando Tella

Another Vista security system victim... Is that supposed to make things easier to the user?
Posted: Tue Jul 29, 2008 6:41 pm
by Bogdan Coroi
I'm new to vista but this permission issue is annoying me, why if my account has administrator privilegies must i run the software as an administrator.
AFAIK, this is because you have UAC (User Account Control) enabled. In this way, an "admin" account will use 2 access tokens: the administrative token for administrative tasks and the standard user token for the other tasks. You can disable UAC if you know you won't need it.
Posted: Tue Jul 29, 2008 7:43 pm
by Bubbaloo
Bogdan Coroi wrote:I'm new to vista but this permission issue is annoying me, why if my account has administrator privilegies must i run the software as an administrator.
AFAIK, this is because you have UAC (User Account Control) enabled. In this way, an "admin" account will use 2 access tokens: the administrative token for administrative tasks and the standard user token for the other tasks. You can disable UAC if you know you won't need it.
Highly recommended to avoid other issues like this in the future. That's one of the first things I did after I installed Vista.