Cinema 4D version 2019.1-RC3_r2 (Test build) - 16.08.2019 Tweet

[aoktar]

I just want to remind you that the serious problem with motion blur is still not resolved. I have already spoken about this 4 times.

what's problem?

[divasoft]

I just want to remind you that the serious problem with motion blur is still not resolved. I have already spoken about this 4 times.

what's problem?

Well, I will describe the problem for the fifth time.
MB calculating time increased frame by frame. As you can see 61 frame calculating time is 3:13, but if i restart render same frame (61) will be calculated 1:23 and time increasing again.
The calculation time of one frame can reach half an hour, hours. And again, if I restart the render, the same frames that were calculated per hour will be calculated per minute.
Impossible to render scene with many objects with MB.

[aoktar]

I just want to remind you that the serious problem with motion blur is still not resolved. I have already spoken about this 4 times.

what's problem?

Well, I will describe the problem for the fifth time.
MB calculating time increased frame by frame. As you can see 61 frame calculating time is 3:13, but if i restart render same frame (61) will be calculated 1:23 and time increasing again.
The calculation time of one frame can reach half an hour, hours. And again, if I restart the render, the same frames that were calculated per hour will be calculated per minute.
Impossible to render scene with many objects with MB.

You posted many messages while I'm off at vacation.
Please send your scene, I'll check it what's wrong on your side

[marcus1070]

Hi friends,.. there's a strange behaviour in this version.. the displacement is ignoring the border mode of the image node... on the image atached you can see better.. the diffuse is black border and the displacement still looks wrap around..* both are in the same imagetexture node with black color Border mode

[crackfox]

hi aoktar,

i presume this is known but there are some issues with the upsampler:

- the passes get glitched. the zdepth and ao pass for example look divided into four screens and they are also full of interlace like artefacts.

- the pixels that are too bright also look grainy and very glitched in the denoise pass.

i can upload screencaps if the problems are not known already.

best,

[bagel]

Not sure if it's my particular combination. Here's what I have:

Universal Mat:
Opacity Mask => 16 bit PNG right out of photoshop.
Displacement => 16 bit PNG right out of photoshop.
Displacement Node:
Height: 0.001cm
Mid Level: 0
LoD: 4096
No Filter.

As soon as I connect the chain to the output material, Octane crashes, even when a render isn't running.

If I use an 8-bit PNG for the displacement, it works fine.

This is just an FYI at the moment. The particular piece I'm working on I can't share, but I'll try to reproduce in a new project soon and share that with you so you can try to reproduce as well.

Thanks!

[pxlntwrk]

Hi,
I have some questions about the "SpotLight".
This object is quite new to me, I may not handle it in the right way ...

I noticed that there was a disc to probably reprensent the emitting source of the light,
the diameter of this disc increases proportionally with the spotlight angle.
Should not we have here a control over the diameter of the source emitting light too? (I have not found a way to make this disc invisible too?)
In addition I feel that even with the option "Surface Brightness" unchecked, the brightness of this disc still increases with its surface diameter?



this disk (light source) is located well below the proposed pivot for the object (unknown distance ?) which makes it difficult to set up precisely in a scene ...


Is this the normal behavior for the spotlight?

If not, can someone enlighten me?

thanks

[gohmn]

I have RC3_r2 installed but I'm getting this error message on launch and octane is deactivated. Is there not a newer 2019.1 build right now?

[Raoul]

I also have RC3_r2 installed and am getting this error message on launch... Can we get this fixed ASAP!!?
there doesn't seem to be a newer version to migrate to. Please don't lock us out of octane without any warning like this!

[aoktar]

I also have RC3_r2 installed and am getting this error message on launch... Can we get this fixed ASAP!!?
there doesn't seem to be a newer version to migrate to. Please don't lock us out of octane without any warning like this!

I didn't want to make a new build since we have a few critical bugs. I can make a new build to avoid your situation.