Hi, Ive rendered out loads and loads of still images in CC3-Headshot and iRay.

So i start with the default character in CC3
I use the headshot plugin
All looks fine....

But then, i render it out and these bizzare triangles appear. Im sure i had the same problem in Unreal, but i just simply changed the material in Unreal and it worked? 
Having no luck in iRay and not much via a google search

It looks like a  Z-fight between cornea and eye mesh under certain lights.
To observer the problem clearly hide the character and reveal eyes only. Then render.

To fix:
1. Try replacing eyes with one of those default DH eyes.
2. If (1) does not help, copy black metallic map and paste it into Displacement slot for Std_Eye_R and Std_Eye_L materials. Set Displacement strength value to 1.

Hi,
Once again thankyou for reply. Im sure you've helped me out with literally All of my queries.

I tried the displacement option and it didnt seem to work

Sorry to be a drag but im not familiar with shortcut speak...

U say replace eyes with default eyes? DH?.. If this is the eyes in content folder, then yes i tried and it made no difference.

Only one set seemed to work. I also noticed ALL my marketplace eyes that i bought are the same.!!!

So frustrating this. Its sun morning got a hell of a lot to do and now im stuck with this HUGE issue. 
Do u think its cos i got a 3090? Had sum issues with it when i first got it. I contacted Reallusion Support and they sent me back sum cut n paste code with instruxtions and it got iray working with my 3090...

Here are the only eyes that seem to work
Game_Eyes_MultiUV
Game_Eyes_OneUV

OMG!!!!!

Just been randomly clicking Sh+t like a madman!!!
FOUND THE FIX!!!!!!
UNTICK this checkbox. Hope this helps any1 in the future!!!

Yes, definately not your 3090 - I had a similar issue here


--------------------------------------------------------------------------------------------------------------------------------------------------------

Please be patient with me ..... I don't always 'get it' the first time 'round - not even the 2nd time!   - yikes! ... 

● MSI GT72VR Laptop, i7 7700HQ 4-Core 3.8 GHz 16GB RAM; Nvidia 1070, 8GB Vram ● iClone-7.93 ● 3DXChange Pipeline 7.81 ● CC-3 Pipeline 3.44 ● Live Face ● HeadShot ● Brekel Pro-Body ● Popcorn FX ● iRAY ● Kinect V2 ● DaVinci Resolve17 ● Mixcraft 8.1

Funny thing is, that this whole mess is caused by the very setting, which supposed to be eliminating those kind of artifacts - Eliminate Shadow Artifacts.
But we have to keep it ON most of the time to have shadows smoothed on body parts, thus all kind of workarounds for eyes




Physically Accurate Cornea setting under some combination of lights/shadows should properly set shadows I suppose (otherwise I am not sure what else does it do). So sometimes we want to keep it ON.
@sonic7 I know you opened an FT ticket at that time and it's been assigned. Let's hope they fix it finally.

I have researched it a bit more and making a proposal to RL.

First, about Physically Accurate Cornea.
In some instances (lights condition), accurate cornea render shadows more accurately IMO.
Like this one.

With Physically Accurate Cornea OFF:




With Physically Accurate Cornea ON:



In both cases above, the Eliminate Shadow Artifacts is OFF.

Now lets turn it ON and keep Accurate Cornea ON:



That looks just terrible.

Now, NVIDIA SDK manual suggests enabling shadow_terminator_offset_mode = on (in CC it equals to Eliminate Shadow Artifacts checked) only in exceptional cases and rather handle odd shadows by tessellating the surface.
Because this mode (if enabled globally) might cause some other issues with 2 meshes being too close to each other. This is exactly what happening with cornea/eye geometry in the screenshot above.

NVIDIA also suggests handling shadow artifacts per object with shadow_terminator_offset = true parameter.
In other words enable Eliminate Shadow Artifacts for body, but not for eyes for instance. But this parameter was never integrated in CC/iClone on object level.
Source: https://raytracing-docs.nvidia.com/iray/manual/index.html#physically_plausible_scene_setup#tessellating-curved-surfaces

I did test it manually by exporting MI scene and inserting this parameter manually into the scene MI file for body instance and it worked just fine.
It did fix body shadows, but did not affect eyes.

So I propose to RL integrate shadow_terminator_offset parameter individually on object level. So that addition check box has to be created.
I will also post this info in sonic7 ticket as well.

Wow, nor much on this topic. Hope ppl in the future see these posts and it helps stop the mind numbing frustration. Ive rendered out about 30 pictures with expressions etc. Only notice the grey shapes when u zoom in. But once u see it you cant UNSEE IT!!!!!

Thanks

For the shadow artefacts option:
Yea, i kinda unticked that option but thought it looked terrible. 

Glad to have a happy ending... Thanks once again

Think iRay overall is an absolute pain. 
Cant use fx particles
Takes waaaay too long to render compared to Unreal
There is 10x more help online if things go wrong.

My new problem is shadows off the lights???????????... Like the actual bulb is casting a shadow....Grrrrrr
No shadow in the viewport, but shadow in iRay viewer??? Again it will prob be some tick box somewhere... tsk