x-particles test #1

Deprecated Krakatoa C4D Beta Discussion
1

hi all,

i had a quick look today on beta3, here is the first rendering and some first notes:

  • first of all, GREAT JOB! :slight_smile:
  • c4d sometimes freezes, unfortunately i can´t send some bug reports because the whole system freezes completely :frowning:
  • with x-particles and motion-blur ON, krakatoa doesn´t render in view-port. picture manager works fine.
  • could you implement the console output directly in the status bar? so you can see directly what´s happening without having the console window open.

//

OSX 10.9.1
C4D R15.057
KRAKATOA 2.3.0 BETA3

krakatoa test.jpg
krakatoa test.jpg1500×1000 368 KB

2

cool render trialjam and you sure right about x-particles and motion-blur cuss im having the same issue over here!

3

Thank you, glad you are enjoying it!

Can you exclude memory problems? E.g. using too much memory for particles, or attenuation buffers?
For example, if you have a Point light and you increase its Shadow Map resolution to 2048 or 4096, chances are you will run out of memory on a multi-core machine. Each render thread creates its own attenuation map buffers, and it is very easy to use up all memory for just shadow information. Similarly, rendering very high resolution output creates one image buffer per thread, then combines all buffers into the final image. In a machine with, say, 16 threads your output image resolution would be allocated 16 times in memory during rendering. The solution is to enable the thread limiting in the Misc. panel and use less threads (4,2, or even 1). It will render slower, but won’t hit memory problems.
That being said, everytime it hit a memory limit, KC4D finished rendering eventually (after freezing my OS for the time being due to extensive disk paging). But I am running Windows.

Of course, your problems could be related to OSX (which I haven’t used). Since more than half of our Beta testers are on OSX, I hope we will get enough feedback to figure this out…

We checked and it appears that CINEMA 4D does not render Motion Blur in the viewport in general. Are you aware of another renderer that supports Motion Blur in the viewport? Right now it is logged as Bug and as Known Limitation. If you believe there is a workaround (as in another developer has managed to produce Motion Blur in the viewport), please let us know and we will investigate further.

Thank you for the suggestion, I will log it as a Wish.

4

Thank you for the quick reply Bobo! and thank you all for the hard work. :slight_smile:

5

hi Bobo,

i´m not sure about memory limits, i will have an eye on it…
the maximum memory allocated to particles that i´ve seen in the console was 800mb.
just had a crash, cinema takes 4gb of ram, but the system has 24gb. :frowning: (btw the “qtkitserver 16992 cinema 4d” crashed as well)

i see, just checked, the physical renderer of c4d doesnt´t render mblur in the viewport as well. but krakatoa should then render in viewport without mblur instead of doing nothing :slight_smile:.

6

Ok, thanks! Sounds like a real crash and not memory issue.

I agree, that’s why it is logged as a bug. I guess we have to turn off MBlur internally if it is rendering to viewport.