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 5 ... 75
I works for me. I just create a Corona Material with all channels off except for Self-Illumination. Then I load a video into the texture slot of the self-illumination channel and I apply the material onto the C4D Sky object. When changing frames and rendering them in Corona I can see the correct frames from the video.

Ah, now I understand. Yes, we would have to explicitly support the motion tracker object...

So where did you have the footage in the first situation?

No ones forcing you to download and use daily builds. Just stick to latest stable release until another stable release comes out.
Removing dailies would make development slower and stable releases bugier. As much as you don't like dailies, but it saves some time on QA and gets better coverage of different system configurations.


It's possible now, you just have to make the light smaller :-) Try to make caustics visible with a huge softbox in real life and it will also be harder. Plus the object in MilkmanDave's scene is not too well-suited for caustics.

You have to exclude the object & the floor so caustics can work/show.

Sorry, but no. What you're doing there is a hack. The fact that caustics work with excluded objects is a mistake. Normally you'd want to have one light for both lighting the scene and for generating caustics. Separating these two doesn't make physical sense and is terribly wrong. :-)

Bug Reporting Cinema 4D / Re: Render region issues
« on: 2019-07-03, 18:06:02 »
If we fix the render region resetting, I think it will actually fix the TR render regions too. Thanks for mentioning this!

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

Pages: 1 2 [3] 4 5 ... 75