Chaos Corona Forum
Chaos Corona for 3ds Max => [Max] Bug Reporting => [Max] Resolved Bugs => Topic started by: tmsfischer on 2015-11-11, 10:22:03
-
Hi guys,
I have a biiig problem. I'm working on an animation project, and just rendered 200 frames out of it with UHD cache, animtaion (flicker free ) preset ( 'cause i have trees, naps, lights moving in the scene ) and i have got totally randomly thirteen frames ( of the 200 ) which came out black, or almost black - see attached...
I have tried to render one frame with HD cache, and got no problem(but cannot re-render all with HD cache, cause flickering...)
Have you ever seen this? What can be the problem?
Thanks in advance!
-
Looks like bug to me. Let's move it to bug reporting board and see what happens.
-
Did you pre-render the HDCache on its own and set to Load From File, or are you rendering and appending the UHD file for each frame along with the main render pass?
-
No, i didn't pre-render HDCache, and didn't set to load from file, it's on "calculate from scratch", UHD, animation preset , so for each frame...
any idea?
-
I had exactly the same problem lately. But i cant remember how i solved it.
Only thing i remember that this was apearing when i was using DR and only specific cameras were afected. I can look for this scene and try to to remember how i solved it.
Actualy it kind a looks like Displacement+messed up boolean mesh. So most probably that is bad geomety what is causing it.
-
We have a similar report in support right now, but it happens when rendering with Corona+Deadline. And it probably is not uhd-cache related.
-are you using Complex Fresnel plugin by Siger or any Siger materials?
-are you using displacement?
-can you try rendering with no UHD Cache (pt+pt) - this scene should not profit much from using UHD so it should be fine to render it with pt only, and we would check if it's UHD-related
-
And yes, i was using DR (on rebusfarm...) but no boolean mesh in the scene, and not even displacement ( only on soil in the small vases.... )
but bad geometry, what can it be? i think everything is proper, box, cylinder or line based models most of them, some trees and plants from evermotion but nothing too complicated...
-
Hi Maru,
-no complex fresnel plugin, no siger materials.
-displacement just on small planes (there are 3 of them... )
I already tried with PT + HD cache, but not yet PT+PT...
BUT
the problem is that its completely random, i mean,
-i rendered on rebus farm all 200 frames first( yesterday )
-came home, checked the results and frame n°14 , 19, 20, 22 etc...fourteen frames bugged
-so than i re-render only the bugged frames on my computer yesterday night
-this morning, checked the results, still 2 frames bugged ( but the others are OKAY! )
- so than rerendered these 2 again with HD cache, and everithing is okay ( except for every ex-bugged frame are flickering now....)
-
Important question which it looks like hasn't been asked yet: which version of Corona are you using?
-displacement just on small planes (there are 3 of them... )
The question was if there is displacement at all. So there is. Can you check what happens if you disable displacement completely? ("displacement" checkbox in common render settings)
I already tried with PT + HD cache, but not yet PT+PT...
Please try with pt+pt.
-
My corona version is 1.2.1
I disable displacement and try PT+ PT now ( is pt+pt flicker-free in active animation?...)
I let you know,
Thank you !
-
My corona version is 1.2.1
Why not 1.3?
( is pt+pt flicker-free in active animation?...)
Could be noisy, but not flicking.
-
Why not 1.3? Because i just ask rebusfarm last week if they support 1.3 and they said just from this week so as i was afraid i didn't want to take risk .. :)
pt+pt is rendering now with no displacement, but for the moment seems everything ok....
i send the view in a few minutes...
-
My best guess is that is is a NaN problem caused by faulty texture or incorrect mesh + displacement. Such problems should be fixed in 1.3. If you provide us the scene, I can check if I can reproduce the problem in 1.3, but I would not count on it
-
Here is the image attached, with pt+pt with no diplace...
-
And what if i have my scene (so made in 1.2.1) , and i upgrade to 1.3 by myself. By upgrading, does it change anything in the render result?
Should i change something ( like when i upgraded to 1.2.1 and opened an old file, i had problems with the old version sun, so i had to change it ... ) ?
'cause if not, i am up to upgrade of course (even rebusfarm, i checked they support now! ) :)
Thanks!
-
And what if i have my scene (so made in 1.2.1) , and i upgrade to 1.3 by myself. By upgrading, does it change anything in the render result?
Should i change something ( like when i upgraded to 1.2.1 and opened an old file, i had problems with the old version sun, so i had to change it ... ) ?
'cause if not, i am up to upgrade of course (even rebusfarm, i checked they support now! ) :)
Thanks!
It should look the same or very similar, BUT you won't easily be able to re-open the saved 1.3 max files in 1.2.1 if you decide to roll back for some reason, due to several material values changing. So, basically, once you upgrade and save the max files in 1.3 you will need to stay in 1.3.
-
I See, but i think i give a try, upgrades are always better!
Thank you very much!
-
Remember to backup your scene if you wish to get back to it for some reason.
-
SURE! THANKS!
-
probably resolved with the displacement NaN fixes
-
Same problem here. I have small scene with no displacement etc. all in corona custom material and nearly 20 % of the frames were black.
When i red this topic i've changed to PT + PT and everything seems fine.... just render will take sooo long time... i have 1200 frames.
-
what Corona version do you use? can you share the scene?
-
Same problem here. I have small scene with no displacement etc. all in corona custom material and nearly 20 % of the frames were black.
When i red this topic i've changed to PT + PT and everything seems fine.... just render will take sooo long time... i have 1200 frames.
If I am correct, you are running out of Ram memory. PT+PT will do the job but slower.