Best Practice - Configuration graphic drivers and graphic settings

Partner Channel / Creo Parametric

This guide describes how to configure your graphic-card and debug graphical issues.

Share on Social Networks

Share Link

Use permanent link to share in social media

Share with a friend

Please login to send this presentation by email!

Embed in your website

Select page to start with

10. Optimization of Nvidia GPU’s • Critical menus in the control panel.

11. Optimization of Nvidia GPU’s • System information displays the driver version and e.g. dedicated memory

1. Best Practice Configuration graphic drivers and graphic settings

15. Optimization of AMD GPU’s Performance/Quality – AA settings and more. Custom or application specific.

17. Optimization of integrated Intel GPU’s • 3D section gives the user ability to change preferences. Performance settings are recommended.

12. Optimization of Nvidia GPU’s • If a user notices weak performance in Creo , the quality setting can be switched from quality to performance. Users can also let the application decide.

13. Optimization of Nvidia GPU’s • 3D Settings allows the user to modify the settings either globally or individually. If Creo is slow and shows symptoms of graphic issues, set the preferences to low/disabled. Antialiasing for instance draws a lot of power from the GPU. • Best way to find the perfect setup is to try them out.

16. Optimization of integrated Intel GPU’s • Access the Intel GPU properties section via desktop – RMB • 2 Critical sections: Power and 3D Recommend to set power plan to maximum performance.

18. DirectX Diagnostic tool • The DXDiag tool can be accessed by searching for “ dxdiag ” in Windows. • Possibility to export information to a .txt file. Includes vital information for graphics debugging.

9. Optimization of Nvidia GPU’s • Nvidia GPU’s usually come with a control panel which allows users to configure graphical settings and preferences. • These preferences can make or break a GPU when running software. • In most cases, changing the settings can improve performance, especially on modest GPU’s with low memory. • The Control panel can be accessed on the desktop by clicking RMB and selecting Nvidia control panel.

7. Additional GPU issue resolutions • High DPI (dots per inch) can cause blurriness, which users can interpret as a graphical issue. • Either operate Creo with “Disable display scaling on high DPI settings”. Common on 4k monitors. Or Set the scale below 150%, e.g. 125 - 100%

8. Additional GPU issue resolutions • Geometries disappearing randomly Might be an issue with display settings. • Check the “Geometry display settings” in Creo Parametric. Try different combinations. Also, check that option skip_small_surfaces is not set to yes in the config.pro file.

14. Optimization of AMD GPU’s • AMD GPU’s come with AMD’s native CCC or Catalyst Control Center . • Ability to modify preferences, performance and power options. • Similar to Nvidia's control panel. • Access the control panel via desktop – RMB or Windows search tool.

4. Debug graphical issues? • Apply the following option to your personal config.pro file: graphics win32_gdi • Open Creo and test how the software behaves with a model that has previously shown symptoms of graphical issues. • If the graphical issue is not present, the GPU usually has some kind of general issue, e.g. outdated driver, settings etc. • Download latest drivers, delete the graphics option ( Creo will start with default option OpenGL) and test how the software behaves with the same model. • If the issue is still present, the root cause must be identified.

2. Debug graphical issues? • Prerequisite: ability to add config options to your personal config.pro file. • Software launches for few moments then disappears without any error message, a traceback file is created in the startup directory • Unable to start the software, a traceback file is created in the startup directory • Getting the error message “PTC Creo has stopped working” during startup • Fatal error encountered • These issues are usually caused by graphical issues. Note : All this kind of issues are not always graphic related ...

5. Determining the root cause • Creo Parametric utilizes the following advanced graphics functionalities: FBO - Frame buffer object. Instead of rendering OpenGL data in screen window buffer (buffer which belongs to the OS window which is displayed on screen), everything is rendered in offscreen memory area which are called frame buffers. Once drawing finished, contents from framebuffer is sent to OS window for display on screen. • VBO - Vertex buffer object . All 3D data is stored on the graphics card via VBO. OpenGL gives an id for each VBO that is created on the card. Once created, rendering is very fast because everything is already on the card and all application need to do is to enable a given VBO with it’s ID. • Shader - instead of asking OpenGL to perform lighting calculations, programs are uploaded on the card so that lightning calculations can be performed more efficiently. OIT (Order Independent Transparency), Phone lighting etc. are possible because of shaders .

6. Determining the root cause • Verify that the graphics option is not utilized. This way Creo will utilize OpenGL • Set the following options in your personal config.pro file enable_opengl_fbo no enable_opengl_vbo no enable_opengl_shader no • Open Creo . Check if the graphics issue is present. Since the options are set to “no”, the issue should not be present. • Close Creo and set the fbo option to yes. Test again to see if the issue is present. Repeat the process until you notice the graphical issue (one option at a time to yes). Once you have found the option which causes the graphical issue, send the details of the GPU and System + OpenGL option to our support.

3. Debug graphical issues? • Start with the command win32_gdi. Alternative : start without config.pro/clean .cache2008 folder By default, Creo utilizes OpenGL. OpenGL is a cross - language, cross - platform application programming interface (API) used for rendering 2D and 3D graphics. The API is typically used to interact with a graphics processing unit (GPU), to achieve hardware - accelerated rendering. • By utilizing the win32_gdi option, rendering is transferred directly to the processor (CPU). Graphics Device Interface (GDI) is a Microsoft Windows API. This API is not as advanced as DirectX, Vulkan or OpenGL. Issues with the GPU can be determined by using the win32_gdi option, since the GPU is not utilized . Note : It is not recommended to test this option with large assemblies or complex drawings. Testing should be performed on medium sized assemblies/drawings where graphics issues have been observed.

Views

  • 10 Total Views
  • 6 Website Views
  • 4 Embeded Views

Actions

  • 0 Social Shares
  • 0 Likes
  • 0 Dislikes
  • 0 Comments

Share count

  • 0 Facebook
  • 0 Twitter
  • 0 LinkedIn
  • 0 Google+