By Bogdan Coroi
#273675
I assume max2k8 is wrong :). Someone else mentioned this before, but I can't reproduce it. Make sure you're rendering using SHIFT+Q and you're not using Last Frame Rendered (F9).
By Bogdan Coroi
#273684
You can reproduce it every time and on different scenes? (Even after restarting max2k8?) If so, could you share a scene so I can dig it further?
By sandykoufax
#273689
Thanks Bogdan,

maybe it seems that a scene problem.

It occurs only that scene currently.

I don't know the reason but anyway ok, that scene is just test scene. :wink:

If this problem occurs again at other scene, I'll tell you again. :)
By JCAddy
#273744
I ran into this problem while testing the plugin and haven't had it since. I think it's really a scene dependent thing, not sure why or what causes it but I think that's it.
User avatar
By Bubbaloo
#273970
This used to happen to me with region and blow-up in Max 2008. Since I went to Max 2009, it hasn't done that.
A work around I found in 2008 is:
After rendering region or blowup, and you change it back to view, switch viewports several times (full screen) then switch back to camera or perspective and try rendering the full view. It worked for me.
By ishook
#275332
Happens to me a lot w/ max2k8. If you change your render resolution it'll cancel the forced region if you're going from region to full frame.

Haha, thanks.

Hello, I'm still waiting for a solution to the pro[…]

Well.....they must have been proven wrong, as it's[…]

Hello dear customers, We have just released a new[…]