Try disabling all quality shader settings in iClone, tessellation set to 0 but re-enabled in Indigo if you're using it. Set Virtual Memory 40GB or higher on the hard drive you're exporting your project to (for me it helped with large projects of over 3 Million polygons) Only Render from iClone to Indigo with still shots not frames -your computer needs all the processing power it can get and when iClone is loaded it takes a lot away so I suggest you export your Indigo frame sequence. As an example that this method works I'll show you my test project. The landscape here is tessellated. https://www.youtube.com/watch?v=UYfeHF0JClU
The issue has the same result on a win10 so with DirectX 12 only thing that has changed is that IClone crashes faster. Do the question remains. What is so important that it needs ram storage even when working files are written to disk.
We have confirmed that this issue wasn't fixed, we had tried to fix it in earlier time but wasn't succeed, the status for this issue is currently in Hold. We apologize for the wrong status displayed earlier in this issue, it should be set to Hold as in issue 465. Thank you for your understanding. Reallusion
Thank you very much for your feedback. The issue you mentioned has been verified and fixed, it will be released in the next patch of iClone Indigo Plugin. Reallusion
my iclone 6.52 crashes when I try and chage the indigo render settings to range . The program literally just dissapears and crashes without any warning or error message . Im starting to thing there is no customer service and im regretting spending over a thousand dollars on your software . Please get back to me as im needing this to work as I use it for work . I will be looking for a refund on my entire purchase if nobody get's back to me . I have been waiting over a week for a response. My email is drsikora@outlook.com . My computer is an i7 with 16gb ram and ge force 4gb