Author Topic: Corona Renderer for Cinema 4D Beta 2 Release Candidate  (Read 39895 times)

2018-10-15, 21:08:59
Reply #90

tuami

  • Active Users
  • **
  • Posts: 175
    • View Profile
Hello!
Any chance to get rid of those bright pixels? When using Beta 2 RC1 they dont appear.


Windows 7/10 / Cinema 4D R18/R19 / Corona Beta 2 RC2/RC3
« Last Edit: 2018-10-16, 21:44:40 by konorg »

2018-10-15, 23:17:16
Reply #91

StenierTag92

  • Users
  • *
  • Posts: 2
    • View Profile
BUG Report!

Hi everyone! My R19 stuck at boot logo "Initializing Plugins" with beta2 RC1-2-3. I tried to reinstall and uninstall plugins, but still have the problem :(

2018-10-16, 02:33:35
Reply #92

Eddoron

  • Active Users
  • **
  • Posts: 552
  • Achieved Pedestrian
    • View Profile
Hello!
Any chance to get rid of those bright pixels? When using Beta 2 RC1 they dont appear.
Scene attached...

Windows 7/10 / Cinema 4D R18/R19 / Corona Beta 2 RC2/RC3

Have you enlarged the images of the previous renders and could it be that the hot pixels show up when the camera is closer?
If not, then it's the Mandela-effect.

Do you have volume caustics enabled and what's your MSI? Also your material setups and basically any info we can get.
« Last Edit: 2018-10-16, 02:45:15 by Eddoron »

2018-10-16, 07:58:34
Reply #93

iacdxb

  • Active Users
  • **
  • Posts: 757
  • 3D Deisgner
    • View Profile
    • www.behance.net/iacdxb
Hello!
Any chance to get rid of those bright pixels? When using Beta 2 RC1 they dont appear.
Scene attached...

Windows 7/10 / Cinema 4D R18/R19 / Corona Beta 2 RC2/RC3

In quick.... I set MSI to 1 and after 6 passes....all clear. You can try other numbers where looks better..

...


Windows, Cinema 4D 2023.

2018-10-16, 09:19:39
Reply #94

Beanzvision

  • Former Corona Team Member
  • Active Users
  • **
  • Posts: 3873
  • Bengamin
    • View Profile
    • Cormats
Hold on a minute....You're complaining about pixels after only 6 passes? You have 150 passes set, let it do it's thing, use denoising, then let us know. I just did 20 passes with denoising and a lot of that went away...
Bengamin Jerrems l
Portfolio l Click me!

2018-10-16, 11:45:16
Reply #95

tuami

  • Active Users
  • **
  • Posts: 175
    • View Profile
Hold on a minute....You're complaining about pixels after only 6 passes? You have 150 passes set, let it do it's thing, use denoising, then let us know. I just did 20 passes with denoising and a lot of that went away...

Hello again
I do not know why but the problem has resolved itself. The problem was actually another scene which I had rendered with 160 passes and the bright pixels were still visible. In the B2 R1, the problem was initially not visible. Anyway now it seems to work sorry for the confusion.

project finished ;)

https://www.konorg-shop.de/messestaende/leucht-messestand-led/
« Last Edit: 2018-10-16, 21:42:46 by konorg »

2018-10-16, 14:55:20
Reply #96

Nazar Babiak

  • Users
  • *
  • Posts: 2
    • View Profile
Hi dear devs!

What about that Motion Blur thing I wrote about on page 4?

Thanks!

2018-10-17, 14:42:07
Reply #97

Pepelecrabb

  • Active Users
  • **
  • Posts: 96
    • View Profile
Once again the LUTs are missing in B2 rc3.

2018-10-17, 14:58:36
Reply #98

katzenwaffe

  • Active Users
  • **
  • Posts: 42
    • View Profile
My VFB-tone mapping settings seems to reset all of a sudden all the time. I need to know what I am doing to make this happen to prevent it. Can I lock it somehow?
Let's say I've set up a camera in a scene, and dialed in settings for exposure, highlight compression, saturation etc and all of this is stored in camera tag. Next time I open scene it's sometimes all back to default?

What am I doing wrong?

2018-10-17, 15:06:14
Reply #99

iacdxb

  • Active Users
  • **
  • Posts: 757
  • 3D Deisgner
    • View Profile
    • www.behance.net/iacdxb
Once again the LUTs are missing in B2 rc3.

Its working in OS X.

...
Windows, Cinema 4D 2023.

2018-10-17, 15:16:19
Reply #100

Beanzvision

  • Former Corona Team Member
  • Active Users
  • **
  • Posts: 3873
  • Bengamin
    • View Profile
    • Cormats
BUG Report!

Hi everyone! My R19 stuck at boot logo "Initializing Plugins" with beta2 RC1-2-3. I tried to reinstall and uninstall plugins, but still have the problem :(
Are you still having issues with this? Can you try installing manually?
https://help.c4d.corona-renderer.com/support/solutions/articles/12000005452-corona-renderer-for-c4d-installation-process-beta-version-
Bengamin Jerrems l
Portfolio l Click me!

2018-10-18, 13:51:02
Reply #101

jamieirvin

  • Active Users
  • **
  • Posts: 70
    • View Profile
    • Infinite3D
Does anyone else find that when you 'draw' a region render in the VFB, it doesn't restrict rendering to the defined region until the region is then adjusted?

 This only seems to have been an issue since the arrival of the beta. It wasn't apparent in the alpha releases.

I'm using RC3 on Mac OS
Core 3 HF2 - C4D R19 - OSX 10.13.2 - 64GB RAM

2018-10-18, 13:53:30
Reply #102

jamieirvin

  • Active Users
  • **
  • Posts: 70
    • View Profile
    • Infinite3D
I have also found that if you switch cameras during IR then all the camera settings (tone mapping, LUT etc) reset to default.

This has only happened a couple of times but I thought I was going mad until I realised the issue.
Core 3 HF2 - C4D R19 - OSX 10.13.2 - 64GB RAM

2018-10-18, 16:24:19
Reply #103

ozwald

  • Active Users
  • **
  • Posts: 147
    • View Profile
I have also found that if you switch cameras during IR then all the camera settings (tone mapping, LUT etc) reset to default.

This has only happened a couple of times but I thought I was going mad until I realised the issue.

I believe that the values of the tone mapping, LUTS, ..... etc belong to the camera in which those adjustments are made, if you change the camera you must apply them again.
I think it's like that ... right?

2018-10-18, 17:46:15
Reply #104

jamieirvin

  • Active Users
  • **
  • Posts: 70
    • View Profile
    • Infinite3D
I have also found that if you switch cameras during IR then all the camera settings (tone mapping, LUT etc) reset to default.

This has only happened a couple of times but I thought I was going mad until I realised the issue.

I believe that the values of the tone mapping, LUTS, ..... etc belong to the camera in which those adjustments are made, if you change the camera you must apply them again.
I think it's like that ... right?

Yes, sorry that's not what I was referring to.  If I switch cameras as the IR is rendering, the values on the original camera reset to default when I switch back again. 

I should have explained that better...
Core 3 HF2 - C4D R19 - OSX 10.13.2 - 64GB RAM