Cinema4D version 2020.2-R3 (Obsolete stable) 19.02.2021 Tweet

[aoktar]

It's not directly about me, DrawBitmap function is not working as should in R20. What is causing it don't know, but looks like a R20 problem.

I just tested it - it works perfectly with R20 and 2020.1.5 R4

So something must have changed in 2020.2

Of course more than something changed because of optimizations. I wrote why it happened, we hit to some bug or unexpected behavior on R20 for the core functions.

[zoppo]

It's not directly about me, DrawBitmap function is not working as should in R20. What is causing it don't know, but looks like a R20 problem.

I just tested it - it works perfectly with R20 and 2020.1.5 R4

So something must have changed in 2020.2

Of course more than something changed because of optimizations. I wrote why it happened, we hit to some bug or unexpected behavior on R20 for the core functions.

Of course I am aware that lots of things changed with 2020.2
I thought I'd tell you to help narrow down where to look.

[aoktar]

I thought I'd tell you to help narrow down where to look.

Sure it helped, at least gave some ideas to how avoid a crash in case

[CCIDgfx]

I just wanted to update that I went back to 2020.1.5-R4 and store render buffer is working. I just saw another person having the same issue so I know it's not my machine now.

Regards

[jayroth2020]

Kalua, what value is the phong tag set to? Cinema usually defaults to around 40 or so...

Phong is not interfering in this case.
Actually playing with the gamma (from 2.2 to 1) actually fixxes the issue. Is there a guideline on how you should Normal maps be set? Some maps work better than others. Is there any issue I am not aware of?

Yes, normal maps should always be gamma 1.0; in fact any 32bpc bit file should be as well.

[zoppo]

I just wanted to update that I went back to 2020.1.5-R4 and store render buffer is working. I just saw another person having the same issue so I know it's not my machine now.

Did you see the workaround above?
(And yes, it's not your machine

[CCIDgfx]

EDIT: It's an issue for R20, can't fix it. Why do you prefer R20?

I have the same issue and I don't intend to switch from R20 soon (lots of plugins ...).
The Live Viewer A/B view is not working, store render buffer is not working and this is a HUGE problem that should be dealt with.

Now, my friend useruser found a workaround, so Aoktar, I think this should be fixable in R20:

Enable "Lock resolution" and change the y-axis resolution to something other than 1:



That's it. You can change both values so they match, but the important one is the second one.
It does even work when you set it to 1.01 and leave the other at 1.

Thank you so much dude =)

[Kalua]

Kalua, what value is the phong tag set to? Cinema usually defaults to around 40 or so...

Phong is not interfering in this case.
Actually playing with the gamma (from 2.2 to 1) actually fixxes the issue. Is there a guideline on how you should Normal maps be set? Some maps work better than others. Is there any issue I am not aware of?

Yes, normal maps should always be gamma 1.0; in fact any 32bpc bit file should be as well.

Thank you. I didn't know it.

[newartstudios]

Another issue is inaccurate F Stop for octane camera. F 0.5 should give You insane shallow depth of field, but it's barely noticeable. This looks more like F 4.6. I can crank up aperture edge setting to max value 3, but it still doesn't match reality.

[divasoft]

Another issue is inaccurate F Stop for octane camera. F 0.5 should give You insane shallow depth of field, but it's barely noticeable. This looks more like F 4.6. I can crank up aperture edge setting to max value 3, but it still doesn't match reality.

+1