Chaos Corona Forum
Chaos Corona for Cinema 4D => [C4D] Bug Reporting => [C4D] Resolved Bugs => Topic started by: PsychoTeddy on 2018-02-08, 14:30:12
-
I just installed the Beta version and I have been struggling the whole morning to get the rendering going again.
I kept the same setting as Alpha version. Nothing extreme, because I was currently just rendering fast previews. On Alpha, I'd get the preview within a second or two.
With Beta I first had the problem of everything rendering black until I realized that C4D Sky element doesn't work anymore so I replaced it with COrona Sky.
Started interactive preview again and got a super pixelized preview that didn't change for 20min and then C4D crashed.
I have noticed that it keeps switching between Parsing scene and Computing sec. GI, it never actually starts going through Passes.
I'm not really sure how to fix it?
-
Probably the fastest way to diagnose is for you to send the scene, this could be done using the private uploader if it can't be shared publicly (https://corona-renderer.com/upload (https://corona-renderer.com/upload))
Either way, we'd need to know more about the scene - one thing I wonder is if replacing any Corona camera tags or Corona lights might resolve the crash, in case there is some old format of data in the version saved with the Alpha?
-
Replace old Corona tags, materials & finally create new render settings...
Similar thing (parsing-computing endless loop) happens here if i continue working on a scene made for a different engine. I must clean all residues, then IPR runs fine.
-
Ok, I'll try replacing everything and see if it works. Thank you for the advice ;)
Hope it works.
-
IR reparses the scene every time something important changes in the scene and we cannot know if it influences the way the scene should be rendered. Some 3rd party plugins periodically write some data to the scene, causing the IR to loop. Unfortunately, there's not much to be done with this. But we'll look at your scene and maybe we can fix it or at least identify the culprit.
-
You only uploaded a .jpg file with the pixelated VFB. We can't help you further without looking at your scene file, sorry.
-
The problem with VFB still presists. I've changed all the materials to Corona materials.
It's not the Beta itself, because I've used it on other 3D models that were created from scratch with the Beta version and it worked fine.
Now the only way to get the preview is to render in the Render View inside C4D.
Is there some cache to clear or something to fix this?
I've attached the Render View preview of one of the scenes
-
Most likely, we'd still really need the scene. If you could upload it, that would be very useful! Last time we only received a JPG image of the VFB, but we'd need the actual C4D scene (it won't be shared, or used for anything other than debugging). Thanks!
https://corona-renderer.com/upload
-
Here's one of the scenes from Render View
-
Again, an image of the render doesn't have what we need to diagnose what you are experiencing - we'd really need the scene to find out what is happening in there.
-
This?
-
Here's one of the scenes from Render View
Hey Psycho? I know how to fix your scene. Send it here https://corona-renderer.com/upload and I'll show you!
Save your scene with assets: File > save project with assets.... Zip what you just saved, then send it to us.
-
This?
Nope. Has to be the actual .c4d file (with any relevant assets for texture maps etc.). There's nothing we can diagnose from an image, whether that's a render or screen capture, sorry. We won't be able to help further without the scene being sent along.
-
Yeah you should've clarified what "scene" means because I'm not familiar with the lingo.
-
1532705587_Capture.JPG
Nope...
-
I can see that you sent us an image to the private uploader?? You need to send the entire c4d. Go to File > save project with assets.
-
Yeah, I understand now that scene doesn't mean picture.
I had problems with the uploader even though the file's 111MB so I uploaded it to the Dropbox alternative.
-
Thanks
-
So....
You have a few issues going on. Firstly, you have the gi mode set to "single bounce". This isn't going to do you much good in a dimly lit room like this. Change it over to "full". Denoising was set to remove fireflies, not really needed here. Try full denoising and lower it to .65 (default), the higher you go the more fine details you will lose in wood grains etc.
Secondly, your portals seem to be set up incorrectly. For a good explanation on them, see this article and example 2. https://coronarenderer.freshdesk.com/support/solutions/articles/5000501660-how-do-light-portals-work-in-corona-renderer-
Thirdly, and this has nothing to do with your render quality ;), but your hierarchy is a mess! lol Try to group things ie: lights, cameras, furniture etc A clean workflow is a good workflow.
Other things like your blinds are completely blocking most of the light, I'm not sure if that's what you are going for or not.
The render attached is only 10 passes and it started right away for me.
Hope that helps
-
Thank you for your help and for the tips.
LOL...I know the hierarchy's a mess, sorry about that. It's kind of currently a patched up model that needs cleaning up. I'm also aware of some of the issues with materials that you've mentioned (like the blinds). They've been removed when I was clearing out all the Corona materials.
I tried changing the render settings as you suggested but it didn't really fix the issue that I was having with this particular model. Interactive rendering still doesn't work. It takes forever to start up and then when it does it keeps switching from parsing to Sec.GI or doesn't do anything at all. It never actually starts doing the passes. Now, obviously the model itself works fine on your computer so it has to be something on my end. I've used this version of Corona on new models and it worked fine. So I was wondering if you have any idea what might be causing this issue? Maybe some temporary files somewhere that are clashing with the new version or some type of cache that needs to be cleared?
-
So I managed to fix it in a very crude way. I cleaned up the old file as much as I could and the VFB still didn't work. Crashed C4D a couple of times so I lost my patience and opened a new "scene" in a new folder. I copied parts of the old scene group by group testing the VFB after every pasted group and saving the scene after it tested ok.
I still can't identify what was causing the problem exactly, but pasting everything into a new file worked for me so if anyone ever has this problem try fixing it like this.