Loading...
> >

Eye Problem with Esme Model

DarkRepastDarkRepast Posts: 223
in Technical Help (nuts n bolts)

I'm using this model: https://www.daz3d.com/esme-hd-for-genesis-8-female

And the eyes have this black mark on them.

I played with the surfaces, but I couldn't really find the exact problem.

Any thoughts?

EYE PROBLEM copy.jpg
87 x 58 - 12K

Comments

  • margravemargrave Posts: 1,822

    It's transparency issues caused by the geometry inside the eye being too close to the eyeball. Change your Instance Optimization setting to fix it.

  • DrunkMonkeyProductionsDrunkMonkeyProductions Posts: 979

    Set Instance optimization from "Auto"(default) to "Memory".

    Be sure to check before rendering that this setting hasn't been changed by other assets, such as render settings, you may load.

     

     

  • DarkRepastDarkRepast Posts: 223

    Okay, first off...you folks are amazing. Thank you so much.

    I've never used that setting before and it's been going on 6 years since I started playing with Daz. I'm curious why that happened. Is there some documentation you might recommend so I could gain a better understanding of INstance Optimization and the times you might change it?

     

    Thank you again! I really really appreciate it.

  • felisfelis Posts: 4,304

    The reason is the precision in Daz Studio Iray.

    If 2 polygons are close to each like in the eye, and the character is too far from world origin, then Iray lacks precision and can not seperate the polygon and they will overlap.

    Then by switching instances, Iray place it at world center, and thereby enough precision for no overlapping.

  • margravemargrave Posts: 1,822

    DarkRepast said:

    Okay, first off...you folks are amazing. Thank you so much.

    I've never used that setting before and it's been going on 6 years since I started playing with Daz. I'm curious why that happened. Is there some documentation you might recommend so I could gain a better understanding of INstance Optimization and the times you might change it?

    Thank you again! I really really appreciate it.

    The official Iray documentation by Nvidia explains what it does.

    "Speed" will disable instancing, which is faster but uses more memory, while "Memory" will enable instancing, which is slower but saves memory. For whatever reason, the Iray engineers decided to tack on a feature to that toggle that will shift your whole scene so that the camera is at 0,0,0, which reduces the floating-point errors that cause the mesh intersection.

    If you set Instance Optimization to "Speed" and try to render an outdoor scene by Aako or Andrey Petroskey that has thousands of instances, your computer will crap itself, burst into flames, and then ring your front door.

    Basically, unless you know your scene has no instances and you really, really need a bit of a speed boost, always set it to "Memory".

Sign In or Register to comment.