Daniel Doerksen Posted February 20, 2011 Share Posted February 20, 2011 How would one go about figuring this error out. my render pretty much finishes, but sits there at the end and you cant close the rendering info window? Link to comment Share on other sites More sharing options...
ScottDeW Posted February 21, 2011 Share Posted February 21, 2011 I've been using V-Ray for a while now, and even that's a new error for me... Normally when I get an error such as that, I end up rebuilding my scene. I suggest opening a new max file, merging everything in, and then re-doing all your settings. If the problem continues, it might be something in the scene file itself. The problem then is figuring out what in your scene is causing this. Also, if you are rendering any displacement, motion blur, etc... You may want to disable these to make sure that these effects are not the issue. Good luck, I'd like to know how you solve this! -Scott Link to comment Share on other sites More sharing options...
Daniel Doerksen Posted February 21, 2011 Author Share Posted February 21, 2011 (edited) thanks for the tip ill try the merge idea. i increment save. so what im trying to figure out now is where it all went wrong and its seeming to be related to onyx/treestorm. soon as i started adding there trees to a larger extent. i have a few 60k shrubs in it renders fine. but when i added the 2-6million trees. it seems thats when disaster occurred. i have my memory set to 8000mb in settings. Its a bit frustrating since ive been really wanting to move over to realistic trees :s. this error might go hand in hand with my other post under the trees creation thread. Edited February 21, 2011 by Daniel Doerksen Link to comment Share on other sites More sharing options...
ScottDeW Posted February 21, 2011 Share Posted February 21, 2011 If it is a memory issue, the problem could not be that you are running out of memory. But rather that you may have a bad stick. Have you tried running tests on your memory? You may also want to keep an eye on your task manager when rendering. I've noticed things tend to get weird when you use more than 85% of your total memory when rendering. Link to comment Share on other sites More sharing options...
Daniel Doerksen Posted February 21, 2011 Author Share Posted February 21, 2011 the highest i saw my memory go i believe was 78%. but ill check again. ill run mem test and report back Link to comment Share on other sites More sharing options...
ScottDeW Posted February 21, 2011 Share Posted February 21, 2011 thanks for the tip ill try the merge idea. i increment save. so what im trying to figure out now is where it all went wrong and its seeming to be related to onyx/treestorm. soon as i started adding there trees to a larger extent. i have a few 60k shrubs in it renders fine. but when i added the 2-6million trees. it seems thats when disaster occurred. i have my memory set to 8000mb in settings. Its a bit frustrating since ive been really wanting to move over to realistic trees :s. this error might go hand in hand with my other post under the trees creation thread. Ah that very well might do it. First thing I've noticed about the Dynamic Memory Limit, that it's per-core of your machine. Or at least it use to be back when 1.5 went final. So you don't want to set it to 8000mb, because that will set aside 8GB of ram per core. You may notice your render times improve if you end up setting this to about 1GB. Secondly, your trees aren't being considered by the Dynamic Memory Limit if you leave them as actual geometry in the scene. If it's actual geometry, it's considered to be static geometry. Things like proxies, displacement, fur are considered to be Dynamic. So the limit only applies to these items. I generally keep my DML at 1GB-1.5GB, when I use onyx. Now I use Onyx Trees myself. Unless you need to animate them moving. You should combine them all into one object, and proxy it out. I then instance them and use a randomize script for scale and rotation to add a degree of variation. Also, you could get a script that can randomize the material IDs of the elements. This way you can add a variation of color to the leaves. Link to comment Share on other sites More sharing options...
Daniel Doerksen Posted February 21, 2011 Author Share Posted February 21, 2011 I would love to get confirmation on the memory limit per core in 2.0. Do you set a proxy for each tree or group a few trees into a proxy i didnt understand that from your message. i just assumed tree storm would have a effective way of dealing with multiple onyx trees. ok so i guess ultimately a proper work flow for me is to create a library of proxyied onyx trees. one question i have for you is when your creating a proxy for like a fir tree of 16million polys, converting to editable and appling your materials then exporting vrmesh max will be painstakingly slow and might crash. do you have any methods for dealing with that, or do u just push through with patience. Also checked the scene again and rendered it using 81% memory, max is using 7.9gigs this is all with my original settings, and had the error. like i mentioned ill run a memtest for good measure. but i think your right, with your method. i will try to proxy a few large trees tomorrow to test it out. Link to comment Share on other sites More sharing options...
ScottDeW Posted February 21, 2011 Share Posted February 21, 2011 I haven't had any experience with 2.0, so I'd like to know as well. My normal workflow for proxies is combining the elements into one object. Then making the proxy from the single object. However, if it ends up taking too long to do that, I just proxy out the individual elements and group them together. Either way works just fine. Just make sure when you start to duplicate them, they are instances of each other. It still is possible that you are hitting a bad sector of your ram, but I do have a feeling its more of an issue with needing to proxy out your trees. Good luck! Link to comment Share on other sites More sharing options...
tommyjj Posted February 23, 2011 Share Posted February 23, 2011 Try rendering the image in 2 chunks using Crop or Region I've used that in the past for huge scenes that wont normally render all at once Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now