Chaos Corona Forum
Chaos Corona for 3ds Max => [Max] Bug Reporting => [Max] Resolved Bugs => Topic started by: CiroC on 2015-09-02, 11:12:30
-
Hi guys,
It is just me or since the daily build 27-08-2015 there has been a significantly drop in performance? I mean with the daily build from July 23 my scene would start rendering after 20 seconds of scene parsing and 30 seconds of Geometry and Rays/s total of 700K or even more.
Now since the daily build from 27-08-2015 to 01-09-2015 with the same scene the stats are:
Scene parsing 36 seconds
Geometry: 5 or 7 minutes
Rays/s total: 300
Not to mention that it calculates displacement for around 2 minutes when there is no displacement present at the scene.
Any idea why is this happening?
For now my solution is getting back to the 23-Jul daily build
-
Just tested the daily build from 17-08-2015 and it works fine, so I guess I will keep using this one.
-
Not to mention that it calculates displacement for around 2 minutes when there is no displacement present at the scene.
I don't think this is possible. You probably have some displacement in your scene. You can easily check that by disabling "displacement" checkbox in render setup > common > options. Displacement was heavily reworked in the recent versions, so this could be the cause of your problems.
-
Not to mention that it calculates displacement for around 2 minutes when there is no displacement present at the scene.
I don't think this is possible. You probably have some displacement in your scene. You can easily check that by disabling "displacement" checkbox in render setup > common > options. Displacement was heavily reworked in the recent versions, so this could be the cause of your problems.
I'm on 1.2.1 and I'm getting a short displacement calc phase in the scene prep for large scenes (only a few seconds but still) with absolutely no displacement in the scene and global displacement checkbox being off (briefly mentioned it in the Daily Builds thread weeks ago when I reported IR hangs back then).
-
I'm on 1.2.1 and I'm getting a short displacement calc phase in the scene prep for large scenes (only a few seconds but still) with absolutely no displacement in the scene and global displacement checkbox being off (briefly mentioned it in the Daily Builds thread weeks ago when I reported IR hangs back then).
I think I had this going on as well but wasn't sure. I certainly did not want to use any displacement as I was working on a memory hungry scene so I was surprised it always took a few seconds to calculate 0 displacement. But then again, I might have put it in somewhere so I can't say for 100% sure.
-
Not to mention that it calculates displacement for around 2 minutes when there is no displacement present at the scene.
I don't think this is possible. You probably have some displacement in your scene. You can easily check that by disabling "displacement" checkbox in render setup > common > options. Displacement was heavily reworked in the recent versions, so this could be the cause of your problems.
That is the problem. The Displacement option is turn off. That is what I found strange.
-
I do not remember such a problem. Can you provide us with a scene somehow? Is it very big?
-
I will see how big the file is. I have loads of trees since I work mostly with exterior scenes.
-
I´m working on a tight deadine ATM so can´t be of help by sending an example scene right away but I can concur with the latest dailies when I have displacement off in the Common tab, ticked off from the materials and made sure the displacement modifiers are also off I still get a "calculating displacement" when starting a render. It doesn´t take minutes, though, 30 seconds I´d estimate but I could check it more precisely tomorrow if it´s still needed.
-
Same situation here. I think I will manage to send the scene during the weekend.
-
I am testing the latest build and see if there is a change in the performance.
However, there is one thing that keeps bother me since A7. Usually I work with loads of vegetation and sometimes the scene parsing takes only 30 or less seconds and the render goes smoothly. If I stop that render and I re-render again there is a big chance that the scene parsing will take 3 minutes and then the render will take ages.
What is the http address to upload the scenes?
-
Corona private uploader: https://corona-renderer.com/upload/
-
Thanks romullus.
My render after 9 hours. It was my bad not using PT-PT and the actual time of render is almost 4hours, but still this is the result.
-
Hi Ondra,
I am uploading the scene. I uploaded the scene. The name is 00_OneToRuleAll.zip
I am using the Daily build Sep 6 2015.
I think meanwhile I will have to use the old trick: divide and conquer.
Many thanks
-
ok, this looks definitely like a bug
-
ok, this looks definitely like a bug
But I can't find any logical explanation. Let me know if there is anything else you need.
-
I am starting to get to the conclusion that Corona doesn't like Xref files.
If I Xref a scene the scene parsing and geometry gets really high (over 4 minutes). However, if I merge the scene the Geometry takes a little bit longer (1min or so), but the render starts really fast.
The problem I have is that this exterior scene is massive and have loads of trees and other vegetation.
The results from the experience I did:
Scene with no Xref
Scene Parsing - 3 seconds
Geometry - 7 seconds
Scene with a Xref
Scene Parsing - 4 seconds
Geometry - 3:57 minutes
Scene with the merged Xref
Scene Parsing: 3 seconds
Geometry - 1:43
-
I am working on another scene and I noticed the same behaviour.
It is a simple scene with 7350 scatter elements (grass) and maybe 10 trees. I start the render it takes 2 minutes to Scene Parsing and 3 minutes to Geometry. I stop the render and re-render again. The Scene Parsing drops to 25 seconds and the Geometry to 1 minute.
What bothers me is not even the Scene parsing and the Geometry time. The problem is that the Ray/s total and Ray/s actual are very low which makes the render taking ages.
Ondra, do you want this scene as well?
-
yes, it couldnt hurt to have more samples ;)
-
CiroC: it renders fine here... it may be simple memory exhaustion... how is your system memory during rendering?
BTW: we are implementing a Corona warning that will pop out once you start running out of memory.
-
also it seems camera is squished flat in the scene you uploaded... do you also see it?
-
We have similar issues and also disapearing parts of proxys, also if you hit render it says 22 hours and if you stop and hit again render it says 255 hour and for the proxy only it took 30 min for 6 passes at 2800 pixels wide, here an example. Did the test with and no forest, same results, testet on machines with 64 gigs of ram and 32, i7 and dual xeon and sinlge xeon, same results.
-
CiroC: it renders fine here... it may be simple memory exhaustion... how is your system memory during rendering?
BTW: we are implementing a Corona warning that will pop out once you start running out of memory.
also it seems camera is squished flat in the scene you uploaded... do you also see it?
Thanks Ondra for the feedback.
I am attaching a screenshot of the memory used during the render (it is using 14.2GB from 16GB). What is strange is that the CPU is only between 1% and 4%. Does it sound right?
Yes the camera is weird because we are trying to encompass a big area. But if I am not wrong is something possible with a tilt lens. :D
I am going to pack the other scene and upload it.
-
Hi Ondra.
I uploaded another file called Civils. This one doesn't take too long to render, but it is same thing I mentioned. The Scene Parsing and Geometry take something around 5 or 7 minutes, but if you stop and press render again, the Scene Parsing and Geometry goes back to 1 or 2 minutes.
Plus, I tried to render a simple a scene I can see the CPU going to 90%. When this "issue" happens the CPU doesn't go higher than 6%.
-
We have similar issues and also disapearing parts of proxys, also if you hit render it says 22 hours and if you stop and hit again render it says 255 hour and for the proxy only it took 30 min for 6 passes at 2800 pixels wide, here an example. Did the test with and no forest, same results, testet on machines with 64 gigs of ram and 32, i7 and dual xeon and sinlge xeon, same results.
I use loads of proxies. Could it be a problem with that? Usually, I use a combination of scatter and proxies.
I am going to try and convert the scatter objects into Max Geomtry and see if there is any change on speed.
-
CiroC: it renders fine here... it may be simple memory exhaustion... how is your system memory during rendering?
BTW: we are implementing a Corona warning that will pop out once you start running out of memory.
also it seems camera is squished flat in the scene you uploaded... do you also see it?
Thanks Ondra for the feedback.
I am attaching a screenshot of the memory used during the render (it is using 14.2GB from 16GB). What is strange is that the CPU is only between 1% and 4%. Does it sound right?
Yes the camera is weird because we are trying to encompass a big area. But if I am not wrong is something possible with a tilt lens. :D
I am going to pack the other scene and upload it.
ok, this definitely looks like memory exhaustion. With fewer objects the scene should render fine. I will looka t the other one though
-
Many thanks Ondra.
I will try your suggestion.
-
Hi Ondra,
One thing related with this issue, is that when I press the Stop or Cancel button Corona stills carry on calculating the Scene Parsing or the Geometry, which in this situation can take 10 minutes. Is that a bug?
-
that is probably also because you are out of memory and your system is swapping everything
-
Hi Ondra, we check on every machine and the cpu usage its arround 2 or 5 %, only the dual xeons are using 99 to 100%, it doesnt matter if its a tree or a bunch of them, its like its trying to render only with ram, the other thing its that the proxys created with this daily version are unreadable with 1.21 and those proxys are missing some elements ramdomly when render (daily not 1.21).
-
that is probably also because you are out of memory and your system is swapping everything
Many thanks Ondra.
It seems I am too "heavy" on the use of proxies and vegetation. It is a good idea what you mention: having a warning message that the PC is almost running out of memory.
-
already done in daily builds :D
-
here is some time test to campare and image result, both files on the same machine, hope this helps
-
already done in daily builds :D
You are the best Ondra. :D
I am sure you dream in code.
@KOGODIS
What about the Ray/s Total? Mine get really really low.
-
@ciroc, mine too, nule for most of the time that it's suppoded to be calculating, also strange is that we made the same test only for simple geometry for the building and same super slow results
-
My problem is the huge amount of polygons I need, which makes because machines also have limits. How many polygons do you have?
If nothing works my suggestion is using the shadow catcher and work with "render layers".
-
Thats a great suggestion, will try, don't remember how much polygons but the strange thing is that I didn't have problems before and the minimum of ram on the slaves is 24 gigs and the difference in time per frame on a video compared to the dual cribs with 64 gigs were around 20 minutes top, now they are like 29 hours per frame which it's absurd.
-
But if the render was working on the previous versions with the same amount of objects, polys etc.. and using the same ammount of ram, why is it geting that slower!??
-
But if the render was working on the previous versions with the same amount of objects, polys etc.. and using the same ammount of ram, why is it geting that slower!??
With me the problem happened with a couple of daily builds from August. After that the problem was solved (don't ask me why and how).
For now my issue is the high level of proxies and scattered objects that make my machine run out of memory.
-
I need to upload another scene, because I am rendering a simple plane and Corona is telling me that the system doesn't have enough RAM. :D
-
how does your task manager looks like when you see that message?
-
how does your task manager looks like when you see that message?
Here you have :D
I have to mention that the Scene Parsing and Geometry are only seconds.
-
For some reason it stopped now. Which is strange because now I have loads of geometry on the scene.
-
This simple geometry is taking 6 minutes to calculate Geometry. I even restarted the PC and re-render again and nothing changes. Is it because the image output is 5K?
-
I had this as well, insane parsing times and really low rays per sec. Struggled for 2 days trying to clean and fix my scene, reverted back to 1.2.1 just now and it works flawlessly again.. only thing that´s missing is the proxied objects made with the dailies, so maybe proxies are a part of the problem.
-
if you did not run out of memory, could you provide the scene?
-
if you did not run out of memory, could you provide the scene?
Unfortunately I can´t, with that scene at least :( To be more precise re:memory, Corona can usually parse/render scenes fast even when my 32gig is completely drained, but here the scene was using mere 25gigs and the problems occured.
I´ll try to recreate the problem tomorrow with a fresh scene if I get the time. But really the only thing that changed was the proxy objects which I had to redo for 1.2.1 since the ones done with daily versions apparently aren´t backwards compatible.
-
Everybody with "performance drop after update" please check the newest daily build. It should help render things faster, especially with different kinds of lights/lots of lights in scene:
https://coronarenderer.freshdesk.com/support/solutions/articles/5000570015
-
Everybody with "performance drop after update" please check the newest daily build. It should help render things faster, especially with different kinds of lights/lots of lights in scene:
https://coronarenderer.freshdesk.com/support/solutions/articles/5000570015
Aye Aye Captain.
I will give a try and see if there is any improvement.
-
I noticed a slight improvement. Although sometimes on a relatively simple scene the Scene Parsing and Geometry goes to near 4 minutes or more.
-
Two hours rendering. 3K image size with Displacement and this is the result.
The scene is not that heavy.
Daily build 5-10
-
Uhh... Any chance you could send the scene to support? https://coronarenderer.freshdesk.com/support/tickets/new
-
Uhh... Any chance you could send the scene to support? https://coronarenderer.freshdesk.com/support/tickets/new
Sure. I am going to upload to the dropbox and send it.
-
Maru, could we have a Corona solution to render tiles? For situations like this it is quite useful.
-
You can use region rendering or buckets - is that what you meant?
-
You can use region rendering or buckets - is that what you meant?
Exactly. Do you know any script can do that automatically? I had to decrease the image's resolution other wise will not render. For now I have to finish this, but hopefully I will upload the scene tomorrow.
-
this thread is now derailed past the point of being useful. Any new cases should be discussed separately - idealy with maru on our support
( https://coronarenderer.freshdesk.com/support/tickets/new )