Author Topic: Layer in bump texture rollout  (Read 5962 times)

2019-01-09, 00:05:17

renjin

  • Active Users
  • **
  • Posts: 13
    • View Profile
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.

 

2019-01-09, 20:38:22
Reply #1

renjin

  • Active Users
  • **
  • Posts: 13
    • View Profile
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.

2019-01-10, 07:18:42
Reply #2

Gruender

  • Active Users
  • **
  • Posts: 109
    • View Profile
I can confirm this bug, it doesn't even work without the normals shader for me! It seems as the layer shader isn't supported in bump slot (accidentely?).

Cheers...

2019-01-10, 09:07:14
Reply #3

fabio81

  • Active Users
  • **
  • Posts: 444
    • View Profile
we confirm, the native Cinema shader inside a level does not work.

2019-01-10, 09:11:38
Reply #4

houska

  • Former Corona Team Member
  • Active Users
  • **
  • Posts: 1512
  • Cestmir Houska
    • View Profile
I can confirm this too, guys. The bump didn't work for me in the layer shader either. Will look at it today!

2019-01-10, 19:17:55
Reply #5

renjin

  • Active Users
  • **
  • Posts: 13
    • View Profile
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.

2019-01-11, 11:09:53
Reply #6

houska

  • Former Corona Team Member
  • Active Users
  • **
  • Posts: 1512
  • Cestmir Houska
    • View Profile
[...] 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.

This doesn't seem to be the case for me. C4D textures have the same bump strength, when I set it to 100%. C4D noise bump, on the other hand, used a different implementation in the Betas, so now it lookse different, which can affect the strength of the effect too.

2019-01-11, 17:28:16
Reply #7

renjin

  • Active Users
  • **
  • Posts: 13
    • View Profile
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!

2020-12-15, 20:11:51
Reply #8

Fitch

  • Active Users
  • **
  • Posts: 8
    • View Profile
I'm having the same issue. Need to combine two shader to make a bump and the layer channel doesn't seem to be working

2020-12-15, 23:29:28
Reply #9

lollolo

  • Active Users
  • **
  • Posts: 261
    • View Profile
I'm having the same issue. Need to combine two shader to make a bump and the layer channel doesn't seem to be working

Are you using noise shader? This is an old issue which hasn't been fixed, unfortunately. As a workaround, you could use uv(2D) space. But I'm waiting for a fix too!