1
[Max] Daily Builds / Re: Daily builds version 2
« on: 2018-02-02, 14:48:04 »
Great job as always!!
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
If the roof is a simple geometry (like a single block) using just one material, then another solution would be using the rayswtich material to store the original material in reflect, refract, and gi slots, and leaving the direct visibility slot empty.
Why not to use camera clipping? That way the roof will be invisible only to the camera, but will still contribute to the scene in any other way.i cant use camera clipping because in my scene i have other building higher than my project...
Why not to use camera clipping? That way the roof will be invisible only to the camera, but will still contribute to the scene in any other way.
Hi, i've a question...is possible when using vr image add some stuff to add the hotspot to link the image to create a panotour?Hi, there is no such feature in CIE right now.
Thanks
Hi,
I checked your scene, and there is (unfortunately) nothing wrong there at the moment. Corona is currently a "bit" memory hungry (100B per pixel for denoising, 72B per pixel for random sampling). We have some optimizations planned, do not worry ;). The memory usage I got was consistent with this
That's weird. Can you share the scene for us for internal testing? You can use the private uploader from my signature for that.
Frame buffer / render elements eat a lot of memory on high resolutions. Unfortunately 3ds Max allocates itself some more memory for the elements internally, which should be something like 1 GB in your case. That makes 8 GB in total consumed just by frame buffer.
Since you have only 40k unique polygons, I doubt that the geometry is a significant memory consumer. My guess would be some high resolution textures.
Corona allocates some more memory during the denoising phase since it needs some temporary working buffers to copy the render elements to for additional processing (and storing the denoised result). This is something we'd like to fix, but there was unfortunately no time to implement it yet.