hi,
A week now.... no Corona 4 test user posts or everyone is happy with Corona 3.....?
Thanks.
...
What is the new "pick" button in the VFB?
When I install it, it tells me in the progress that the current version is already installed and it is being ignored.
QuoteWhen I install it, it tells me in the progress that the current version is already installed and it is being ignored.
+1 for this issue
C4D R20.057 PC.
Cheers
To everyone having the install issues - does uninstalling Corona for C4D help or not at all?
My scene crashes Cinema 4D immediately after opening it with the new version. January version was fine and stable.
MacOS 10.14.3 , Cinema 4D R20.026, Corona 4 20 February version.
My scene crashes Cinema 4D immediately after opening it with the new version. January version was fine and stable.
MacOS 10.14.3 , Cinema 4D R20.026, Corona 4 20 February version.
This is strange, we try every build on our internal test scenes of course. Could we see your scene please? Maybe it's something scene-specific
My scene crashes Cinema 4D immediately after opening it with the new version. January version was fine and stable.
MacOS 10.14.3 , Cinema 4D R20.026, Corona 4 20 February version.
Thanks for the update
When I install it, it tells me in the progress that the current version is already installed and it is being ignored.
After "successful installation" it appears that nothing changed in c4d.
I had to manually uninstall corona and reinstall it to get the latest beta.
My scene crashes Cinema 4D immediately after opening it with the new version. January version was fine and stable.
MacOS 10.14.3 , Cinema 4D R20.026, Corona 4 20 February version.
This is strange, we try every build on our internal test scenes of course. Could we see your scene please? Maybe it's something scene-specific
We'll never knock back a scene file if it's suspected of causing a crash ;) The private uploader link is in my signature below. Thx
Hi! I rendering with new Corona renderer ( Corona Renderer 4) and have very slow calculating GI, memory (RAM) is quickly over ( Maybe I have too old processor...
My scene crashes Cinema 4D immediately after opening it with the new version. January version was fine and stable.
MacOS 10.14.3 , Cinema 4D R20.026, Corona 4 20 February version.
This is strange, we try every build on our internal test scenes of course. Could we see your scene please? Maybe it's something scene-specific
It crashes only with this one. Other simpler scenes seem fine. It has lot's of volume builder meshes and the crash happens as far as I can tell immediately after these volume objects are parsed (although it might not be related at all). See my message above if you would like me to upload this scene. Thank you.
Hi,
I can't activate last daily build (period expired for this computer):(
I have tested install beta2 but i have error 14
I do not have a subscription and the 45-day period is over.
I deleted the license and tried again but I still can't activate.
I checked on the site if there was a version available, as for the alpha6 of 3DSmax. But I didn't see any.
editing Materials is painfully slow, especially in the node editor and even if we set the Material Preview Quality to 0.1 or something. When IR is running in parallel, it is basically unusable :/
yes, I too, practically using the IR I was experiencing many sudden crashes without signaling an error and closing Cinema. This in many scenes.
I'm back to the official version 3.
Hi,
during the IR, changing the camera the settings are lost. Can it be solved in the future?
Hi,
during the IR, changing the camera the settings are lost. Can it be solved in the future?
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.
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!
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.
Currently all discussions referring to the Daily go into a single thread that is very difficult to sift through. Maybe section for daily discussions?
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
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.
something wrong with CoronaColorCorrection map and saturation spinner/Now this work as Hue spinner :))
sorry for mistake :00something wrong with CoronaColorCorrection map and saturation spinner/Now this work as Hue spinner :))
Are you sure? Can you post a screenshot? I tried this in 3.2 hotfix and in March 14th 4.0 daily and both of them worked fine...
In het latest Daily Build at least, the "Anisotropy" and rotation of the Anisotropy sliders in a new Corona material do not do anything anymore.
Importing a material from an older Corona scene does have working sliders.
Could we please get this investigated?
Latest Corona 4 Daily Build for OSX
C4D R20
Hi everyone,
sorry for my ignorance but the upgrade from 3 to 4 will be automatic? (for those who have an annual subscription) or do you need to download the exe file from here?
Thanks and good job
Hi everyone,
sorry for my ignorance but the upgrade from 3 to 4 will be automatic? (for those who have an annual subscription) or do you need to download the exe file from here?
Thanks and good job
Hi mutilo, you have to download and install the newer version manually.
We are using Renderer 3 HF 1 ...
I have also just started getting NANs is some recent work. ...
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
Sounds great.
Do you know if the freezing during material creation/editing in the last two dailies has been addressed?
(reply #50, #76 in this thread)
Thanks,
-Shane
Sounds great.
Do you know if the freezing during material creation/editing in the last two dailies has been addressed?
(reply #50, #76 in this thread)
Thanks,
-Shane
Hi Shane! We are not experiencing any freezes on our Mac machines. Could you provide us with more information? A video would be nice for starters.
Also, when the C4D is hanging, could you send us the result of "View" -> "Sample process" in the "Activity monitor" for the C4D process?It might also be the result of some other plugin conflicting with C4D. What other plugins do you have installed?Edit: I just read your previous post, where you said that you uninstalled all the plugins and the material creation is still slow for you. In that case, the sample of the process would be great!
Thanks!
Hi, Corona Image Editor not working in new release. (Mac OS).
I get the same issue with the image editor. It won't start at all.
Not sure how much other people use the image editor but I find I am using it all the time. Definitely can't live without it :-)
Sounds great.
Do you know if the freezing during material creation/editing in the last two dailies has been addressed?
(reply #50, #76 in this thread)
Thanks,
-Shane
Hi Shane! We are not experiencing any freezes on our Mac machines. Could you provide us with more information? A video would be nice for starters.
Also, when the C4D is hanging, could you send us the result of "View" -> "Sample process" in the "Activity monitor" for the C4D process?It might also be the result of some other plugin conflicting with C4D. What other plugins do you have installed?Edit: I just read your previous post, where you said that you uninstalled all the plugins and the material creation is still slow for you. In that case, the sample of the process would be great!
Thanks!
Hi Houska, attached is a video of the issue and a process sample.
Thanks,
-Shane
Hi Tom, can you explain the logic behind the "render perfect" check box in the light settings? Why use it and why you wouldn't?
Some quick testing with cloners and instance modes:
Cloner instance mode=Instance
Cloned Object=Corona Lights (IES & non IES)
Works in IR
Works in PV/VFB
Cloned Object=Primative
Works in IR
Works in PV/VFB
Cloner instance mode=Render Instance
Cloned Object=Corona Lights (IES & non IES)
Works in IR
Does Not Works in PV/VFB (cloned lights don't show)
Cloned Object=Primative
Works in IR
Works in PV/VFB
Cloner instance mode=Multi Instance
Cloned Object=Corona Lights (IES & non IES)
Does Not Work in IR
Does Not Work in PV/VFB (no lights show at all)
Cloned Object=Primative
Does Not Work in IR
Works (yes, works!) in PV/VFB
OSX 10:13:6
R20.059
There are no parameters, so this article for Max has all the info in it:
https://coronarenderer.freshdesk.com/support/solutions/articles/12000056738
Basically, just check the Fast caustics checkbox, and reflective caustics are added for the whole scene. Then for materials that need refractive caustics, just enable the Caustics checkbox under Refraction in that material.
One thing to note, please ensure that "Render Perfect" is checked for any Corona Lights which are set to Sphere (actually, make sure of that anyway, whether you are using caustics or not).
Frame synchronization failed: Communication Error" It was suggested on another thread to use 'Arbitrated (experimental)' Team Render setting. This solved the issue with the nodes dropping. However, it created a new issue. We then found that about 40% of the machines (all identical) wouldn't STOP rendering and their render client required restarting every time. With each render teat it would be different machines that would 'stick'. This is when I decided to install the latest daily. After doing so team Render (Arbitrated mode) no longer works at all. The render clients' console says they are picking up the job and rendering passes but there is no output on the local machine's picture viewer and it displays the following: "Team Rendering pass 0/0 on 0 nodes. So now I am a bit stuck and considering rolling back to V3 as Team Render was considerably more stable then. Anyone else had similar? NB: All machines are MacOS 10.13.6 running C4D R20. |
I think the latest (Daily Build 2019-05-03) is a lot slower in comparison with (Daily Build 2019-04-16)....or it's just me :)
I don't have (Daily Build 2019-04-16) anymore on PC.
Old versions ((Daily Build 2019-04-16)) is no longer available (Changes in Corona Renderer 4 for Cinema 4D (Daily Build 2019-04-16) (https://drive.google.com/drive/folders/1--L2vBzH3sFxSfdglqlHoxF9NCS2W2xU) ...so I can't do any test :(
P.S. I found it ... I overlooked the folder up! I'm so ... :D
P.s.2: It looks like there is something wrong with our .STEP file so we have long render times or it's some of metal material...hmm
Anyway..10h for 3500pix render noise level 3 (just 3d model + hdri, without floor, empty scene) is insane?
Does Beta 4 has an improved bump calculation, official v3 has a huge problem with greyscale bump maps.
I don't have (Daily Build 2019-04-16) anymore on PC.
Old versions ((Daily Build 2019-04-16)) is no longer available (Changes in Corona Renderer 4 for Cinema 4D (Daily Build 2019-04-16) (https://drive.google.com/drive/folders/1--L2vBzH3sFxSfdglqlHoxF9NCS2W2xU) ...so I can't do any test :(
P.S. I found it ... I overlooked the folder up! I'm so ... :D
P.s.2: It looks like there is something wrong with our .STEP file so we have long render times or it's some of metal material...hmm
Anyway..10h for 3500pix render noise level 3 (just 3d model + hdri, without floor, empty scene) is insane?
Would be fun seeing what the normals are doing :)
Good evening, I had a big problem tonight while the computer was rendering, I programmed a take with more views to deliver the work today, but this morning I found the little surprise, the first image opened but the other 4 didn't open, I downloaded the latest build of beta4, I don't know if it could depend on that.
Below the error message, thank you
Good evening, I had a big problem tonight while the computer was rendering, I programmed a take with more views to deliver the work today, but this morning I found the little surprise, the first image opened but the other 4 didn't open, I downloaded the latest build of beta4, I don't know if it could depend on that.
Below the error message, thank you
Hello, I kindly ask for support from the Corona team to be assisted in the problem already exposed, the risk taken yesterday, that is to say not being able to deliver the work could recur.
In case you have to use different support channels from this there will be no problems in provedere, thanks.
Best regards, Roberto
Hey @ Minimaldesign.
I also use the latest 4 Beta (for Mac) at the moment.
Maybe it´s because of the Layer in which you inserted your metal-stripe bitmap.
I always put such metal scratches into a filter, so you can control everything... glossiness, contrast, etc.
Color you give to the metal in the color slot of the reflection channel... but I'm sure you know that.
Until now, at me such bitmaps never caused anything like in your description.
The highlight of this release is the inside mode option for the Volume material.
While I'm loving the speed of the internal volume feature, there seems to be a big discrepancy between the preview and the final render??
Make sure you un-check (render perfect on the sphere)While I'm loving the speed of the internal volume feature, there seems to be a big discrepancy between the preview and the final render??
That did it! Thanks for the help.
I installed this new version of Corona, but still have a warning "No active license found on thi computer"......((
hi guys,
I found a bug about hdr. Load a simple hdr in the slot and try to start an animation, the frames will be rendered alternating with a black one and the right one. this with the latest beta and win10
now I'm back with the Daily Build 2019-04-16 and it works fine
thanks
No, I dont buying your licences ;( Maybe sometimes Corona make a free beta-version....
It so sad ((
Our update with Daily build:
I noticed if I use "use high quailty filtering" corona needs around 310 passes to reach noise level limit 4
If I use an old Type "tend" filter, it only needs around 200 passes to reach noise level limit 4
hmm ... I'm a little confused (very high price for to me invisible difference in quality)..it's around +33% and more in render time!
Our update with Daily build:
I noticed if I use "use high quailty filtering" corona needs around 310 passes to reach noise level limit 4
If I use an old Type "tend" filter, it only needs around 200 passes to reach noise level limit 4
hmm ... I'm a little confused (very high price for to me invisible difference in quality)..it's around +33% and more in render time!
Below are tests with my home old PC.
Our update with Daily build:
I noticed if I use "use high quailty filtering" corona needs around 310 passes to reach noise level limit 4
If I use an old Type "tend" filter, it only needs around 200 passes to reach noise level limit 4
hmm ... I'm a little confused (very high price for to me invisible difference in quality)..it's around +33% and more in render time!
Below are tests with my home old PC.
310 passes is really a lot. What is the render resolution you used. I just did a similar scene (matt and glass ball on background with HDR light @1600x900 4% noise level limit) and both scenes took only 5 and 10 passes for both HQ and tent. (tent was in time 1seconds faster)
What is you GI/AA balance settings (standard=16), when I try it with "2", I do notice the HQ filter is 50% slower then the tent.But "2" is really only needed if you need fast but grainy results. Useless for a 4% noise limit
Demo version can be for free.... =) Ehh, sad news (
For different times of day in one render pass (it's intended for use with LightMix). Sure you could change the color of the sun from noon to evening with LightMix before, but guess what, your sun was still coming down from the center of the sky, not at all like evening ;) Now you can set up different suns at correct angles for different times of day, and in one render get two, three or more different times of day thanks to LightMix.
EDIT or as I always like to say, also for rendering scenes on Tatooine.
On different environments, not yet. Although this is in the core, there is the question of how to effectively implement it in the Cinema 4D UI. This may not make it into Corona 4 for C4D as a result, we shall see.
Hi Corona team,
there's the same bug that was there before about animation and black frames but now it comes with the sun. many frames are rendered black.
I attach the file
thank you!
Yeah, I also get crashes with team render. Will jump back to previous release
- When the VFB history item name is clicked, the whole name text is preselected so that you can easily overwrite it
Just curious, how do you render certain regions in the viewport? I know how to use the built-in Interactive Render Region, but how do you create regions with the Corona version?
It crashes with team render if Multi Pass is activated. Without it works :/
Hi guys...when i start in anteractive rendering and then, after stopped i start a normal rendering i get a crash
c4d r19
Hi guys...when i start in anteractive rendering and then, after stopped i start a normal rendering i get a crash
c4d r19
Hi alexcosta,
thanks for reporting this. But it is not happening to me if I try it here. We will need more information.
For example - does this happen in all scenes that you open? Are you on Win or Mac? What version of Corona for C4D are you running?
maybe the problem is with old scenes?
In V4 RC2 the new 'Green-Magenta tint' in the VFB post effects only works when the camera is moved / altered once a value has been input.
I am experiencing slow start-ups and very slow material previews again on OS X with rc4.
Hi,
On Mac OS I can 't get interactive rendering to work. Interactive Viewport works fine but not interactive rendering. Corona VFB pops up but nothing happens. If I then click start IR nothing happens either.
Thanks.
Hi,
On Mac OS I can 't get interactive rendering to work. Interactive Viewport works fine but not interactive rendering. Corona VFB pops up but nothing happens. If I then click start IR nothing happens either.
Thanks.
Hi installed release version of Corona 4 and Interactive Rendering still not working on mac. Interactive Viewport works but not interactive rendering.
Hi,
On Mac OS I can 't get interactive rendering to work. Interactive Viewport works fine but not interactive rendering. Corona VFB pops up but nothing happens. If I then click start IR nothing happens either.
Thanks.
Hi installed release version of Corona 4 and Interactive Rendering still not working on mac. Interactive Viewport works but not interactive rendering.
mmh, no problems here on imac pro 10.14.5 and c4d 20.059. everything works fine with the vfb.
For me, all the object disappear in objects manager when Corona 4 is installed, reappear once I install Corona 3.1 back. R18 here.
For me, all the object disappear in objects manager when Corona 4 is installed, reappear once I install Corona 3.1 back. R18 here.I can see everything in viewfinder, but object manager stays empty, no matter what I do! Tried restarting, reinstalling etc, nothing works!
What!? Disappear? How? Like the scene loads as empty scene?
There is a problem with the transfer of layer material. If I copy this material into a new scene, then only the layer material is copied, but the materials that are included in it are not copied.
anyone else have this crash in Corona4?:
C4D crashes when in interactive render, changing camera with frames in a stage object. So I have 20 cameras's, each on a next frame in a stage object (for sending to renderfarm). When interactive rendering on frame 1 switches to next frame, c4d crash every time...
anyone else have this crash in Corona4?:
C4D crashes when in interactive render, changing camera with frames in a stage object. So I have 20 cameras's, each on a next frame in a stage object (for sending to renderfarm). When interactive rendering on frame 1 switches to next frame, c4d crash every time...
yes, I confirm
[...]
This issue is easily reproducable so if needed I can provide bug-reports or anything.
[...]
This issue is easily reproducable so if needed I can provide bug-reports or anything.
I just tried to change the camera object during IR both through stage object with keyframes and by switching takes with different camera assigned and both methods worked fine. IR changed the camera view with no crash.
I admit that my scene was super simple besides what I describe (as is always the case - fixing bugs is easier on a simple scene), so the crash might be caused by something else yet.
C4D R19 Win + Corona internal 5.0 daily
WorkFlow, if I may ask - a scene where we would be able to reproduce the issue would be great! Thank you!
I noticed that with the new High quality image filter the times are 20% longer. Maybe with this new filter I can increase the noise threshold? type noise level 5%?
anyone else have this crash in Corona4?:
C4D crashes when in interactive render, changing camera with frames in a stage object. So I have 20 cameras's, each on a next frame in a stage object (for sending to renderfarm). When interactive rendering on frame 1 switches to next frame, c4d crash every time...
... is there any plan to refine the region render behaviour so the 'marquee' doesn't reset on each render start? It's REALLY frustrating. It would be handy to have a tick option to keep the region active.
Already posted a bug report here https://forum.corona-renderer.com/index.php?topic=25148.0 (https://forum.corona-renderer.com/index.php?topic=25148.0)
Hi, installed Hotfix1 of Corona 4 and I still have this problem with disappeared objects in objects manager. R18 here, anyone knows how to fix this?
When I select the regular colour picker it auto select black and won't actually let me select any pixels. The inverse colour picker doesn't do anything at all.
Hi,In my case it only works by click & hold - drag - release. OK to confirm ;)
I'm trying to use the colour picker in the 'colour tint' function as per the explanation in the link below:
https://coronarenderer.freshdesk.com/support/solutions/articles/12000039650-how-to-set-automatic-white-balance-in-the-vfb- (https://coronarenderer.freshdesk.com/support/solutions/articles/12000039650-how-to-set-automatic-white-balance-in-the-vfb-)
When I select the regular colour picker it auto select black and won't actually let me select any pixels. The inverse colour picker doesn't do anything at all.
Colour pickers elsewhere in c4d work just fine though 🧐
thank you so much Burnin! :DMain Menu: Mesh > Commands > Reset Scale - click on "Options" (that's the cog wheel) - and check "Compensate Points"
How do you did to reset the scale without altering the position and coordinates of the object?
I reset the scale and axes but it doesn't work. I don't understand where I'm wrong