FlytE Posted July 25, 2006 Share Posted July 25, 2006 Ive recently been encountering a problem that is driving me mad. I have been having trouble rendering out anything greater than 2000 pixels wide. If I attempt to try this, an 'application error' occurs and viz is shut down. I have gone through everything i know to stop this error and the only thing that did was reducing the render output to 2000 or less.... Does anyone know anything about this? Link to comment Share on other sites More sharing options...
Parker1 Posted July 25, 2006 Share Posted July 25, 2006 Strange...I ran one out at 4500x3000 last night with no issues. Are you sending the image through BACKBURNER? We have found that it helps alot. Link to comment Share on other sites More sharing options...
ipdesigner Posted July 25, 2006 Share Posted July 25, 2006 *it happens to me also, but only 3000++ size and an error occur, i reduced to 2000+ and it did fine, dunno why this happening by the way. Link to comment Share on other sites More sharing options...
FlytE Posted July 25, 2006 Author Share Posted July 25, 2006 No im not using backburner... im using the vray frame buffer though.... Link to comment Share on other sites More sharing options...
Ricardo Eloy Posted July 25, 2006 Share Posted July 25, 2006 Try this: 1- enable VRay's VFB and disable Max's. It will save a lot of memory already. 2- try rendering the pic directly to a file (VRay Image) and then re-save it as JPG, Tiff, whatever 3- as Brian suggested, use backburner. It has an option to divide the pic in slices that reduces the amount of memory necessary to render it. This one is particularly useful. Link to comment Share on other sites More sharing options...
FlytE Posted July 25, 2006 Author Share Posted July 25, 2006 Ill give it a try although i have to be honest ive never used backburner. Any pointers on where to start ? lol Link to comment Share on other sites More sharing options...
jow Posted July 25, 2006 Share Posted July 25, 2006 Also you cold try using the 3gb switch...its got me out of alot of problems like this. Link to comment Share on other sites More sharing options...
FlytE Posted July 25, 2006 Author Share Posted July 25, 2006 Im sorry maybe my head isnt really working today but i dont know what the '3GB switch' is.... Link to comment Share on other sites More sharing options...
Jason Matthews Posted July 25, 2006 Share Posted July 25, 2006 I had this problem a little while ago. The issue is that you do not have enough ram to handle the scene. I handled it like this: 1. Render the scene in two different regions 2. In the region you are not rendering turn off as much geometry as possible 3. Repeat steps 2 and 3. Link to comment Share on other sites More sharing options...
jow Posted July 25, 2006 Share Posted July 25, 2006 It enables an app to use up to 3gb of ram (probably closer to 2.6gb) instead of 1.6gb per app. Open C drive, boot.ini and add to the file - multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional 3GB" /3GB so it reads- [boot loader] timeout=30 default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS [operating systems] multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /fastdetect multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional 3GB" /3GB this will give you 2 options when you start windows, choose XP 3GB, and your done. you'll then be able to render much larger scenes etc. Link to comment Share on other sites More sharing options...
ktm07 Posted July 25, 2006 Share Posted July 25, 2006 Backburner is surprisingly easy to use and Brian and I could not survive without it. Do make sure you turn off distributed rendering and frame stamp before running strips in backburner. Tom Link to comment Share on other sites More sharing options...
jow Posted July 25, 2006 Share Posted July 25, 2006 Some links about it http://www.microsoft.com/whdc/system/platform/server/PAE/PAEmem.mspx http://www.microsoft.com/technet/prodtechnol/exchange/guides/E2k3Perf_ScalGuide/e834e9c7-708c-43bf-b877-e14ae443ecbf.mspx?mfr=true http://support.microsoft.com/kb/328882/ Link to comment Share on other sites More sharing options...
BrianKitts Posted July 25, 2006 Share Posted July 25, 2006 yeah I'm gonna second Rick's comments for rendering out to a vray image. I had to do it on some high memory scenes and it works great. But make sure you have HD space where you are saving it. I've had a couple image files push a gig or two. the great thing is it saves out the data as it goes, so each time a bucket finishes the files updated. Which is great cause if your render crashes all the data is still there intact. And if it doesn't finish all the way, just go into your system tab reverse the rendering sequence and start it again. Link to comment Share on other sites More sharing options...
FlytE Posted July 25, 2006 Author Share Posted July 25, 2006 That sounds ok, BUT.... in my case, when I render (or try to) it crashes right at the start - 'updating Vertices' then it has its error and has to close, so no chance to save any info.... This is alot of info and a very quick response, thank you all! Link to comment Share on other sites More sharing options...
jow Posted July 25, 2006 Share Posted July 25, 2006 No worries, PM me if you need help with the 3GB thingy... Link to comment Share on other sites More sharing options...
BrianKitts Posted July 25, 2006 Share Posted July 25, 2006 That sounds ok, BUT.... in my case, when I render (or try to) it crashes right at the start - 'updating Vertices' then it has its error and has to close, so no chance to save any info.... This is alot of info and a very quick response, thank you all! no that sounds about right, thats when mine would crash as well. It will allocate all the memory needed for its frame buffers. then as it starts resolving the geometry and loading it into memory it would max out and crash. Pop open your task manager and switch over to memory usage and see if your zeroing out your memory. Make sure you turn off the max rendered frame window. set the max buffer size to like 20px by 20px so it doesn't use any memory. In your Vray frame buffer, turn off get resolution from max and set your actual render size. And don't render to memory frame buffer. You'll get the rendering progress dialog but no on screen preview (thus no wasting of memory). You're flying blind but if you're cranking up for a final you've probably done enough low res tests so what does it matter anyway... If that still doesn't get your through it, then I'm outta suggestions... hope it works for ya. Link to comment Share on other sites More sharing options...
FlytE Posted July 27, 2006 Author Share Posted July 27, 2006 Well, im still looking into backburner, but i did manage to try the 3GB switch. It now allows me to render out that same file at 3000 pixels wide instead of 2000....so that is alot better thanks! saying that though, anything beyond 3000 is still a crash though... good thing im getting a new machine soon. I wonder if this is something to do with autocad models being brought into viz... has anyone else who has experienced this problem by any chance brought their model in from autocad?.... Link to comment Share on other sites More sharing options...
FlytE Posted July 28, 2006 Author Share Posted July 28, 2006 Some new things i discovered that i felt were worth sharing. After using the 3gb switch, i found viz ran unbearably slow on even the simplest of scenes. Once i rebooted to normal xp.... it worked fine again.... so that really is a last resort. I did however try the rendering to raw image and not using memory frame buffer.... I havent seen the final result as its still rendering but so far is workign a treat. I am using 1.46.15 and im aware there are frame buffer instabilities with this verison, but it really does seem that by default it cant 'render to memory frame buffer' at anything over 2000 pixels wide, sometimes smaller, or it will crash - this is with 2.4 GH dual processors with 1.5 gb of ram. I still havent tried backburner (when i get even a minute to myself i will try lol) but in the meantime vray raw image seems the way to go. Thanks again all! Link to comment Share on other sites More sharing options...
jow Posted July 28, 2006 Share Posted July 28, 2006 Glad to here its working now:) Another thing you might find is problems with your graphics card ( i had probs with the Nvidia release 80-81 driver , seems ok with release 90 thou). Also make sure you've got enough Page file allocated (vitural ram), you gonna need 2.5 -3gb. Set both the initial and maximum sizeto the same amount to avoid fragmenting. Link to comment Share on other sites More sharing options...
FlytE Posted July 28, 2006 Author Share Posted July 28, 2006 I have a funny feeling this is going to be an obvious answer, but you do i load the vray raw image file so i can resave it as jpg or whatever.... ? Link to comment Share on other sites More sharing options...
BrianKitts Posted July 28, 2006 Share Posted July 28, 2006 taking a stab at what i think you meant to type..... yeah to get your image file into an usable extension... from the file menu in max near the bottom click on "load image file" it will put it into the max buffer. From there you can save it out to whatever format you want. Obviously if you're working in a gamma corrected workspace... save it out as EXR TIFF or something that can hold the floating point data, the gamma correction won't be applied in the buffer to save it out as a jpeg. Link to comment Share on other sites More sharing options...
FlytE Posted July 28, 2006 Author Share Posted July 28, 2006 Thanks for that. I found a workaround before i read this in the form of loading it into the ram player.... do you know if I can duplicate it from the max from buffer into the vray one (to use the colour correction...) ? 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