This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
rhino:5:video:troubleshooting:slowrenderingmode [2022/02/03] maryfugier [Question:] |
rhino:5:video:troubleshooting:slowrenderingmode [2022/02/03] (current) maryfugier [File Analysis] |
||
---|---|---|---|
Line 4: | Line 4: | ||
How can I make Rhino 6 or 7 use my GPU to its full potential? | How can I make Rhino 6 or 7 use my GPU to its full potential? | ||
- | //"I wonder why Rhino for instance cannot draw more Power from my graphics card running on only 35Watts whereas it could potentially draw 150-160Watts. GPU usage is 11%-22% depending on the display mode?"// | + | //"I wonder why Rhino for instance cannot draw more Power from my graphics card running on only 35Watts whereas it could potentially draw 150-160Watts. GPU usage is 11%-22% depending on the display mode? For me, this is what I get:// |
\\ | \\ | ||
- | * Arctic viewport: GPU draws 30 Watts has an GPU utilization of around 10% and gives 6FPS | + | //Arctic viewport: GPU draws 30 Watts has an GPU utilization of around 10% and gives 6FPS// |
- | | + | //Shaded viewport: GPU draws 35 Watt has an GPU utilization of around 22% and gives 30 FPS//" |
===== Answer: ===== | ===== Answer: ===== | ||
Line 17: | Line 17: | ||
You may be expecting that //“If something takes 10 seconds, then if I get a card that’s 10x faster, then it should only take 1 second”.// | You may be expecting that //“If something takes 10 seconds, then if I get a card that’s 10x faster, then it should only take 1 second”.// | ||
+ | \\ | ||
This is only true if 100% of the time Rhino spent on the GPU, which is not the case. | This is only true if 100% of the time Rhino spent on the GPU, which is not the case. | ||
But if only 1% of the time is spent on the GPU, then the result is basically going to be the same…10 seconds. | But if only 1% of the time is spent on the GPU, then the result is basically going to be the same…10 seconds. | ||
Line 26: | Line 27: | ||
Getting us a model is the best way for us to know where the bottlenecks are. | Getting us a model is the best way for us to know where the bottlenecks are. | ||
- | You can submit a model for testing to tech support [[https:// | + | You can submit a model for testing to tech support [[https:// |
+ | \\ | ||
+ | //(Fill out the comment field in the upload with all the details, | ||
For example, if you are getting 3 fps Rendered mode result and a Shaded mode yields ~50 fps, that does seem concerning. | For example, if you are getting 3 fps Rendered mode result and a Shaded mode yields ~50 fps, that does seem concerning. | ||
Line 46: | Line 49: | ||
==== File Analysis ==== | ==== File Analysis ==== | ||
- | + | Here are some recommendations | |
- | If you file appears | + | - Keep the overall number of objects in the scene as low as possible and not excessive |
- | + | - Organize your file in and assign “objects” to “layers”. | |
- | Also keep the overall number of objects in the scene as low as possible and not excessive | + | - Check for bad objects and rebuild them. |
+ | - Avoid excessive usage of blocks | ||
+ | - Purge unused content in your file like materials and textured. | ||
+ | - Reset your Render mode settings to default //(Options -> View -> Display modes -> Rendered. Pick button at bottom to reset to Rhino defaults.)// | ||
+ | - Insert the contents of your file into a new file. //(This may leave some problem with the file behind.)// | ||
+ | But still, the display performance can seem sub-par and painfully slow. | ||
If different “shaded” display modes all seemed to produce similar performance results, **except the Rendered display mode** which can be significantly slower than the other modes. | If different “shaded” display modes all seemed to produce similar performance results, **except the Rendered display mode** which can be significantly slower than the other modes. | ||
Line 75: | Line 83: | ||
However, the path from a Rhino object to colorful pixels on the screen is a very complex and tedious process that does not take place in these other products. | However, the path from a Rhino object to colorful pixels on the screen is a very complex and tedious process that does not take place in these other products. | ||
- | TwinMotion and similar products are only interested in two things; | + | TwinMotion and similar products are only interested in **two things**; |
+ | - Polygons | ||
+ | - The color of said polygons. | ||
+ | Once they have all of the information for all of the polygons, there are all kinds of optimizations that can be made. | ||
==== Testing and Analysis ==== | ==== Testing and Analysis ==== | ||
Line 110: | Line 121: | ||
With that said, we are committed to solving the issues mentioned above over time, and are always trying to make changes/ | With that said, we are committed to solving the issues mentioned above over time, and are always trying to make changes/ | ||
+ | //Question? Please email [[mary@mcneel.com|Mary Ann Fugier]]Mary Ann Fugier, Rhino Technical Support, Seattle WA.// |