Page 1 of 1
activeShade crashes...
Posted: Mon Jan 09, 2012 10:38 pm
by naxos
I have an issue with ActiveShade with Maxwell...
Even with a small scene : plane+teapot, it gives me an error telling "only perspective views are supported", then black with no way to close activeShade, then 3dsmax crash...
Of course, i've tried both camera / persp view...
3dsmax2012 + maxwell 2.6.0 (plugin 2.6.14)
Re: activeShade crashes...
Posted: Mon Jan 09, 2012 11:02 pm
by Bogdan Coroi
Always start it having a perspective viewport or a perspective camera active in viewport.
Re: activeShade crashes...
Posted: Tue Jan 10, 2012 12:26 am
by naxos
Bogdan Coroi wrote:Always start it having a perspective viewport or a perspective camera active in viewport.
i did that...
i've used it with 2.5.x... with no problem... but now that i'm in 2.6.0, crash...
Re: activeShade crashes...
Posted: Tue Jan 10, 2012 9:55 am
by Mihnea Balta
Make sure the render viewport/camera isn't locked to an ortho view. Check the Viewport dropdown in the render settings and the lock icon next to it. If this isn't the problem, could you save a scene which crashes and send it to us?
Re: activeShade crashes...
Posted: Tue Jan 10, 2012 2:45 pm
by Bubbaloo
There is also an "orthographic" checkbox in the camera parameters. Make sure it is unchecked.
Re: activeShade crashes...
Posted: Tue Jan 10, 2012 3:52 pm
by naxos
no way...
Just start 3dsmax, put a plane + teapot, create camera (not ortho), choose MX as activeShade, then ask a view to be activeshade (the camera view)... same error, same crash then
Re: activeShade crashes...
Posted: Tue Jan 10, 2012 3:55 pm
by naxos
ok, i get it !!
Start activeShade from menu is ok, but ask for a viewport view to be activeshade crashes...
I'm so used to do so with VrayRT...
It seams a bug to me : we should be able to set a view as the ActiveShade...
Re: activeShade crashes...
Posted: Tue Jan 10, 2012 4:08 pm
by Fernando Tella
Confirmed here too. Activeshade in viewport = crash.
Re: activeShade crashes...
Posted: Tue Jan 10, 2012 4:12 pm
by Bogdan Coroi
Confirmed. Will be fixed for the next update.