#Free iclone project full

Good visuals can lead to better animations. Wireframe only dropped to 7.1 but was unusable anyway as the landscape wireframe fouled the viewport obscuring everything. Toggling the mode from Normal to Smooth (turning off textures) only dropped usage from 7.2 to 6.9. I could tell you more but 'OK, Boomer' springs to mind since we no longer have to suffer the slings and arrows of the depraved injustice that is monochrome 3D. Just like walking to school in the snow every day when we wuz young 'uns. I could tell you stories about how us ancient ones had to make do with wireframe which was an improvement over bounding boxes. Sure, it's like inviting the band instead of Lady Gaga to the party but you get 90% of it while not resorting to hair pulling or teaching your kids a new word or two. Pretty easy to see who the bad guys are here, Mipmap and Bump.įor a more pleasing visual experience while working leave the Mipmap and Bump home. Load with all Selected: 13.9 (11 Gig Limit) Very jerky movement. Load with all but Mipmap Selected: 10.6 (11 Gig Limit) Stops and starts.

Load with all but Bump Map Selected: 9.2 (11 Gig Limit) Load with all but Mipmap and Bump selected: 7.1 to 7.4 (11 Gig Limit) 6 Gigs while the right side show it maxed out 13.9 Gigs which means you are now offloading to the CPU.īelow are the results with various settings: Toggle off Mipmap, Toggle on Bump map to drive up to 10. The animation is baked in but iClone still has to handle all the moving parts and this project is taxing on the iClone environment. The project file consists of a landscape with snow-laden trees, a well-lit village that will push the emission side of things that is packed with an 80 person walking crowd (Anima) and much smaller idler crowds totaling around 100 moving, dodging, textured characters.

#Free iclone project full

At full load it did slow it down, to the point I turned off Mipmap and Bump map while retaining the Normal Render State so I could see the textures. For this I am using the i9, Twin 2080ti driven Puget System beast that I have yet to bring to its knees. Like mileage on a car, your results will vary somewhat depending on your hardware setup, project, and camera view. That is as technical as we are going to get. So. how much does changing settings lighten the load? Without getting technical, (you notice how I made that sound like I really KNOW the technical side) I used a real-world project with loads of characters, effects and props to push the VIDEO memory limits of what we can and can't do depending on settings used. The left side shows a modest 7.1 of 11 Gigs while the right side kicks it up to 9.2 Gigs with MipMap Selected unless you attach every prop in the scene to a common object(s) you will have to toggle those in selected groups or individually which leads to creative frustration as toggling switches tends to be anything but creative.

We all know about toggling items from shader to wireframe and in between but. This adds a few steps and a generational reduction in render quality. In the past, such a scene was managed by breaking it down into parts and compositing the resulting video renders.