Installing wrong version?

[tennet]

I have installed the latest Corona version for C4D, but in my Corona render window it says "Corona 3 (DailyBuild Oct 10 2018)? And if I check the Corona plugin "About" dialog box it says "Version B2 (core 3) Build timestamp Oct 31 2018 17:14:41"...


Do I have the latest version or why does it say different Build dates?

[tennet]

I am running Windows 10 Pro. I just tried to un-install Corona (via Windows "uninstall program") and then re-install the latest download again.. but it still says the same different dates as in my previous screenshot? A friend of mine just downloaded and updated his Corona to the latest version and for him it says "Build date 31 October" in both the "Render Window" and "About" dialog..

Any ideas what is wrong?

[houska]

Hi tennet! This does not seem to be an error. Things like this can happen due to the way we build the plugin. Do you and your friend have the same installer?

[tennet]

Yes, we downloaded them today. He was using an older version than I did, so he updated his Corona and then it says "Build date 31 Oct" in both his render window and the "About" dialog box. My installation shows two different dates (10 Oct in the Render Window and 31 Oct in the About page)?

[houska]

Ok, so if you have the same installer, that's weird... What you see in the about dialog is the Corona for C4D plugin version, whereas the VFB is a part of the Corona Core, so it shows the Corona Core version. You probably have different Corona_Release.dll than your friend. What I'd suggest would be uninstalling Corona, erasing the plugins/corona directory from the C4D folder and installing again. I guess the installer isn't able to update the core .dlls.

If you want to help us debug this issue, try to find out, whether the Corona_Release.dll and CoronaLib_Release.dll files that you have in the plugins/corona folder are the same ones that are bundled within the installer (you can find out by just extracting the contents of the installer somewhere).

[tennet]

Hi Houska,

It seems to be the same files in the new download as in my install folder.. I now un-installed Corona again (using the 'RemoveCoronaForC4D.exe' in Programs/Corona folder).. This also deleted all my Corona plugins from C4D (I have R18/R19/R20 installed).

I then extracted the newly downloaded installer to a local folder. From there I installed it again and after it finished I checked my plugins folder. The plugins were installed in R18/R19/R20.. To be sure it was the same plugin version that came bundled with the installer, then I copied the plugins folder again (from the extracted installer) and replaced the files in my C4D folder.

After starting C4D R19 again, then it is the same. It still says "10 Oct" in the VFB window and "31 Oct" in the "About plugins" dialog (se new screenshot). Are there any other "system files" that Corona uses that need to be deleted? If the VFB window shows the Corona Core version, then my system can't be running the latest build of Corona right now.. right?


(PS! I also run C4D R19 + Corona on my Mac Pro and there it says 31 Oct in both the VFB window and 'About' dialog)

[houska]

After starting C4D R19 again, then it is the same. It still says "10 Oct" in the VFB window and "31 Oct" in the "About plugins" dialog (se new screenshot)

Ok, so this seems like what you have is correct. What about your friend then? Are you 100% sure that he has the same installer and build as you? Could you try the same procedure on his PC?

If the VFB window shows the Corona Core version, then my system can't be running the latest build of Corona right now.. right?
(PS! I also run C4D R19 + Corona on my Mac Pro and there it says 31 Oct in both the VFB window and 'About' dialog)

Aha, that's interesting! So only the Mac version says that the Core build is from 31 Oct? Maybe your friend also has a Mac? In general, I'd say don't worry about this, unless you find some differences in the renderings. The Core really might not need to be rebuilt for one platform, whereas a rebuilt (which manifests itself in a change of the build date) might be needed on Mac. We'll have a look if anything might be inconsistent in the two installers, but otherwise, different build times don't necessarily mean that something is wrong.

[tennet]

Aha, that's interesting! So only the Mac version says that the Core build is from 31 Oct? Maybe your friend also has a Mac? In general, I'd say don't worry about this, unless you find some differences in the renderings. The Core really might not need to be rebuilt for one platform, whereas a rebuilt (which manifests itself in a change of the build date) might be needed on Mac. We'll have a look if anything might be inconsistent in the two installers, but otherwise, different build times don't necessarily mean that something is wrong.

I just doublechecked this with him and he was actually testing this on his Mac earlier today.. and then it showed the same dates in both VFB and About dialog (same as mine does). He just installed it on his PC workstation though and he then got the same "error" as me, with two different Build Dates in VFB/About. He was also using the Official Installer from your website.

Reason that I am worrying is that I find my Cinema R19 crashing VERY often now when working on a Corona-scene (very simple scene with a bit complex shaders using the Node Editor). I'm using the Node Material Editor and when doing updates/tweaks to shaders (while the IR/VFB is active) then it crashes frequently. My Cinema 4D use to be very stable otherwise.. so I was thinking maybe I am running an older build that doesn't have all the fixes installed?

[houska]

Hi again, tennet.

So we double-checked and it's really just a matter of different build times. But feature-wise both the WIndows and Mac version should be the same.

If you are experiencing any crashes however, we'd be more than happy to hear about them. If we could ask you to create a bug report and post it in the bug reports section here on the forums, preferably with the crashing scene and a reliable way to crash, that would be great!

[tennet]

Hi Houska,
Thanks good to know all features are the same then. I can't really share the scene in the forums, but I can create a simpler version of the scene that I can upload to you. Would that be OK?

[houska]

Hi Houska,
Thanks good to know all features are the same then. I can't really share the scene in the forums, but I can create a simpler version of the scene that I can upload to you. Would that be OK?

Hey tennet!

A simplified scene would be even better, if it's still crashing. That would be really great.

[tennet]

Hi! I sent you a simplified scene via Private Transfer (Wetransfer I think..) a week ago. Have you had any time to look at it?

Since I experienced so many issues with the "Corona Shared" shader (when using the Node Editor), then I switched back to the normal C4D Material editor. The crashes are less frequent when not using the Node Editor, but they still happens now and then..

Most often when I restart the IR when using Displacement maps or when I change the 'glossiness' parameter in the Reflection channel. Changing 'glossiness' in the reflections doesn't update in Interactive Render either, I have to restart the IR to see the new effect.