Page 1 of 2
Glitched render on a big size frame
Posted: Thu Mar 16, 2017 9:13 am
by Darkpulse
Hi,
I've got an issue here when I try to render a simple scene on a big resolution. I need to export for printing on A0 300dpi (9933x14043) and I've got some strange issues. I've already rendered successfuly this scene on a A2 size.
Please take a look at the attached file, you'll see a big artefact on the bottom of the frame (sometimes I got different results on this area).
First I was getting an error message, I saw in another topic to decrease the parallel sampes to 1 and indeed it's help me to render the frame without crashing. Now I always got this artefact on this area. Anyone can help me ?
thanks
Cinema 4D R17.055
Octane 3.05.3
Re: Glitched render on a big size frame
Posted: Thu Mar 16, 2017 12:09 pm
by bepeg4d
Hi Darkpulse,
I suspect that you have not enough memory for this resolution.
Do you have the post effect active? If yes, disable it, you should reduce VRAM quite a bit at this resolution.
Have you tried with Out-of core active?
ciao beppe
Re: Glitched render on a big size frame
Posted: Thu Mar 16, 2017 12:39 pm
by Darkpulse
bepeg4d wrote:Hi Darkpulse,
I suspect that you have not enough memory for this resolution.
Do you have the post effect active? If yes, disable it, you should reduce VRAM quite a bit at this resolution.
Have you tried with Out-of core active?
ciao beppe
No, post effect is disable. Out of core seems to be enabled by default.
I have two GTX1080 so VRAM should be ok, isn'it ?
Re: Glitched render on a big size frame
Posted: Thu Mar 16, 2017 2:08 pm
by bepeg4d
Hi Darkpulse,
what do you see in Console log?
ciao beppe
Re: Glitched render on a big size frame
Posted: Fri Mar 17, 2017 6:45 am
by Darkpulse
Code: Select all
Started logging on 17.03.17 07:39:31
OctaneRender 3.05.3 (3050300)
Scene created in plugin version -1
Scene created in plugin version -1
FRAME 4 fps:25 camMb:0 objMb:0
docFrame:4 edRender:0 curFrame:4 From:4 To:4 rFps:25 docFps:25
Total time:5.893 ms. Estimated time:5.893 ms.
Calculation completed.... frames:[4-5]
--------------------------- EXPORT LOG ---------------------------
Export materials time= 1.591 ms
Collect objects time= 0.438 ms
Mesh creation time = 5.61 ms.
Triangles:0 Disp.triangles:0 Hairs:0 Meshes:0
VRAM used/free/max:349Mb/6.018Gb/8Gb
Out-of-core used:0Kb total used RAM:4.821Gb
Total export Time = 93.795 ms
movable:0 Nodes:39 camMb:0 objMb:0
Device:0 TotMem:8Gb rtData:46Mb film:7Mb geo:846Kb node:4Kb tex:7Mb unavailable:1.644Gb temperature:43
Device:1 TotMem:8Gb rtData:46Mb film:7Mb geo:846Kb node:4Kb tex:7Mb unavailable:1.547Gb temperature:42
Tried to access null node
Tried to access pin via an invalid ID P_MESH (111)
Tried to access null node pin
Re: Glitched render on a big size frame
Posted: Fri Mar 17, 2017 10:13 am
by bepeg4d
Hi Darkpulse,
please, coud you try with the latest plugin version?
viewtopic.php?f=85&t=59657
There is a change in frame buffer in the latest SDK.
What is the amount of RAM of your system?
ciao beppe
Re: Glitched render on a big size frame
Posted: Mon Mar 20, 2017 12:08 pm
by Darkpulse
hi again,
Same results with this new build. I have 64GB of RAM installed here.
Re: Glitched render on a big size frame
Posted: Mon Mar 20, 2017 2:23 pm
by bepeg4d
Hi Darkpulse,
do you mind to export to Standalone and try to see if you have the same behavior?
Or could you privately share your scene with us for further investigation?
ciao beppe
Re: Glitched render on a big size frame
Posted: Mon Mar 20, 2017 4:03 pm
by Darkpulse
The artefact is not visible with the standalone. Would you like the project file anyway ?
Re: Glitched render on a big size frame
Posted: Wed Mar 22, 2017 4:02 pm
by bepeg4d
Hi Darkpulse,
do you mind to privately share the scene with us, so we can better investigate the issue?
ciao beppe