| Deviant Login | Shop | Join deviantART for FREE  |
Take the Tour  |
The Journal Portal
Browse Journals |
Polls |
deviantART [dee·vee·un'nt·ART]
Keep in Touch!
|
Deviousness `ChewedKandi has certainly gone out of her way to keep the vector community on the right path. Always making sure that her talents are infinitely scalable, Sharon has put her bezier curves to excellent use, and firmly anchored herself as an inspirational leader. We're absolutely delighted to bestow the Deviousness Award for June 2013 to `ChewedKandi. Congratulations, Sharon! Read More
|
Sta.sh
Reminds me of the day trip to a local university where they were showing off the wonders of the Electron Microscope to us High Schoolers (way back when Professor Peabody and his sidekick Sherman were still using a Way-Back Machine)
There are of course a lot of variables like resolution, quality, etc. which affect the time-to-render, so you may render 2 completely different flames of equal resolution and quality (density) but get completely different render times. Some plugins/variations use more cpu cycles than others, but plugins especially can be cpu intensive.
I rarely use a quality setting below 2000 (save for animations) but often use 4000 or higher and I also have a tendency to render HD resolutions or higher (for printing purposes).
Another thing that can drastically lengthen render times is the ZOOM function (not the scale setting) in the camera properties tab. I know most people will tell you not to use that function but I often find it necessary to increase it to force apo to render "deeper" in the fringe areas of the fractal where there appears to be a lot of noise. However, by increasing the zoom, you can usually get away with a lower quality setting.