Try minimizing viewport to smallest possible size and render. Is the result the same?

HOLY SHYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYX!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

That actually made a difference!
OMG - The ol' resize the screen maneuver strikes again.  
THANK YOU 4U2GES!!!!

It didn't actually eliminate the problem, but it does drastically minimize it.  Some of the hair looks darker and pixelated, but not too noticeable.
Fascinating....almost like, if you can 'hide' the pixelation from the screen, then iClone can't see it and won't render it. 
And you can hide it by making the viewport smaller through pulling the timeline towards the top of the screen.  
So weird, but really amazing that it works this way.  Wondering if this is actually a NVidia driver issue revealed through iClone.

Well, developers can take note of the fact that viewport size adjustment does impact how iClone renders pixelation occurring with overlapping opacity masked textures (ie Daz hair with multiple overlapping textured pieces). 

Really appreciate that help, 4U2ges!  

I was not really sure if that would work, because you had monstrous artifacts there. But I am glad it almost did. For animation though it would take helluva lot of time to render with viewport size that small regardless of setup.
And the idea actually came from your thread about DOF dependency on the viewport size. I was afraid after fixing it (according to your FT entry), opacity artifacts would not go away anymore by varying viewport size. But apparently a workaround routine is still valid.
See the original thread: https://forum.reallusion.com/339948/Opacity-Artifacts?PageIndex=1

Playing around some more with the artifacting hair due to overlapping opacity-masked textures: 
-hair with shine roughness cranked up (to 'black') gives more artifacting than the same hair with roughness lower (to 'white')
-resizing screen will eliminate large artifacting, but will not eliminate small artifacting
-workaround is to lower roughness on artifacting areas/pieces, or pull them out by reducing opacity.  Then resize screen prior to render (resizing results can vary depending on resize and artifacting amount you start with.) 

Some other engines have this problem, including Unity.  I saw in another thread for a different software (Godot) a user is speaking with another user about flickering trees on a mountain top, and the assisting user refers to "back face culling" and "z-depth sorting" as possibly causing the issue.  Assisting user ultimately had no solution for the other user.

Really strange!  I can confirm that the custom export to 4096x2048 is working fine now.  I tried it several times before posting this...

Thanks Kellytoons. 



Ryzen R9 5950x, RTX 3090, 128Gb Ram ,2 x 2 TB Samsung 980 Pro M.2 SSD

Horror Stories in VR
Immersive Sound VR
Immersive Sound VR on Oculus TV

Well, I have been playing with this DOF stuff in another scene and it all of the sudden I found it was giving me exactly what I wanted.  A very strong Blur to very sharp over a short distance.
I took the settings and moved them to my other scene, and Voila, I had what I wanted.
I just wasn't arranging the sliders properly to get the effect I wanted, but I found it is possible.  It was made a lot easier by using the DOF color-viewer.  That really shows you what you have depth wise.
Such a fantastic tool it is!
 

Setting the bokeh to various shapes has a dramatic effect in DOF level as well. The circle bokeh type will really increase the blur amount. That's how I like it!

i

nope, i can create a new scene and have undo but as soon as i save it and open it again it is gone

Undo is only available for the open, active, Project. As soon as you close a Project and reopen it the undo information is gone. This is normal as undo information is not saved with the Project.


Gerry

---

System: Win 10 Pro (21H2), Asus X99-E WS, CPU i7-5930K -3,5 GHz, 32 GB DDR4 2666-16 RAM, NVidia GTX 1080 Ti GPU - 11 GB VRAM(Driver Studio-536.99), Samsung 850 Pro 512 GB SSD, 6 TB HD storage.

that is not what i meant, what i meant was that once i save a project and open it again will cause undo to stop working, if i make any change to the project i can't undo it, happens everytime