Chaos Corona Forum
Chaos Corona for 3ds Max => [Max] Bug Reporting => [Max] Resolved Bugs => Topic started by: quizzy on 2016-03-17, 15:23:44
-
I have multiple scenes where the render hangs on Parsing the scene. I can wait forever and it wont stop parsing. I need to end 3dsmax, and open the autosave every time. This is pretty anoying. Is there anyone else having this? And is this on the top of the bug resolve list?
I am a fond user of corona but this is a big GRRRRRRRPPUMPPPFFF and ARRGGGHHHGGHGHH for me...
btw, its totally random
-
Could be a RAM issue.
-
Which version of Corona? Can you report it over helpdesk? https://coronarenderer.freshdesk.com/support/tickets/new
-
@maru: done / corona 1.3 in 3dsmax 2015
Ram is 32Gb, and only uses (when it does render) around 5Gb
-
do you have motionblur turned on and object that has motionblur is selected when put to rendering?
I have this happen with "XMesh" object selected and if motionblur is turned on in render setup dialogue. It hangs on parsing scene.
-
Do you use Corona bitmaps?
-
Hi,
any progress? Does it happen in latest RC? can you share a scene where it happens (http://corona-renderer.com/upload)? How much random it is?
-
i have the same issue - its totally random - it does not take forever but it can take a good minute for what would usually take 3 seconds.
-
Which version of Corona?
-
do you have motionblur turned on and object that has motionblur is selected when put to rendering?
I have this happen with "XMesh" object selected and if motionblur is turned on in render setup dialogue. It hangs on parsing scene.
I might have idea about it since i am active Thinking particle user.
There is a pausability that corona hangs if there is no prerecorded particle cache. Or if simulations of any kind are going on while the rendering proces is beeing started (for example it needs to be something recalculated, for example aditional teselation, before render of new frame).
This is very anoying limitation but still this is LIMITATION related to any particle cache not only TP.
To avoid this:
1 - always prerecord cache before starting render.
2 - chek and double chek for maching of vieport and render sttings.
PS - i could have reacted earlier on this thread, it is because i read only part of the topic.
PSS - also insane amount of motion blurred geometry might cause insane acc structure building times (for example scattered trees with wind, or alot of particles shitload millions for them) then you should use 1 velocity chanel 2 pixel motion blur in addobe after effects.
-
I've had this a lot recently using very heavy forest pack carpets.
It would be great to be able to escape out of parsing and/or see parsing progress.
Cheers
Jan
-
CAn you (anyone with this problem) capture a minidump when it happens? How is the CPU and RAM usage when it happens?
-
Hi Ondra
The scene doesn't crash it will just freeze up and continue parsing for 2-3 hours. It renders fine after but this quite a leap of faith for a render.
Ram at about 60%
CPU at 25%
Intel(R) Xeon(R) CPU E5-2690 v3 @ 2.60GHz (×2) 64 GB RAM
The dump file is 5 GB compressed. We can drop box it to you perhaps?
Cheers
Jan
-
Zipping the file should help tremendously. But our dropbox uploader can handle up to 10GB files: https://www.dropbox.com/request/TxIykqXBaJnRvWIwOypP
-
Zipping the file should help tremendously. But our dropbox uploader can handle up to 10GB files: https://www.dropbox.com/request/TxIykqXBaJnRvWIwOypP
We just shared it with you via dropbox. Hopefully you got an email with a link. 5GB.
Cheers,
-
got it, thanks. Note to self: _forum 11326
-
Hi,
I analyzed the memory dump and it is stuck inside forest pack plugin, in its IForestRenderBegin method. We cannot speed that up or cancel it from Corona. I can forward the memory dump to guys at Itoo if you allow me, perhaps they will look at it and try to optimize it. I am moving this to resolved in the meantime
-
Hi Ondra,
Please do.
Many thanks
Jan
-
great, would you also share the problematic scene with Itoo?
-
Forwarded the report to Itoo
-
According to Itoo developers, it's stuck in the Collisions checking. Depending of density and number of items, Collisions may take a long time to be computed. They suggest to decrease density settings, or when possible disable Collisions completely. Sometimes same effect can be achieved using other methods. You should post in their forum for more details.
-
According to Itoo developers, it's stuck in the Collisions checking. Depending of density and number of items, Collisions may take a long time to be computed. They suggest to decrease density settings, or when possible disable Collisions completely. Sometimes same effect can be achieved using other methods. You should post in their forum for more details.
Very interesting, thanks Ondra. We'll test later today and see if that makes a difference.
-
I don't know whether this is connected, but I've got a complicated Forest Pack scene and when I have been testing changes with Forest Pack I've been getting parsing freezes.
I've found that if I have selected the Forest Pack when I press render, it freezes while parsing. If I don't have anything selected it parses OK.
-
Do you use/scatter Laubwerk trees?
Good Luck
-
Turning off/tweaking the collisions solved the problem for us Adam
-
No, just Forest Pack and I'm pretty sure there is no collision checking in this scene, but they are nested (ie some FP objects are masking other Forest Pack objects).
It's actually rendering fine as long as I don't have a Forest Pack selected/open when I start the render.
-
Everyone experiencing some problems/crashes/long parsing with Forest plugin - can you try disabling "limit to visiblity" option and see if it helps?