Jump to content

tonyo_d

Members
  • Posts

    7
  • Joined

Personal Information

  • Country
    Canada

tonyo_d's Achievements

Newbie

Newbie (1/14)

10

Reputation

  1. Your scene needs about 6000 MB to render, and you are only allowing it to use 4000 MB. The dynamic memory is set in settings tab -> system section. Change Dynamic memory limit from 4000 to 6500 and see if it works. Even though the grass is not seen in your water camera, it is still in the scene and needs to be computed for GI, reflections/refractions, etc. Also, in forest pack pro, did you use the camera clipping option? If not, try using it. It will free some memory. One last thing I don't think the summary info counts the forest pack proxies, as it is a 3rd party plugin. Not sure though. Pretty sure it is a memory issue
  2. Hi Terri. I was talking about merging xrefs, not proxies. Personally, as your problem is happening randomly, I think your main issue could be the lack of dynamic memory. Your scene contains a whole lot of polys.
  3. A4 @ 300 dpi = 3508 X 2480. That's pretty high resolution! 2 hours for such a big render is not that long, even though your scene is pretty simple. The water must be quite long to render. Brute force, while very accurate is also very slow. Try using Light cache instead. That will speed your render a lot.
  4. Yeah, Hopefully it will not be 2008-2020... Oh and by the way, sorry for the bad quality of my english. My first language is french. At least I try!
  5. First merge xrefs in your scene if you have any. I've seen irradiance maps go nuts because of xrefs. Then make sure that the "check for missing files" option is checked. Then i'd try to send the job to backburner manager, with the option "include maps" on. That will pack every file including proxies in the same zip (backburner job). Then run the backburner server on your computer. All files will be seen as local by max. If there are missing maps, backburner server will tell you. ALSO If you made your grass with forest pack pro, make sure that you update to the latest version. Older versions have problems with some non-english or special characters in proxy names. One last thing: 4000MB dynamic memory seems a little low for that much polys. If your system can afford it, I would upgrade to at least 6000. That should do the trick.
  6. Thanks for your replies. Problem solved! I have no idea what caused it though :/ After few days messing with the settings, I got fed, so I imported my render setting preset from an old scene. It didn't work. Then I opened the old scene, deleted everything and merged my new scene elements in it. Boom! No more crunchy edges. So basically - It was not a render settings problem (because it did not work when I merged the render settings from the old scene) - It was not a lighting problem (because I kept all my lights when I merged in the old scene) - It was not a material problem (because I kept all my materials when I merged in the old scene) Baffled!
  7. Hi everyone, I am having a weird effect in the corners of a room. I have never seen it before, so I am quite confused... I use 3DS Max 2013 with VRay 2.40.03. What is weird is that it does not happen everywhere in the scene. Only in some corners. Oh and no, there are no gaps between edges (planes actually cross each other) Anybody ever saw that before? Thanks
×
×
  • Create New...