Tweet
I've recently encountered a strange issue with V-Ray, Particleflow, and the "scene bounding box is too large..." warning. I understand the nature of the message: some (visible or hidden) objects in the scene are placed too far from the scene's origin and could cause raytracing issues. What makes it strange is the inconsistency at which this message occurs in my scene.
The scene uses Max Design 2011 64-bit and all objects are no further than 800 system units from the scene origin and everything is contained in an enclosed light-grey "studio" shell. Unhiding every object, layer, and category of object doesn't reveal anything outside of the studio object when "Zooming to Extents All". In production renders of previous iterations of the scene this warning would pop up on some frames but not others. What I first thought is maybe some particles are escaping the deletion conditions/events in my particle logic, but unhiding everything and ensuring all particles are visible yielded nothing outside the studio object.
It hasn't actually caused problems until today. I'm about to send the latest version off to a render farm and started running a low-res test render on my machine beforehand. On about the 108th frame it gave the message and essentially got stuck on the light-cache pass. I didn't let it finish but it was estimating over 2 hrs on that pass when I hit cancel. These tiny 480x270 test frames were otherwise taking 25 seconds apiece to fully render with IR/LC before this frame.
What's stranger still is I went back to the save file of the same scene with production render settings, nothing else is different, and tried rendering the same frame and it works fine along with a few other random frames in the suspect time segment. I'd have expected those settings to be independent of the bounding box issue or at least more likely to cause it at higher quality settings if anything. I haven't tested every frame but so far it seems fine; no warning. I am quite concerned that it will drag out the time and cost at the farm if it does happen.
Interestingly it would also come up if I increased the dynamic memory limit from 800MB in the settings:system rollout so I don't touch that anymore.
So it's happening in some frames but not others in a scene that apparently doesn't change maximum dimensions, and appears when render settings are lower or memory limits are higher against intuition. Is anyone here familiar with this warning and why it might be behaving the way it is for me?
Thanks kindly
The scene uses Max Design 2011 64-bit and all objects are no further than 800 system units from the scene origin and everything is contained in an enclosed light-grey "studio" shell. Unhiding every object, layer, and category of object doesn't reveal anything outside of the studio object when "Zooming to Extents All". In production renders of previous iterations of the scene this warning would pop up on some frames but not others. What I first thought is maybe some particles are escaping the deletion conditions/events in my particle logic, but unhiding everything and ensuring all particles are visible yielded nothing outside the studio object.
It hasn't actually caused problems until today. I'm about to send the latest version off to a render farm and started running a low-res test render on my machine beforehand. On about the 108th frame it gave the message and essentially got stuck on the light-cache pass. I didn't let it finish but it was estimating over 2 hrs on that pass when I hit cancel. These tiny 480x270 test frames were otherwise taking 25 seconds apiece to fully render with IR/LC before this frame.
What's stranger still is I went back to the save file of the same scene with production render settings, nothing else is different, and tried rendering the same frame and it works fine along with a few other random frames in the suspect time segment. I'd have expected those settings to be independent of the bounding box issue or at least more likely to cause it at higher quality settings if anything. I haven't tested every frame but so far it seems fine; no warning. I am quite concerned that it will drag out the time and cost at the farm if it does happen.
Interestingly it would also come up if I increased the dynamic memory limit from 800MB in the settings:system rollout so I don't touch that anymore.
So it's happening in some frames but not others in a scene that apparently doesn't change maximum dimensions, and appears when render settings are lower or memory limits are higher against intuition. Is anyone here familiar with this warning and why it might be behaving the way it is for me?
Thanks kindly
Comment