C4D Commanline Goes Past 100%


#1

Sometimes when I do renders with the commandline, the percentage of progress goes past 100%. For example, here’s the commandline output of an animation that is 30 seconds long, 60fps, and only renders every fourth frame (I’m using a frame step of 4):

Read shader cache: 391.5 us
Rendering frame 0 at <Mon Aug  1 09:38:11 2022>
Rendering Phase: Setup

Progress: 0%

Rendering Phase: Main Render

Progress: 0%

Progress: 2%

Progress: 3%

Progress: 4%

Progress: 6%

Progress: 8%

Progress: 10%

Progress: 12%

Progress: 13%

Progress: 15%

Progress: 17%

Progress: 18%

Progress: 20%

Progress: 22%

Progress: 23%

Progress: 25%

Progress: 27%

Progress: 28%

Progress: 30%

Progress: 31%

Progress: 33%

Progress: 35%

Progress: 37%

Progress: 39%

Progress: 42%

Progress: 43%

Progress: 45%

Progress: 47%

Progress: 49%

Progress: 51%

Progress: 53%

Progress: 55%

Progress: 57%

Progress: 58%

Progress: 60%

Progress: 62%

Progress: 64%

Progress: 66%

Progress: 68%

Progress: 70%

Progress: 72%

Progress: 74%

Progress: 76%

Progress: 78%

Progress: 80%

Progress: 81%

Progress: 83%

Progress: 85%

Progress: 87%

Progress: 89%

Progress: 91%

Progress: 93%

Progress: 95%

Progress: 97%

Progress: 99%

Progress: 101%

Progress: 103%

Progress: 105%

Progress: 107%

Progress: 109%

Progress: 110%

Progress: 112%

Progress: 114%

Progress: 116%

Progress: 118%

Progress: 120%

Progress: 122%

Progress: 124%

Progress: 126%

Progress: 128%

Progress: 129%

Progress: 130%

Progress: 132%

Progress: 134%

Progress: 135%

Progress: 137%

Progress: 139%

Progress: 141%

Progress: 142%

Progress: 144%

Progress: 146%

Progress: 148%

Progress: 150%

Progress: 152%

Progress: 154%

Progress: 156%

Progress: 158%

Progress: 160%

Progress: 161%

Progress: 163%

Progress: 165%

Progress: 166%

Progress: 168%

Progress: 170%

Progress: 172%

Progress: 173%

Progress: 175%

Progress: 177%

Progress: 179%

Progress: 181%

Progress: 183%

Progress: 185%

Rendering Phase: Finalize

I believe I have only ever observed this while using the Physical renderer and not when using standard.

Any idea why this happens?