I needed to render an old project and used vray 1.45.70 for this render.
It occured that the renderslave used a huge ammount of memory on to the point of 2,4 Gb, wich caused max to crash. I think this has to do with the new way instances are handled. So i turned down the memory usage for dynamic geometry and the scene took forever to render.
I just switched back to vray 1.09.03g and the scene renders just fine, without excessive memory usage and fast as hell.
What could be causing this, i never had problems with this scene and it is nothing out of the ordinary for us. If this proves to be a real problem we can’t switch to the new build because we have to render these kind of scenes all the time.
I also noticed that the amount of subdivisions for quasi monte carlo rendering has gone from 1 to 50 :shock: . Is this correct and if yes, why.
I hope Vlado or someone can clear this up, cause i am allready in love with the lightmap and going back is not a real option.
we opserved the same thing here. We did a view tests with big amount of polygons and got crashes all time.
It really seams like 1.45 can’t handle more polygons then 1.09. Seams to be bug?
No different if using the Dynamic engine. Maybe it’s not working yet.
So !
The best thing you have to do is to import your old scenes in a new one in Max.
That allows you to get a scene with the new version parameters at
their default Value.
Yes, you have to set up the renderer as it was before…Not so annoying!
just look your settings in another max window.
Next, if necessary, transform all your material in a Vray mat.
To get faster opacity, for instance.
Im trying it right now and it is definitly not working .
I am waiting for 10 minutes for the first pass to complete and it is not past the first square yet (640x480 pixels), while the rendering on the old vray at 3500 x 2526 pixels is finished in 1:30 hour.
Im trying it right now and it is definitly not working .
I am waiting for 10 minutes for the first pass to complete and it is not past the first square yet (640x480 pixels), while the rendering on the old vray at 3500 x 2526 pixels is finished in 1:30 hour.
This is just silly, Vlado please help.
ErikIt would be helpful if you can provide me with some more information about your scene to vlado@chaossw.com; In addition, instances are indeed handled in a different way, so if you have many instances of high-poly objects, this could be causing a problem. In any case, I need to know more before I can say anything.
The problem is because of the 2d displacement - in 1.45.70 each
displaced instance makes its own copy of the displacement map, which is
what takes so much memory (compared to 1.09.03n where the maps were
connected to the modifiers and not to the objects). This will be fixed
for the next builds.
Any pointers on how to use this feature. Should my workflow be the same as with Photonmaps i.e. first render Lightmaps for 1st and 2nd bounces, save the file and then switch 1st bounce to irradiance mapping. Also do I still turn off reflections and refraction when calculating the Lightmaps?
Lastly do I still make use of Skylights at openings to get “sun light” into the building?
WWX to wich post are you refering, your question doesn’t make a whole lotta sence in this thread. I think your refering to the render i made with the lightmap of that testfile thread.
Erick I posted a similar ? under the Tut topic, with no replies, when I read your post here saying that you love Lightmaps, I took it that you have established a workflow using them.
In our test scene we used about 15000 copys of the standart teapots. While we had no problems in the viewport, both vray and the scanliner crashes on rendertimes do to a lack of RAM memory (no matter how much virtual memory we gave).
It’s just a sample for the problem. So if you use a lot of meshsmooth objects you can encounter crashes when the polycount get up to 3 millions. This happens not to instances, but you can’t always work with instances.
At the moment I can’t see any improvements in this on Vray 1.45. Anyhow I thougt that this is one of it’s main features. Don’t know if it is Vray related or more a bug in Max.
It would be very interesting to have this bug fixed, or this feature improved. If you go for 2k rendering you simple need to screw up itteration on meshsmooth, displacement etc.
Don’t want to unfair, but our test with finalrender where different, it’s possible!
I mailed my scene to Vlado and this was his answer,
“The problem is because of the 2d displacement - in 1.45.70 each
displaced instance makes its own copy of the displacement map, which is
what takes so much memory (compared to 1.09.03n where the maps were
connected to the modifiers and not to the objects). This will be fixed
for the next builds.”
I am also having this serious trouble with some scenes regarding memory usage, and render times using 1.45 compared to 1.09.03
using 1.09.03r 3dsmax.exe process uses up to 400 MB of RAM and takes 00:57 seconds to render 640x640 pixels frame.
using 1.45.70 3dsmax.exe process uses up to 1,44 GB! of RAM, and scene takes 05:52 seconds to render same frame.
I am talking about pure rendering, no Imap calcualtions involved. either Imap precalculated or not using Imap at all, RAM usage ramps up when updatins instances and the scene preparation stage.
Yes, the scene has some surfaces using 2D displacements.
when we are not talking about render tests, but high res stills, my system crash and can’t render.
Yes, I can go back to 1.09.03, but the quality of the Imap is so much much cleaner in 1.45.70 that is a big pain to go back :-)))
oh, it’s so cruel to give us the sweet to taste and we not being able to swallow it all :op
did you look at the Quasi Monte carlo slot ?
HAve you changed the parameters ?
If you see 50, here is the reason… of your huge time.
Read above …
Gael
Hi Gael,
As I said, No Imap calcualtions (either precalculated or NO GI at all)
so the QMC is not the issue here.
Disabling displacement and it solves one of the issues, Memory usage. But render times keep being some 5 times those of 1.09.03r same scene frame, etc.
.
.