Votes
6
Product:
iClone 6
Version:
6.42
Status:
Hold
Issue 465
Bug that makes Iclone crash, when you export to Indigo
Hi all, I have been raising this in the forum and in cases with RL a couple of times. They asked me now, to open a feedback tracker case. Please kindly support, so they see the urge to get this fixed. Although they promised to do it in the past already.

What is the issue :

When you export scenes as animation to Iclone => it crashes (example, export the abandoned house scene from Iclone 6 all frames). Originally RL confirmed to fix the bug in 6.5. No nobody seems to be able to remember it.

Reason : RAM Memory overflow (therefore it happens on an irregular base, based on other software running and total RAM on the computer available)

IMPORTANT : THIS IS KNOWN SINCE VERSION 6.0 of ICLONE !!!!!!
SO the bug exists since nearly 2 years.

But to be constructive, let's make some suggestions to RL :

Potential fixes

FIX A:

INTERMEDIATE SAVE IT FIX
Iclone exports 3 Things in the process a) all the material, etc in a folder, b) an .igs file that helps to read that and c) after it has done all the work an information to Indigo how many files there are. (and here lies the problem, if it crashes it has exported tons of A,B but C does not exist. So the solution is, after every A,B has happened, just write an intermediate file for C, and erase it again after the next A,B has been created. That makes sure, you can at least render, before the tool crashes.

FIX B:

FIX THE PROBLEM FIX
ICLONE can export one frame without any trouble. The tool only crashes once many frames are exported. So, why is it crashing after all? My assumption is, that the memory is not being cleared out, after exporting a frame. Somehow Iclone does not erase the just rendered scene in the RAM or does only partially do that. I have monitored this a couple of times and there seems to be a Memory set-back in the tool, but that happens irregular. So I assume the code needs to be reviewed and ensured, that the memory is set-back after every frame has been exported.


PLEASE VOTE FOR THIS ISSUE AS RL IS SELLING A SOFTWARE THAT IS BUILD TO CRASH, WE ALL ARE PAYING FOR BEING ABLE TO RENDER FILMS IN INDIGO, BUT THAT DOES NOT WORK AFTER ALL!!!!

The bug has been recorded on all Operation Systems Win 7 and 10. On various machines, various configs. The bug has been confirmed by RL. I am copying the case number and Peters feedback below !

PLEASE VOTE !
OS: Windows 10
Related Issue:   Indigo Plug In Memory Issue (Issue 567) (Issue 852)Iclone 6.5. Plugin to Indigo crashes (Issue 567)
Attachment:
  • Bildschirmfoto 2016-06-06 um 07.50.19.png
  •  4
  •  3708
Bug
Submitted bysbaerman Jun 6, 2016
1
COMMENTS (4)
Ascensi Oct 9, 2017 
Disable all shader quality settings in iClone, lower tessellation to 0 if using it, re-enable tessellation in Indigo -iClone quality settings are for iClone not indigo and will reduce/kill performance. I spent over a week trouble shooting with both Reallusion and Indgo team and came to this realization and have since asked them to update their manual to add this essential tip. I have since been able to render scenes over 3 million polygons example showing it works https://www.youtube.com/watch?v=UYfeHF0JClU

When exporting animation squence do not render the frames from iClone to Indigo..  just export the entire project as an Indigo project bet remember if you have all the shaders in iclone set above low quality then you're taking away resources that would otherwise be used to create the iClone projects. Also increase Virtual memory perhaps around 40GB  iClone would die because it would often run out of memory.
fazalqkhan Jun 8, 2017 
whenever I use indigo, my iclone starts acting up. either crashes while rendering (in iclone renderer) or crashes while saving files. Quite frustrating.
sbaerman Jul 18, 2016 
No reaction from RL, they put the issue on hold, but no feedback.
stevevonder Jun 6, 2016 
How can Reallusion do that? First they promise something and they don't even remember. This is strange!
1