Author Topic: Corona Renderer 4 for Cinema 4D daily build  (Read 55250 times)

2019-03-22, 10:17:15
Reply #60

fabio81

  • Active Users
  • **
  • Posts: 444
    • View Profile
at the moment i'm back to version Corona3 because i have some work in progress, i'll be back to build 4 soon and i'll update you.
Thank you

2019-03-22, 10:19:35
Reply #61

houska

  • Former Corona Team Member
  • Active Users
  • **
  • Posts: 1512
  • Cestmir Houska
    • View Profile
Thank you for your help Fabio. Don't delay your work because of bug reporting, that's understandable.

2019-03-22, 10:29:31
Reply #62

koubankeo

  • Active Users
  • **
  • Posts: 119
    • View Profile
Hi,

during the IR, changing the camera the settings are lost. Can it be solved in the future?

Hi Houska,

just switch to another camera and reset the tone mapping in IR to default?

2019-03-22, 13:02:21
Reply #63

houska

  • Former Corona Team Member
  • Active Users
  • **
  • Posts: 1512
  • Cestmir Houska
    • View Profile
Hi,

during the IR, changing the camera the settings are lost. Can it be solved in the future?

Hmm, you are right, it really behaves in a weird way! Just cube + light + 2x Corona Camera in the scene and when I'm playing with the tone mapping settings in the VFB, the values in both cameras are somehow changed, although only the value in the active camera should change... We'll take a look at it

2019-03-22, 14:29:55
Reply #64

shane_w

  • Active Users
  • **
  • Posts: 130
    • View Profile
Thanks to everyone for all the comments and complaints! They are very valuable to us to be able to catch all the bugs that often do not appear during our testing. Without testing and user reports there will be a lot more bugs!

I would like those of you with serious issues and/or crashes to provide more detailed reports in separate threads so that we have more information to fix them. Steps that lead to reproduction of the crash are a must (or at leasr, describe what you were doing before it crashed - what you clicked, etc...), the crashing scene is very helpful and of course, the _BugReport.txt

Thanks for your continued support!

Hi Houska, where would you like the separate bug reports posted?  It might be nice to have a bug report category for the betas so they don't get put in the regular bug report thread and confuse people using the release version.

-Shane

2019-03-22, 14:39:07
Reply #65

houska

  • Former Corona Team Member
  • Active Users
  • **
  • Posts: 1512
  • Cestmir Houska
    • View Profile
Hi Houska, where would you like the separate bug reports posted?  It might be nice to have a bug report category for the betas so they don't get put in the regular bug report thread and confuse people using the release version.

Hi Shane, I'm afraid the betas are offered without support. If you encounter a bug, it would be best to test it in the newest daily build (or at least the current stable version) and if it is present in those versions, report it. It is however technically not feasible to port bug fixes to older versions for us.

2019-03-22, 14:49:35
Reply #66

shane_w

  • Active Users
  • **
  • Posts: 130
    • View Profile
Hi Houska, I think you may have misunderstood what I am suggesting.  You requested instead of posting bugs in the Beta thread to create a new thread.  Putting beta bug reports in the general bug reports will be confusing for the release version users.  Below is the idea I am proposing.

Corona Renderer Forum
     Corona Renderer for Cinema 4D
          general
               Daily Builds
                    Beta Bug Reports

2019-03-22, 14:53:25
Reply #67

TomG

  • Administrator
  • Active Users
  • *****
  • Posts: 5434
    • View Profile
Hi!

What Houska was saying though was that reporting a bug that exists in a beta version is not something useful - a bug is only useful if it exists in the current release, as that is the only place we can fix bugs. Beta versions are "locked in" and any bugs in those will have to remain there, as we can't bug fix those. So, if you discover a bug in a beta, you would need to test the current release and see if the same bug is there, and if so, report it under a new thread as normal. If the bug is gone in the current release, then no need to report it, as there is nothing we can do about its presence in the beta version.

Thanks!
   Tom

EDIT - in other words, beta versions are provided "as is" with no support.
Tom Grimes | chaos-corona.com
Product Manager | contact us

2019-03-22, 14:58:26
Reply #68

houska

  • Former Corona Team Member
  • Active Users
  • **
  • Posts: 1512
  • Cestmir Houska
    • View Profile
Oh, I see. What you're calling beta is actually a daily build. Sorry for my confusion. BTW, it seems that you confused Tom the same :-) But I think I understand now.

I think a special daily build bug report section would just confuse things. Just think what we would have to do when a daily build changes into a stable version... Instead, I suggest putting all the daily bugs into the bugs section here on the forums, but marking it clearly as such. Something like "DAILY" into the topic would be enough.

2019-03-22, 15:02:08
Reply #69

shane_w

  • Active Users
  • **
  • Posts: 130
    • View Profile
Thanks to everyone for all the comments and complaints! They are very valuable to us to be able to catch all the bugs that often do not appear during our testing. Without testing and user reports there will be a lot more bugs!

I would like those of you with serious issues and/or crashes to provide more detailed reports in separate threads so that we have more information to fix them. Steps that lead to reproduction of the crash are a must (or at leasr, describe what you were doing before it crashed - what you clicked, etc...), the crashing scene is very helpful and of course, the _BugReport.txt

Thanks for your continued support!

Hi Tom, I think this more is being read into my note then intended.  I understand everything you are both saying.  My question is in direct response to Houska asking for daily build bug reports being placed in a new thread.

There is no good place that I can see to do that.

-Shane

2019-03-22, 15:05:44
Reply #70

shane_w

  • Active Users
  • **
  • Posts: 130
    • View Profile
Oh, I see. What you're calling beta is actually a daily build. Sorry for my confusion. BTW, it seems that you confused Tom the same :-) But I think I understand now.

I think a special daily build bug report section would just confuse things. Just think what we would have to do when a daily build changes into a stable version... Instead, I suggest putting all the daily bugs into the bugs section here on the forums, but marking it clearly as such. Something like "DAILY" into the topic would be enough.

Yes!

Currently all discussions referring to the Daily go into a single thread that is very difficult to sift through.  Maybe section for daily discussions?

Thanks,

-Shane

2019-03-22, 15:19:19
Reply #71

houska

  • Former Corona Team Member
  • Active Users
  • **
  • Posts: 1512
  • Cestmir Houska
    • View Profile
Currently all discussions referring to the Daily go into a single thread that is very difficult to sift through.  Maybe section for daily discussions?

Now that I think about it, we can simply create a new section for each new daily build version: "Corona 4 Daily Build bugs", "Corona 5 Daily Build bugs", etc... But I think a better place would be to place it under the bugs section.

2019-03-22, 16:53:52
Reply #72

fabio81

  • Active Users
  • **
  • Posts: 444
    • View Profile
Hi,

during the IR, changing the camera the settings are lost. Can it be solved in the future?

Hmm, you are right, it really behaves in a weird way! Just cube + light + 2x Corona Camera in the scene and when I'm playing with the tone mapping settings in the VFB, the values in both cameras are somehow changed, although only the value in the active camera should change... We'll take a look at it

exactly the procedure is this, in a scene with many cameras set with its own values, in IR selecting a different camera the values all return to 0.
It would be very useful if it were fixed, because every time to avoid this I have to stop IR, select a different camera and then re-launch IR
Thanks :D

2019-03-25, 16:46:45
Reply #73

tiagosaraivacg

  • Active Users
  • **
  • Posts: 73
    • View Profile
    • tiagosaraivacg
Just one doubt guys, i've already posted this issue before. Just wondering if this is a particular case, or everyone else has the same issue.

After working with "Node Edited Materials" I can only preview them rendering directly to the VFB or IR . If I render directly in the viewport. the texture simply disappears and renders black.

Is this a known issue.. will it be fixed? ... since I use node editor a lot. It's a flaw on my workflow.


thanks in advance.

2019-03-26, 09:41:06
Reply #74

Beanzvision

  • Corona Team
  • Active Users
  • ****
  • Posts: 3811
  • Bengamin
    • View Profile
    • Cormats
Just one doubt guys, i've already posted this issue before. Just wondering if this is a particular case, or everyone else has the same issue.

After working with "Node Edited Materials" I can only preview them rendering directly to the VFB or IR . If I render directly in the viewport. the texture simply disappears and renders black.

Is this a known issue.. will it be fixed? ... since I use node editor a lot. It's a flaw on my workflow.


thanks in advance.

Hi, without seeing your node setup I'd say that this might be caused by using the Corona Shared Shader? If that's the case, yes it is a known bug and the remedy would be to not use this until a fix is implemented. If you can share your node setup that would be great!
Bengamin Jerrems l chaos-corona.com
3D Support Specialist - Corona l contact us
Corona Uploader l Upload
Portfolio l Click me!