Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - houska

Pages: 1 [2] 3 4 ... 74
Bug Reporting Cinema 4D / Re: Render region issues
« on: 2019-07-03, 16:04:47 »
Hi jojorender,

thanks for notifying us. There has been a change in how the regions work recently, causing this bug. We'll fix the issue, but it will mean that it can happen that you load a document and when you start rendering it, only a part (region) of the image will be rendered. But if you use C4D PV instead of VFB, you won't see the active render region, which might confuse you. Do you (or anyone else for that matter) think that this is acceptable? Or will it not be confusing at all? We might change the rendering status text to something like "Rendering render region pass 2/100", would that make sense?

Ok, in that case it's something that we'd like to fix. Would you be able to pinpoint down what's causing those NaNs? The simplest would be if you uploaded your scene to us via the private uploader (link is in my signature below) and we would check that out ourselves. If that's not possible for any reason, you can try simplifying the scene by deleting objects and then sending the smallest subset of the scene possible, where the issue still appears. Of course, we will consider your scene confidential in any case.

I don't think it worked. For some reason, it doesn't show up in our uploads.

Hi Gruender!

The link is in my signature below this post ;-) Thanks for your help!

Bug Reporting Cinema 4D / Re: UV Randomizer - Bug C4D Beta
« on: 2019-07-02, 15:20:48 »
Hi designerman77,

unfortunately, we're still preparing the hotfix for v4, so no progress in the case of UVW randomizer yet.

Bug Reporting Cinema 4D / Re: No License after Crash
« on: 2019-07-02, 14:35:30 »
The user activation data should be saved in "C:\Users\YOURUSERNAME\AppData\Local\CoronaRenderer"
You can check for any changes in that directory when you licence Corona. The next signup, Corona will load your credentials and/or the licence from there.

I checked it and it seems to me that the scene preparation times in IR are a bit longer than I'd expect (around 30 seconds on my ThreadRipper), but it did render just fine. We will investigate this a bit more later

Hi speedeshrimp911!

It seems like you have NaNs in your scene. NaNs are issues in the light transport calculation that manifest as black dots and they have the unpleasant property that any calculation with them propagates with further calculations. This means that when you apply the bloom and glare to an image, which contains a NaN, it will be spread over the whole area of the image. You can check for NaNs yourself by right-clicking in the Corona VFB.

However, it is possible that your issue is already fixed. To check, please update to Corona 4

Hi MilkmanDave!

Try to render with caustics enabled and disabled in Corona Light and compare those two images. You'll see that the caustics are indeed there. There are however two issues with your setup:

1.) The light emitter is so big that the caustics are everywhere and you have a hard time seeing them.
2.) The geometry is not so well-suited to show-off caustics. What you want is concave surfaces that will focus light, making the caustics very bright in some places of the image

Oh, sorry for that. I didn't realize I should add more information to the last answer. My mistake...

No, unfortunately, the sampling focus pass is not present in the C4D version for now. But we have it in the roadmap for version 5, so it will appear in one of the daily builds.

I need help Cinema 4D / Re: Grainy Volumetrics...
« on: 2019-07-01, 14:35:04 »
Hi John!

You are welcome to upload your scene. You'll find the link to the private scene uploader in my signature below.

Gallery / Re: Oh Canada!
« on: 2019-07-01, 13:02:45 »
If I may - the car looks a bit too clean given that it has just been driving that road full of snowy dirty slurry :-)

Interesting fact: I actually found a bug where the light's intensity won't update when you resize the light using the scene's gizmos, so I will fix that for the next daily.

Also, note that all the photometric units work with a constant conversion ratio between the radiometric and photometric quantities, not taking into account the light's color (or rather, presuming a 555nm green light). Note that even if we wanted to do this conversion more accurately, we could still only use a heuristic. Indeed, exact radio<->photo conversion is impossible without a spectral renderer.

Unfortunately, there are no plans on updating the IES code as far as I know. The light distribution parsing works well, so there's no need to change that.

As for the other parameters, they really only have niche uses and currently we have other issues to care about than supporting the whole IES feature set.

You seem to have a lot of memory used in total on the system. Which other applications do you have running? Does it help if you close them? Do you use multi-pass rendering? If so, how many passes do you use? At that resolution, the memory consumption can be quite huge... Could you show us what the Activity Monitor / Memory tab says if you click on Cinema 4D while rendering such a scene?


Pages: 1 [2] 3 4 ... 74