Artefacts with Procedural bump maps

[kopperdrake]

I'm trying to create a cut edge look to a sheet of metal by using a simple procedural bump. On some of the geometry it works, on other the polygin edges seem to be breaking the procedural texture up - any ideas?

I've circled obvious areas in a rather subdued red

[mikefrisk]

It could be your geometry. If you have polys with >4 vertices try tripling them.

[kopperdrake]

Thanks, but I should have said, they're already tripled.

[kopperdrake]

I've just tried it with a UV map and that works fine - I'm a bit stumped. I can use the UV'd texture route for the deadline, but it would be useful to know what's happening.

[kopperdrake]

Oh, now that *is* weird - I actually UV'd another part of that object by mistake - a washer below the screw head, and I assumed it had fixed the issue with the plastic screw head sleeve itself as it's rendering fine now! Does Octane throw a wobbly if there are no UVs associated with an object, even if they aren't needed?

I'll try it on another component and see if that does the trick.

[kopperdrake]

I realise I'm talking to myself - but it seems as though even if there's geometry hidden in LW with the LWOctane Object Properties "Enable State" set to '0', if the geometry is taking up the same space as another object, it will cause artefacts?

[gristle]

Hi there. I recently had an issue with poly artifacts like this.
I was using the Octane projection system. I swapped to using the old projection node (plugged into normal) and LW projection and the issue went away.

I forgot to mention it here, may be one for Juanjo?

[mikefrisk]

It could be so many things. Are you able to upload the object and scene file? Hard to tell from just one still render.

[juanjgon]

I realise I'm talking to myself - but it seems as though even if there's geometry hidden in LW with the LWOctane Object Properties "Enable State" set to '0', if the geometry is taking up the same space as another object, it will cause artefacts?

Hi,

In theory, if the enable state is set to 0 in the object properties the object is not extracted at all, so it can't take the same scene as another object. If you can reproduce this problem, please send me a sample scene to check it here.

About the bump map texturing problem, it is hard to say without a sample scene. Again, if you can attach a scene with this problem, I'll take a look at it.

Thanks,
-Juanjo