|
rgreenidge
|
rgreenidge
Posted 9 Years Ago
|
|
Group: Forum Members
Last Active: Last Year
Posts: 257,
Visits: 1.7K
|
The last time I used iClone, and I didn't update to 6.4 quick fix, due to some of the problems people had on here. Well it worked all night without crashing. Before that it started crashing all over the of the place a 2 weeks ago, sometimes while just playing with the content menu etc. I thought the new video driver solved my problem, then a few days later I was crashing. What I did next was to defrag my iClone hard drive, it was up there in %. Then I went in the computer control panel etc., updated and really increased my virtual memory size on all the drives I use for the virtual memory. The iClone drive was the only drive I had to defrag, and for myself it's the only drive other than my backup where I'm constantly adding, deleting, overwriting files, where then the info that should be together ends up all the drive. Since the defrag, and virtual memory changes, I've had no crashes the whole last night I worked on iClone, but I'm still working with a 800x450 rendering screen, while working on my projects before I change to 1920x1080 and making the video files from them (PNG) and separate audio files. I don't use any virtual memory space on my iClone hard drive, I keep it separated. I let 3 other drives handle the virtual memory. You can set the virtual drive memory to automatic, but I prefer to do it manually because I like using a bigger fixed size. I would at least recommend a minimum of two drives, one for your Windows System (C) and your virtual memory and one drive just for iClone. I'm not a fan of SSD drives, because the more you write to it, the more it wears out. Yes it's fast, and probably faster to end up in the garbage? When they solve that problem, give me more $torage, I'll probably buy one. There was a time I didn't trust hard drives.
Home built; ASRock X570 Pro 4, AMD Ryzen 9-5950X CPU, AMD RADEON RX6900XT, 16GB video card, 131GB of RAM.
|