Corona for C4D Alpha 6 is out! This is the final version of Alpha 6, with many new features (and bug fixes) compared to Alpha 5 - full details (and there are a lot!) are on the blog post:
Your processor doesn’t support required features (SSE 4.1). You need to use legacy version of Corona Renderer. Contact our support for more info.
I using legacy version (Phenom II X6 1055T) and Corona is work. Possible, you forget remove the condition in legacy version.
This error is irritate =) You must to click Ok.
p.s. Why “You need to use legacy version of Corona Renderer”?) Sorry for my English
p.p.s. WTF verification system?! I dont saw word the “Main” and tried input “Alfa”. After i copy/paste “3ds Max: FairSaaS” and error and error. I wanted close forum, but i tried however the “FairSaaS” and Bingo =)
GokhanB, the legacy version for CPU which don’t support SSE4.1 . For example, old AMD CPUs - The legacy version slowest them the standard.
The legacy version and standard version included in the installer. The installer select a version, which for your CPU
I’ve been using it everyday for the last week and not a single crash or hang or anything! Super stable release for me for an alpha, excellent work. Can’t wait for Corona for Cinema4d to conquer the rendering world
Is anyone experiencing odd behavior when rendering high res (4k+)? Using Corona and rendering pretty much anything of higher resolution the VFB gets quite laggy and there are some weird freezes going on every couple of seconds.
Hi, do you use Windows or macOS version of Corona? Other users already reported this problem earlier, but we still can’t reliably reproduce this bug so I would like to ask you what is the exact procedure to reproduce it? Thank you
That would actually be on Windows, 8.1 to be precise.
I haven’t quite nailed it down as to when it happens and I’ll report back once I have more concrete info.
On a side note, and it might be connected to the first issue too, the VFB is going a little bit crazy with bloom & glare - crazy as in it sometimes flickers. It isn’t reliable as sometimes it doesn’t even show up for 10 seconds while if you turn it on or off it takes 1 second to initialize.
the flickering or goin crazy is not actually a but.. this is caused by turning ob bloom/glare during rendering and the flickering is just the update frequenzy on your VFB when adding new pixles+adding the effect..
simple solution would be to turn it off while rendering inside the VFB or before by unchecking the box in the rendersettings and adding it after the render is complete (or stopped) and already denoised. since the VFB letz you change a lot of setting after the render is complete - hell, you can even change the entire lighting via lightmix after you are done ..
@NkilarI’ve had similar problems with B&G - as hog0 says its better once the render has completed but it’s still not great. I don’t know if this is an issue in max too?
B&G used to slow the render down quite dramatically if it was on with earlier versions of the RC’s but it’s better now, I still think it slows it down but not sure to what extent.