I am having an issue, that I haven’t seen for awhile. I am running MAX 2014, and the latest V-Ray, and I can’t cancel my render. I remember this being a problem a long time ago, but I haven’t seen it for awhile. I have to ctrl-alt-del, and kill MAX.
Sometimes the light cache gets stuck, doesnt matter the max version. Scene you made yourself? What are the settings? how complex is it? any scatter objects? any proxies which have been copied instead of instanced? displacement?
Same here GTX 560
typical scene, nothing special, but I am using Multiscatter.
Nearly 15gb for a typical scene is crazy… Something is seriously wrong with that multiscatter.
you shouldn’t be nearing 15 on the kind of images you usually post up.
I have 32Gb on my main machine, and 24Gb on my 5 i7’s. I usually run around 15Gb, on most scenes. This scene, which I’ll post tomorrow, has displacement for the roof, siding, and some stone. I also have multiscatter grass and trees.
Sent from my Nexus 7 using Forum Runner
I asked if you had displacement and you said ‘nothing special’…
Well, displacement isn’t really special, at least for my projects. [quote=“cubiclegangster”]
I asked if you had displacement and you said ‘nothing special’…
[/quote]
I ´m not sure if this is directly connected to your problem not beeing able to cancel rendering.
But Multiscatter can be quite unpredictable. I ´m not sure if this is a vray or multiscatter problem.
Probabely it´s more a Vray issue or maybe just the way it is.
If you have a lot of objects intersecting, the lightcache will use a lot more memory compared to having the same amount of objects
not or only slightly intersecting.
I made an example
A simple teapot scattered 1mio times on a plane.
The first images show the memory consumption of 1mio teapots.
The second image shows the memory consumption again of 1 mio teapots.
In this image I transformed some vertex of the teapot to extend the bounding box.
Means a lot more intersection is going on. Notice the difference in memory consumption
while the amount of geometry and gi settings are the same.
This is why you sometimes can render multiscatter with for example 5mio instances
without a problem while another time a scene with just 1mio instances completely
freaks out. Always try to keep the intersection as low as possible.
Could you please try to activate “Low Thread Priority” from Settings Tab > Miscellaneous options and run the same test again.
If it is possible please send us this scene in order to investigate what is root of this issue.
I will sure try, thanks![quote=“svetlozar_draganov, username:svetlozar_draganov”]
Could you please try to activate “Low Thread Priority” from Settings Tab > Miscellaneous options and run the same test again.
If it is possible please send us this scene in order to investigate what is root of this issue.
[/quote]
Did you fix this issue Bobby, I’m just starting to use 3dsmax 2014 with Vray 3 and I cancel a render then have to wait ages!
it stopped happening for me. I don’t thing I did anything - I am on Vray 2.4.
I am having a similar’ish problem with Vray 3002 & Max 2014. The final bucket in the render “hangs” for ages. Sometimes it finishes, but other times it just hangs there and 3dsMax becomes unresponsive (have to kill Max to stop it). No displacement being used. scene memory usage during rendering is about 5Gb. Also, sometimes even when the rendering is finished (Rendering tab says “Rendering image…:done” ) & all the buckets have gone, it still hangs / crashes 3dsMax
is it always on a specific element? Like, lets say, something bright? I thought 3.X had a toggle which avoids that.
I have not used it enough yet to really know what the problem is (“if” it is a problem). I was experimenting with a Vray 2.4 scene but switching the Embree option turned “on” in Vray 3. Turning it OFF (the default) seems to maybe fix the problem i was having. Other problems i have had include crashing when using Xrefs in the scene.
Correction - turning off Embree does not solve the problem ! I also have max ray & probalistic lights turned off.
That’s interesting and good to know - thanks man.
I find it happens with me when i also have Photoshop open. Something about Photoshop taking priority over shortcuts
For me it seems to be directly related to the render size, so an empty scene at 640 odd is fine after cancel - instant response, but up at 6k square, I can wait over 4-6 seconds and more to cancel. If i’m only doing very quick test renders for camera alignment, wanting to render 8-10 renders in a couple minutes, the 6 seconds I wait between all adds up and is literally taking me twice the time! Does anyone else confirm this issue in Vray 3 and 3ds max 2014. I never had this in 2012.
I have also seen that an empty scene loaded with 10 render elements also then takes a lot longer to render blank and then cancel. the non element render takes 4-6 to cancel, with loads of elements its over 12 seconds - again its an empty scene.
I guess 3ds max 2015 will not fix this if its an Autodesk issue of course. It would be good to know others have the issue though?
EDIT- having now tested on an identical spec machine to mine at work, the issue is my machine specific!!! DOH I cant figure out what it could be, same max version, vray version, plugins. The hunt continues!
ANOTHER EDIT - logging in as a different user also fixes it, so its just my login!! Amazingly frustrating.
i realized kind of same. canceling an rendering is always in par with a long wait (few seconds) before max is responsive again.
I’m not sure if thats related with the cache or renderelements, but i’ve got similar effect on both max2012/vray 2.4 and even worse max2014/vray3.0 … not just one machine.