Author Topic: no motionblur while rendering on farm  (Read 4552 times)

2017-02-13, 15:28:19

postwendend

  • Active Users
  • **
  • Posts: 17
    • View Profile
hey i use c4d r18 with teamrender to render on our deadline driven farm a sequence in corona.

if i render a frame localy the motion blur works fine. but when i send it to our farm corona doesn't apply motion blur to the image.

below a reduced slave log from deadline

Code: [Select]

2017-02-13 14:54:18:  0: STDOUT: ========================================
2017-02-13 14:54:18:  0: STDOUT:  Corona for Cinema 4D, version A6
2017-02-13 14:54:18:  0: STDOUT:  Version of core 1.5
2017-02-13 14:54:18:  0: STDOUT:  (c) Render Legion s.r.o., 2014-2016
2017-02-13 14:54:18:  0: STDOUT:  Plugin successfully loaded
2017-02-13 14:54:18:  0: STDOUT: ========================================
XXX
2017-02-13 14:54:33:  0: STDOUT: Rendering frame 9 at <Mon Feb 13 14:54:32 2017>
2017-02-13 14:54:33:  0: STDOUT: Rendering Phase: Setup
2017-02-13 14:54:33:  0: STDOUT: Progress: 0%
2017-02-13 14:54:35:  0: STDOUT: [Corona4D] Parsing of material Mat took 0.003 seconds
2017-02-13 14:54:35:  0: STDOUT: [Corona4D] Parsing of material WHITE took 0 seconds
2017-02-13 14:54:37:  0: STDOUT: [Corona4D] Parsing of material Material took 2.002 seconds
2017-02-13 14:54:37:  0: STDOUT: [Corona4D] Parsing of material ROT took 0.146 seconds
2017-02-13 14:54:37:  0: STDOUT: [Corona4D] Parsing of material WEISS took 0 seconds
2017-02-13 14:55:35:  0: STDOUT: [Corona4D] Parsing of material Material.2 took 57.788 seconds
2017-02-13 14:55:35:  0: STDOUT: [Corona4D] ====RENDER STARTED====
2017-02-13 14:55:35:  0: STDOUT: [Corona4D] Core build timestamp: Dec 21 2016 10:41:03
2017-02-13 14:55:35:  0: STDOUT: [Corona4D] REPORT: unchanged: 0, Prim: 72, Inst: 0, Mtl: 0, Env: 1
2017-02-13 14:55:35:  0: STDOUT: [Corona4D] CoronaCore::renderFrame before core->onFrame
2017-02-13 14:55:35:  0: STDOUT: [Corona4D] Calculating displacement took 0 seconds
2017-02-13 14:55:36:  0: STDOUT: [Corona4D] rtcCommit: 433ms
2017-02-13 14:55:36:  0: STDOUT: [Corona4D] EMBREE: Created 1 elements, memory usage: 158 M bytes.
2017-02-13 14:55:36:  0: STDOUT: [Corona4D] CoronaCore::renderFrame after core->onFrame
2017-02-13 14:55:36:  0: STDOUT: [Corona4D] CoronaCore::renderFrame before unique materials
2017-02-13 14:55:36:  0: STDOUT: [Corona4D] CoronaCore::renderFrame after unique materials
2017-02-13 14:55:36:  0: STDOUT: [Corona4D] Preparing geometry took 0.589 seconds
2017-02-13 14:55:36:  0: STDOUT: [Corona4D] CoronaCore:RenderFrame: after directLight
2017-02-13 14:55:36:  0: STDOUT: [Corona4D] Precomputing light distribution took 0 seconds
2017-02-13 14:55:36:  0: INFO: Task Overall Progress: 100%
2017-02-13 14:55:36:  0: STDOUT: Rendering Phase: Finalize
2017-02-13 14:55:36:  0: STDOUT: Progress: 0%
2017-02-13 14:55:38:  0: STDOUT: [Corona4D] CoronaCore::renderFrame: after GI precompute
2017-02-13 14:55:38:  0: STDOUT: [Corona4D] Computing primary GI took 2.792 seconds
2017-02-13 14:55:39:  0: STDOUT: [Corona4D] Pass 1/200
XXX
2017-02-13 15:05:33:  0: STDOUT: Progress: 99%
2017-02-13 15:05:40:  0: STDOUT: [Corona4D] ------Entire previous render::run took 601258ms
2017-02-13 15:05:40:  0: STDOUT: [Corona4D] Rendering took 601.299 seconds
2017-02-13 15:05:40:  0: STDOUT: [Corona4D] Denoising
2017-02-13 15:05:40:  0: STDOUT: Progress: 100%
2017-02-13 15:07:55:  0: STDOUT: [Corona4D] Denoising took 135.339 seconds
2017-02-13 15:07:55:  0: STDOUT: [Corona4D] CoronaCore::exiting renderFrame
2017-02-13 15:07:55:  0: STDOUT: [Corona4D] Rendered 10/200 passes
2017-02-13 15:07:55:  0: STDOUT: [Corona4D] Unique Primitives: 2310456
2017-02-13 15:07:55:  0: STDOUT: [Corona4D] Primitives with instancing: 2310456
2017-02-13 15:07:55:  0: STDOUT: [Corona4D] Area lights: 91
2017-02-13 15:07:55:  0: STDOUT: [Corona4D] Geometry groups: 72
2017-02-13 15:07:55:  0: STDOUT: [Corona4D] Materials: 78
2017-02-13 15:07:55:  0: STDOUT: [Corona4D] Instances: 72
2017-02-13 15:07:55:  0: STDOUT: [Corona4D] Portals: 0
2017-02-13 15:07:55:  0: STDOUT: [Corona4D] Area lights: 91
2017-02-13 15:07:55:  0: STDOUT: [Corona4D] Avg samples per pixel: 11.0273
2017-02-13 15:07:55:  0: STDOUT: [Corona4D] Avg rays per sample: 65.9552
2017-02-13 15:07:55:  0: STDOUT: [Corona4D] Rays/s: 6.06663e+06
2017-02-13 15:07:55:  0: STDOUT: [Corona4D] Samples/s: 92408.1
2017-02-13 15:07:55:  0: STDOUT: [Corona4D] UHDCache records: 21937
2017-02-13 15:07:55:  0: STDOUT: [Corona4D] UHDCache records added during viz: 0
2017-02-13 15:07:55:  0: STDOUT: [Corona4D] UHDCache rejected %: 45.1186
2017-02-13 15:09:23:  0: STDOUT: Rendering successful: 903.554 sec.
2017-02-13 15:09:23:  0: STDOUT: 2017/02/13 15:09:23  Service Local Machine went offline
2017-02-13 15:09:26:  0: INFO: Process exit code: 0
2017-02-13 15:09:26:  0: INFO: Finished Cinema 4D Task
2017-02-13 15:09:26:  0: Render time for frame(s): 15.144 m
2017-02-13 15:09:26:  0: Total time for task: 16.153 m
2017-02-13 15:09:26:  0: Saving task log...


2017-02-23, 09:29:20
Reply #1

hdri3d

  • Active Users
  • **
  • Posts: 18
    • View Profile
Hello,

I have a same problem !
motion blur work fine in local Mac Pro  but doesn't work whit render farm (Ranchcomputing)
You have a solution to this problem?
Thank

2017-02-28, 17:55:36
Reply #2

hdri3d

  • Active Users
  • **
  • Posts: 18
    • View Profile
I have to use a renderfarm for an animation but the motionblur does not work with the renderfarm!

Do you have a solution if you like

thank you

2017-03-07, 11:19:41
Reply #3

maru

  • Corona Team
  • Active Users
  • ****
  • Posts: 12754
  • Marcin
    • View Profile
Thank you for reporting this, and sorry for no response from our side until now.
The bug reports (either on forum, or other places) will never be lost, so it is sure that our developers will find a solution as soon as possible.
Additionally, I can confirm that this issue is logged in our internal tracker.
Marcin Miodek | chaos-corona.com
3D Support Team Lead - Corona | contact us

2017-03-07, 13:46:07
Reply #4

hdri3d

  • Active Users
  • **
  • Posts: 18
    • View Profile
Thank you very much for your answer,
I tried the rendering with ranchcomputing which is a great renderfarm in france with whom I work often.
They are very professional and they are waiting for news from developers for the solution to the problem of motion blur so that customers can render with the renderfarm
Again thank you for your answer and I take this opportunity to congratulate you for this genuine engine that is Corona for C4D

2017-03-15, 17:00:54
Reply #5

maru

  • Corona Team
  • Active Users
  • ****
  • Posts: 12754
  • Marcin
    • View Profile
Hi, sorry that it took so long, but I have good news - our dev team was able to reproduce the issue, and fixed it successfully. Currently there is no workaround, so we will have to wait a bit more for the updated build. We will be sure to let you know once it will be available for download.
Marcin Miodek | chaos-corona.com
3D Support Team Lead - Corona | contact us

2017-03-15, 17:35:29
Reply #6

hdri3d

  • Active Users
  • **
  • Posts: 18
    • View Profile
Very good news
Thx for your works

2017-03-17, 12:32:01
Reply #7

Nikola

  • Corona Team
  • Active Users
  • ****
  • Posts: 478
    • View Profile
Hi, fixed version will be released next week.

2017-03-21, 07:39:01
Reply #8

hdri3d

  • Active Users
  • **
  • Posts: 18
    • View Profile
awesome
I will be able to render an animation on the renderfarm
Bravo for your work and the speed of correction

2017-03-28, 14:58:24
Reply #9

maru

  • Corona Team
  • Active Users
  • ****
  • Posts: 12754
  • Marcin
    • View Profile
Hi, the new build with command line motion blur rendering fixed is available here:

macOS:https://drive.google.com/open?id=0B7xyYS3daSJ7WV9pYS1ObkVCamM
Windows:https://drive.google.com/open?id=0B7g1HtV8lD7gekZnVlJuSXkxcnM

Please test it and report any problems to us!

Marcin Miodek | chaos-corona.com
3D Support Team Lead - Corona | contact us

2018-01-30, 17:48:50
Reply #10

houska

  • Former Corona Team Member
  • Active Users
  • **
  • Posts: 1512
  • Cestmir Houska
    • View Profile
No more reports, so it is most probably fixed. If this happens again to you, feel free to write another bug report.