Messages

1

[C4D] Feature Requests / Drag and Drop layers in Layered Material

« on: 2019-03-18, 16:39:33 »

I'd like to see some way to move layers up and down the stack to speed up edits without having to clear materials/masks and rebuild---doesn't really have to be drag and drop (though that'd be ideal). It could just be a dropdown (this *is* C4D after all) or up/down arrow.

2

[C4D] General Discussion / Re: Rebus Corona 3.0 upload error

« on: 2019-01-14, 18:51:25 »

Rebus has fixed the upload issue. Re-install plugins in preferences window, restart Rebus, and BLAMMO! It works!

Also, I have to say--Rebus' customer service is top notch!

3

[C4D] Bug Reporting / Re: Layer in bump texture rollout

« on: 2019-01-11, 17:28:16 »

I should have been more specific--C4D noise bump is different while all other aspects seem to work as expected. Thanks for the explanation/clarification!

4

[C4D] Bug Reporting / Re: Layer in bump texture rollout

« on: 2019-01-10, 19:17:55 »

Also of note--I've had to uninstall 3.0 and install last available beta because of a Rebus render farm issue (error recognizing Corona version) and there seems to be a pretty big difference in the way 3.0 and the betas handled textures--namely texture strength. I had to reduce nearly all bump map strength levels by 80-90% to get similar results.

5

[C4D] General Discussion / Re: Rebus Corona 3.0 upload error

« on: 2019-01-10, 19:12:17 »

Some back and forth with Rebus team but problem still persists with Corona 3.0--I've since reverted back to last available Corona beta and everything uploads without error.

Also of note--seems bump maps are handled differently between v3.0 and beta versions as I had to do a lot of strength readjustments (reductions--85% down to 3%!) for nearly all materials. 

6

[C4D] Bug Reporting / Bump map issue

« on: 2019-01-10, 02:30:41 »

I posted this in the general discussion thread mistakenly, so sorry for the double post if you see this again.

Bump maps don't seem to work with procedural noise when nested in texture rollout via the "layer" mode. They work in all other instances like Diffuse, Reflection, etc.--it also works as expected with images. Anyway, hope this can be addressed since it's nice workflow to utilize and I used it frequently in the betas. I can post a scene if none of this can be reproduced on your end.

Thanks!

7

[C4D] Bug Reporting / Re: Layer in bump texture rollout

« on: 2019-01-09, 20:38:22 »

I'm assuming either nobody has this issue (aside from my colleagues here at work), I'm not explaining it well enough, or I'm (we) doing something wrong. Attached is an image from a Corona material bump tab--I've put a layer in the texture field so I can stack bump maps and use the layer settings to control each map. This seemed to work fine in the latest beta and it also works fine in the Diffuse and Reflection tabs but for whatever reason i'm having no success in the bump tab--all procedurally created bumps are cancelled out (as mentioned before, images work as expected--it's only C4D's procedural noise shaders that refuse to work). Am I doing something wrong here? Is there another way to stack C4D's procedural noise textures that I'm unaware of? I'd be thrilled if this is something I've been doing wrong for all this time to only find out there's a better/easier/more common way.

8

[C4D] General Discussion / Rebus Corona 3.0 upload error

« on: 2019-01-09, 16:54:55 »

I assume this is more of a Rebus issue, so this is more of an FYI but my team is receiving upload errors for Corona 3.0/C4D. Smartcheck is tagging Corona for an error that says "You need at least Corona 0.2.0.6 to render with rebusfarm...) We all have latest versions of R20 and authorized versions of Corona 3.0 for C4D. I've submitted a ticket with Rebus and will update when I hear anything. That said, anyone else have this issue?

9

[C4D] Bug Reporting / Layer in bump texture rollout

« on: 2019-01-09, 00:05:17 »

Choosing the layer function in the texture rollout with a procedural noise applied doesn't seem to work for the Bump tab in v3.0 (latest versions of R20 and Corona). I can choose an image and it works fine but not so with any of the C4D procedural noise options. Strangely the same process works just fine in the diffuse tab. Anyone else have this issue? This seemed to work perfectly well in all of the Corona betas I used and I haven't changed my process for creating materials at all. Any help would be appreciated.

 

10

[C4D] Resolved Bugs / Re: HDR Light studio connection

« on: 2018-06-12, 18:02:28 »

Update: Corona works well with HDR Light Studio on first interaction within C4D--IR updates work as expected and lighting is consistent with experiences in the past when it's working well. Seems the problem arises after initial setup when HDRLS is re-opened to tweak lighting--I either get a yellow cast of light in IR where I have to close and re-open IR for any updates to lighting changes or IR updates when changes are made but seems to use the temp HDR file in memory, so no actual lighting changes are rendered .

11

[C4D] Resolved Bugs / Re: HDR Light studio connection

« on: 2018-06-11, 23:03:24 »

I'd like to resurrect this issue as I haven't found a viable solution as of yet.

I used to get it to work at least on first try when I setup the prebuilt hook, then it would get wonky and yellow when I did adjustments thereafter. Now it just plain doesn't work--it seems to recognize changes within the HDR Light Studio environment, but updates in IR show no actual realtime changes in lighting.

Also, this didn't seem to affect it before, but I'd like to note there is no way to select Corona as renderer in HDR dropdown list.

Any solutions/workarounds would be appreciated!

Corona 2 build May 28, 2018
HDR Light Studio Carbon (Drop 2) build: 5.6.0.2018.0504

12

[C4D] Resolved Bugs / Re: IR not rendering geometry outside viewable area

« on: 2018-06-07, 21:25:21 »

Alright, I think I've just pointed out my own ignorance when it comes to Corona. All this time I've been using interactive render on lower res images just fine and wasn't aware of the regular render method until I needed to do higher resolutions. I suppose the off screen issue is a byproduct of speeding up the interactive renderer? All good now as the regular render seems to be chugging along just fine.

13

[C4D] Resolved Bugs / IR not rendering geometry outside viewable area

« on: 2018-06-07, 20:17:55 »

I'm rendering a pretty simple scene (2400x2400 - lone product on black) and am having issues where IR will not render the geometry off screen. I can pan around in the window and Corona will update the portions that were off screen, but then the other areas now off screen don't update resulting in either an incomplete image or inconsistent detail. Anyone experience this before? Attached is an image where I didn't pan around and the top half of the image wasn't rendered. Any help would be appreciated!

-R19
-Windows 7 Professional
-Quadro K2200