Hi all.
I have been trying to figure out what is going on here. Displacement is the culprit, but all that changing settings does, is move the problems to different areas, or change the reflections to some other weirded out look.
The desired displacement is correct, but the artifacts it causes in NON-displaced areas is the problem.
Displacement Woes
Forum rules
Please add your OS and Hardware Configuration in your signature, it makes it easier for us to help you analyze problems. Example: Win 7 64 | Geforce GTX680 | i7 3770 | 16GB
Please add your OS and Hardware Configuration in your signature, it makes it easier for us to help you analyze problems. Example: Win 7 64 | Geforce GTX680 | i7 3770 | 16GB
Hi,
probably an issue with normals directions or uvs.
Please, change the kernel to InfoChannel, and post a screenshot in wireframe mode with Backface highlight option active, and the uv coordinate pass, thanks.
ciao Beppe
probably an issue with normals directions or uvs.
Please, change the kernel to InfoChannel, and post a screenshot in wireframe mode with Backface highlight option active, and the uv coordinate pass, thanks.
ciao Beppe
Here are the screenshots.
What is weird is that when displacement is added to the two parts (the only ones that have displacement), the button on top (in the middle) which is a completely different part gets screwed up too (it has no displacement).
What is weird is that when displacement is added to the two parts (the only ones that have displacement), the button on top (in the middle) which is a completely different part gets screwed up too (it has no displacement).
Win7 | Geforce TitanX w/ 12Gb | Geforce GTX-560 w/ 2Gb | 6-Core 3.5GHz | 32Gb | Cinema4D w RipTide Importer and OctaneExporter Plugs.
OK...I think I know what is going on, maybe, anyway. I placed the non-displaced mesh polys outside of the UV area in C4D to get those polys out of the way. As a result, their UV coords are black. Could Octane be getting screwed up trying to calculate mesh areas that have no UV coords? But that would not explain why the button part is getting messed up too.
Win7 | Geforce TitanX w/ 12Gb | Geforce GTX-560 w/ 2Gb | 6-Core 3.5GHz | 32Gb | Cinema4D w RipTide Importer and OctaneExporter Plugs.
Hi,
try with a polygon selection and two copies of the material, one with Displacement, and the second without.
ciao Beppe
try with a polygon selection and two copies of the material, one with Displacement, and the second without.
ciao Beppe
Instead of doing this, create a polygon selection and use a copy of material without displacement, or correct the uvs, and paint with 50% gray the parts that should not be affected by displacement.treddie wrote:OK...I think I know what is going on, maybe, anyway. I placed the non-displaced mesh polys outside of the UV area in C4D to get those polys out of the way...
ciao Beppe
Sorry for the delay...Schedule is getting in the way. I will be trying that out tomorrow evening. Will post back.
Win7 | Geforce TitanX w/ 12Gb | Geforce GTX-560 w/ 2Gb | 6-Core 3.5GHz | 32Gb | Cinema4D w RipTide Importer and OctaneExporter Plugs.
Not a direct answer to your problem, but be aware that polygons outside of the usual 0-1range still have UV coordinates, just not within the default area most apps assume as default. "No UVs," and "Non 0-1 UVs," are not always handled the same way across various programs.treddie wrote:OK...I think I know what is going on, maybe, anyway. I placed the non-displaced mesh polys outside of the UV area in C4D to get those polys out of the way. As a result, their UV coords are black. Could Octane be getting screwed up trying to calculate mesh areas that have no UV coords? But that would not explain why the button part is getting messed up too.
- Frank
Animation Technical Director - Washington DC
Thanks, Frank, for the info. It at least explains part of the improvement I see now that I moved those parts back into the 0-1 range, and painted with 50% gray. However, although the texture problems seem to have cleared up, the black triangles are still there and C4D says the normals are fine:Not a direct answer to your problem, but be aware that polygons outside of the usual 0-1range still have UV coordinates, just not within the default area most apps assume as default. "No UVs," and "Non 0-1 UVs," are not always handled the same way across various programs.
Win7 | Geforce TitanX w/ 12Gb | Geforce GTX-560 w/ 2Gb | 6-Core 3.5GHz | 32Gb | Cinema4D w RipTide Importer and OctaneExporter Plugs.

