This shows you the differences between two versions of the page.
ko:flamingo:performancetuning [2015/09/14] |
ko:flamingo:performancetuning [2020/08/14] (current) |
||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ====== Flamingo Performance Tips ====== | ||
+ | |||
+ | ====FLAMINGO PERFORMANCE TIPS==== | ||
+ | > **Summary: | ||
+ | |||
+ | ======COMPARISON TESTS====== | ||
+ | See these newsgroup threads for comparisons of various hardware configurations: | ||
+ | |||
+ | **[[http:// | ||
+ | |||
+ | **[[http:// | ||
+ | |||
+ | Add your hardware configuration and render time to the list by posting a reply to each thread. | ||
+ | |||
+ | ======PROCESSOR====== | ||
+ | The speed of the main processor in your computer is the main factor in Flamingo performance. A dual-processor or dual-core computer (when correctly enabled in Windows NT, Windows 2000, Windows XP or Vista) will speed up rendering, probably by 85%, compared to a single processor. | ||
+ | |||
+ | ======POWER SUPPLY UNIT====== | ||
+ | Make sure you have a good PSU, especially in the case of multiple processors/ | ||
+ | |||
+ | ======GRAPHICS CARDS====== | ||
+ | Graphics cards don't speed up Flamingo rendering. | ||
+ | |||
+ | ======RAM MEMORY====== | ||
+ | Rendering with inadequate RAM memory is a major reason for slow Flamingo performance. | ||
+ | |||
+ | To recognize a shortage in RAM, watch disk accesses, or use Task Manager, as below. | ||
+ | |||
+ | Watch your disk drive light while the image is painting on the screen. You should see very little disk activity (unless some other application is working hard). | ||
+ | |||
+ | If the rendering process is causing significant amount of disk accesses (paging, swapping) Flamingo will be slowed down, and more RAM would speed up rendering. | ||
+ | |||
+ | For more precision about RAM on NT, Win2000, XP, or Vista run Task Manager, and on the Performance tab, note the PhysicalMemory/ | ||
+ | |||
+ | If during a rendering CommitCharge/ | ||
+ | |||
+ | For these 32-bit Windows versions, more than 2GB of RAM memory probably isn't cost-effective. | ||
+ | |||
+ | ======OUT OF MEMORY ERRORS====== | ||
+ | Because of Windows (32-bit) limit of 2GB of memory space per process, Windows can't allocate more than 2GB of Virtual Memory to the Rhino/ | ||
+ | |||
+ | For more precision on this, use TaskManager | ||
+ | |||
+ | ======VIRTUAL MEMORY====== | ||
+ | You should allocate more than 2GB of disk space to Windows Virtual Memory. | ||
+ | |||
+ | ======PREPARING THE MODEL IN RHINO: | ||
+ | To save rendering time, or to avoid out-of-memory problems: | ||
+ | |||
+ | Run SelBadObjects on your model, and replace any bad objects. Bad objects usually cause big delays in the render meshing process, and make bad render meshes. | ||
+ | |||
+ | Minimize the number of mesh polygons that Flamingo must handle by the methods below: | ||
+ | |||
+ | Hide or turn off the layers of any objects in your model that don't contribute to the rendering, particularly things that are far away, behind other surfaces, or inside solids. | ||
+ | |||
+ | Having geometry outside the view of the camera can slow Flamingo down, for example ground planes made as surfaces or polygons which are much bigger than the scene being rendered. Keep such geometry as small in extents as is possible for the rendered scene. In the case of ground planes, use the Flamingo Environmemt' | ||
+ | |||
+ | ======MESHING TECHNIQUE====== | ||
+ | Set Rhino > File > Properties > Mesh to Jagged& | ||
+ | |||
+ | An alternative that we recommend is to use the Custom setting at Rhino > File > Properties > Mesh, and setting all the numeric parameters to zero except for " | ||
+ | |||
+ | ======CUSTOM MESHING====== | ||
+ | If a specific rounded object appears faceted in profile/ | ||
+ | |||
+ | If cracks appear between adjacent surfaces, join them into the surfaces into a polysurface; | ||
+ | |||
+ | ===Important=== | ||
+ | See also [[rhino: | ||
+ | |||
+ | ======RENDER MESH ONLY====== | ||
+ | Use the MESH command to mesh the model and then HIDE the [[rhino: | ||
+ | |||
+ | ======FLAMINGO SETTINGS FOR SPEED====== | ||
+ | Leave Rhino > Raytrace > Properties > Flamingo > AntiAliasing at High/4X or lower, unless you demonstrate that you need to devote more rendering time to this. See the Help file. | ||
+ | |||
+ | There may be some special situations where increasing AntiAliasing is required, but usually it is more economical of rendering time to increase resolution ( Rhino > File > Properties > Flamingo > Resolution ) of the rendered image instead, to get the same clarity in the final print. | ||
+ | |||
+ | If you are using soft shadows on any lights, turn this setting off for test renderings. Keep the number of lights using soft shadows as small as you can. Setting the sample number high on soft-shadowed lights is much more expensive in terms of rendering speed than setting the jitter number high. Use the minimum number of samples that makes an acceptable rendering. | ||
+ | |||
+ | ======QUICK TEST RENDERING====== | ||
+ | In Rhino > File > Properties > Flamingo > Resolution choose " | ||
+ | |||
+ | To save time during test rendering, use the RenderWindow or RenderPreviewWindow" | ||
+ | |||
+ | Also use RenderPreview command to make a trial full-resolution rendering on your screen that shows the colors, light and shadows, just one level of reflection, etc. but doesn' | ||
+ | |||
+ | ======TRANSPARENCY AND REFLECTIONS====== | ||
+ | Making objects transparent and reflective greatly increases the rendering time. You can experiment with reducing the number of bounces at Rhino > File > Properties > Flamingo > Bounces. | ||
+ | |||
+ | Turn off anything outside your view that you don't need to affect your rendering, Flamingo takes them into account in reflections if they are turned on in Rhino. | ||
+ | |||
+ | ======PIXEL SIZE OF RENDERING====== | ||
+ | Choose a Custom resolution (pixel size) such as 1024x768 or higher in Rhino > File > Properties > Flamingo > Resolution when rendering to save to an image file for printing your final output. | ||
+ | |||
+ | We recommend that you multiply your desired paper printing size in inches by 85 to get the horizontal and vertical resolution (pixel size) for your image. In many printing situations, pixels-per-paper-inch higher than that level do not significantly improve the result, and so cause unneeded processing time. It depends on the type of paper used, the capabilities of the printer, and how the image is going to be viewed. | ||
+ | |||
+ | Increase your final-rendering resolution above our suggested 85 pixels-per-inch-of-printout, | ||
+ | |||
+ | ======PRINTING YOUR RENDERING====== | ||
+ | For control of your printing, open your rendered image in a program like PhotoShop (Adobe) or PaintShopPro (JASC). | ||
+ | |||
+ | Be mindful that some image printing programs tend to default to printing your image only at 72 dpi scale, but you should modify the printing scale to your needs, without changing the XY (pixel) resolution of the image. | ||
+ | |||
+ | Adobe PhotoShop is tricky to print with, it is locked in on the concept of DPI. You never want to " | ||
+ | |||
+ | Some users may complain that the DPI setting in an image file from Flamingo 1.1 is 72DPI. DPI merely is a suggestion on how big to print the image. Unfortunately we use " | ||
+ | |||
+ | ======PIXEL SIZE FOR EFFICIENCY====== | ||
+ | Experiment to find the minimum pixels-per-inch-of-paper that you need to get adequate printed images. Anything higher is wasted time in rendering. | ||
+ | |||
+ | ======MORE HELP====== | ||
+ | If all this doesn' | ||
+ | |||
+ | [[tech@mcneel.com|Technical Support Email]] tech@mcneel.com | ||
+ | |||
+ | |||
+ | ---- | ||
+ | |||
+ | |||
+ | |||