Page 1 of 1

LV not updating

Posted: Fri Feb 05, 2016 2:18 pm
by miohn
Hi,

maybe some can get me to the point.

I'm working on a heavy scene with 3.1 Version (2.500 objetcs, 3Gig VRam, 8 mio polys)
and the LV will not update anymore.
No matter if I click on "stop and reset dat", "pause", "restart new render"
or "Send scene and restart new render"
it still says "updating" but nothing happens.

Only quitting C4D and restart let me start a new render in LV.

Does it make sense to change some of these settings: OGL samples, LV refresh time(ms) and Performance timer(ms)?
Have no idear what these are doing.

thanks
Mike

Re: LV not updating

Posted: Fri Feb 05, 2016 3:34 pm
by bepeg4d
hmm, I guess that you have reached the limit :roll:
Have you try with the out-of-core option enabled?
ciao beppe

Re: LV not updating

Posted: Fri Feb 05, 2016 3:46 pm
by miohn
hi bepeg4d,

which limit do you mean?
GPU are all titan with 6 GB and in the scene there are about 4.5 Gb are used.

regards
Mike

Re: LV not updating

Posted: Fri Feb 05, 2016 4:26 pm
by bepeg4d
Hi,
sorry I have read 3GB and I have thought that was your GPU limit :(
What about parallel sampling?
Have you tried with out-of-core?
ciao beppe

Re: LV not updating

Posted: Fri Feb 05, 2016 4:35 pm
by miohn
out of core I haven't tried yet, because of 1,5 Gig VRam free.

Sorry, what do you mean with "parallel sampling"?

regards
Mike

Re: LV not updating

Posted: Sat Feb 06, 2016 1:07 pm
by bepeg4d
Hi,
parallel samples is a new kernel parameter and by default is set at 8, if you bring it down to 1, the VRAM consumption will be reduced, but the rendering will be slower.
On the other side, if you bring it to 16, the rendering will be faster but the VRAM consumption will increase.
viewtopic.php?f=33&t=51679
ciao beppe

Re: LV not updating

Posted: Fri Feb 12, 2016 3:39 pm
by jang2235
Please test.

No texture, try using the No Material Triangle Poly rendering fill the 5.5G of memory or more.

I am TitanX users.

Of course, a Lightwave user.

5.5G (39M Poly Over) failed to render over.

I think it's Octane 3.0 issue in the main program.

I think the test for high-capacity memory, because the problem occurred.

This is my Think.