Votes
0
Product:
iClone 8
Version:
8.12
Status:
Active
Issue 9107
Garbage collection bottleneck during MI File save causes progressively slower export
1. Export 200 frames. The tenth frame is exported four minutes later. Average 2.5 frames per minute.
2. Note the time it takes to export 100 frames is 46 minutes later, or 2.17 frames per minute.
3. The 200th frame is not done in 92 minutes. It's done in 184 minutes, bring the overall average down to 1.08 frames per minute.
4. Note that if I had exported 400 frames, which I would NEVER do now until this issue is fixed, it would take the better part of a day or maybe more to export.
5. After the export, iClone is useless and must be restarted.

Mind you, all this exporting is before IRAY even begins to start rendering. It's almost debilitating. I remember exporting being slow in iClone 7, but not a progressive nightmare.

Until this is fixed, I'll have to export in chunks of 150, since the dropoff is not so bad at 150. The problem with that is that you have to throw away 60 frames for simulation. You can't have hair and clothing flying around every 150 frames, so you have to back stitch, and discard the simulation frames and even then, the hair doesn't 100% line up. You can tell the video was stitched. So I had to turn off dynamics.

One fix for this would be an option to have the simulation happen OUTSIDE the start of the export, IRAY or not. OR really, just have it do the entire simulation in one frame and THEN start the render. I've never understood why the simulation would ever be included in a render. Even in playback, why not hust have the simulation in lace and THEN play?
OS: Windows 11
Attachment:
  • Render start.jpg
  • 100th frame.jpg
  • Reder end.jpg
  •  2
  •  250
Submitted byJeffster The Mighty
1
COMMENTS (2)
Jeffster The Mighty
The problem seems to be lessened when exporting to an SSD. This isn't just the time involved. It's also the state that iClone is left in after the export is finished. While my new computer does have a main SSD, apparently exporting to the secondary HDD (to avoid online backup of the mi file) causes some sort of additional problem.
Jeffster The Mighty
This appears to be a problem with video running on multiple textures. There were three panels playing looping video, along with clear tubes showing flowing liquid. For this project, the garbage collection becomes intolerable at 150 frames. In other projects, there is no problem.
1