mirror of
https://github.com/Stone-Red-Code/docs-desktop.git
synced 2026-09-04 17:16:03 +02:00
Andy De George
da363692ff
* Reset branch for WPF changes * Convert BMP to PNG; fix link-out-of-scope err * Add snippets for WPF... 6794 files!!!! * Add missing snippets * update file updated between migration * Fix paths to include * update breadcrumb and toc * fix index links * fix index links * fix index links * fix markdown
12 KiB
12 KiB
title, ms.date, helpviewer_keywords, ms.assetid
| title | ms.date | helpviewer_keywords | ms.assetid | |
|---|---|---|---|---|
| Maximize 3D Performance | 03/30/2017 |
|
4bcf949d-d92f-4d8d-8a9b-1e4c61b25bf6 |
Maximize WPF 3D Performance
As you use the [!INCLUDETLA#tla_winclient] to build 3D controls and include 3D scenes in your applications, it is important to consider performance optimization. This topic provides a list of 3D classes and properties that have performance implications for your application, along with recommendations for optimizing performance when you use them.
This topic assumes an advanced understanding of [!INCLUDETLA#tla_winclient] 3D features. The suggestions in this document apply to "rendering tier 2"—roughly defined as hardware that supports pixel shader version 2.0 and vertex shader version 2.0. For more details, see Graphics Rendering Tiers.
Performance Impact: High
| Property | Recommendation |
|---|---|
| xref:System.Windows.Media.Brush | Brush speed (fastest to slowest): xref:System.Windows.Media.SolidColorBrush xref:System.Windows.Media.LinearGradientBrush xref:System.Windows.Media.ImageBrush xref:System.Windows.Media.DrawingBrush (cached) xref:System.Windows.Media.VisualBrush (cached) xref:System.Windows.Media.RadialGradientBrush xref:System.Windows.Media.DrawingBrush (uncached) xref:System.Windows.Media.VisualBrush (uncached) |
| xref:System.Windows.UIElement.ClipToBoundsProperty | Set Viewport3D.ClipToBounds to false whenever you do not need to have [!INCLUDETLA#tla_winclient] explicitly clip the content of a xref:System.Windows.Controls.Viewport3D to the Viewport3D’s rectangle. [!INCLUDETLA#tla_winclient] antialiased clipping can be very slow, and ClipToBounds is enabled (slow) by default on xref:System.Windows.Controls.Viewport3D. |
| xref:System.Windows.UIElement.IsHitTestVisible%2A | Set Viewport3D.IsHitTestVisible to false whenever you do not need [!INCLUDETLA#tla_winclient] to consider the content of a xref:System.Windows.Controls.Viewport3D when performing mouse hit testing. Hit testing 3D content is done in software and can be slow with large meshes. xref:System.Windows.UIElement.IsHitTestVisible%2A is enabled (slow) by default on xref:System.Windows.Controls.Viewport3D. |
| xref:System.Windows.Media.Media3D.GeometryModel3D | Create different models only when they require different Materials or Transforms. Otherwise, try to coalesce many xref:System.Windows.Media.Media3D.GeometryModel3D instances with the same Materials and Transforms into a few larger xref:System.Windows.Media.Media3D.GeometryModel3D and xref:System.Windows.Media.Media3D.MeshGeometry3D instances. |
| xref:System.Windows.Media.Media3D.MeshGeometry3D | Mesh animation—changing the individual vertices of a mesh on a per-frame basis—is not always efficient in [!INCLUDETLA#tla_winclient]. To minimize the performance impact of change notifications when each vertex is modified, detach the mesh from the visual tree before performing per-vertex modification. Once the mesh has been modified, reattach it to the visual tree. Also, try to minimize the size of meshes that will be animated in this way. |
| 3D Antialiasing | To increase rendering speed, disable multisampling on a xref:System.Windows.Controls.Viewport3D by setting the attached property xref:System.Windows.Media.RenderOptions.EdgeMode%2A to Aliased. By default, 3D antialiasing is enabled on Windows with 4 samples per pixel. |
| Text | Live text in a 3D scene (live because it’s in a xref:System.Windows.Media.DrawingBrush or xref:System.Windows.Media.VisualBrush) can be slow. Try to use images of the text instead (via xref:System.Windows.Media.Imaging.RenderTargetBitmap) unless the text will change. |
| xref:System.Windows.Media.TileBrush | If you must use a xref:System.Windows.Media.VisualBrush or a xref:System.Windows.Media.DrawingBrush in a 3D scene because the brush’s content is not static, try caching the brush (setting the attached property xref:System.Windows.Media.RenderOptions.CachingHint%2A to Cache). Set the minimum and maximum scale invalidation thresholds (with the attached properties xref:System.Windows.Media.RenderOptions.CacheInvalidationThresholdMinimum%2A and xref:System.Windows.Media.RenderOptions.CacheInvalidationThresholdMaximum%2A) so that the cached brushes won’t be regenerated too frequently, while still maintaining your desired level of quality. By default, xref:System.Windows.Media.DrawingBrush and xref:System.Windows.Media.VisualBrush are not cached, meaning that every time something painted with the brush has to be re-rendered, the entire content of the brush must first be re-rendered to an intermediate surface. |
| xref:System.Windows.Media.Effects.BitmapEffect | xref:System.Windows.Media.Effects.BitmapEffect forces all affected content to be rendered without hardware acceleration. For best performance, do not use xref:System.Windows.Media.Effects.BitmapEffect. |
Performance Impact: Medium
Performance Impact: Low
| Property | Recommendation |
|---|---|
| xref:System.Windows.Media.Media3D.Transform3DGroup | When you don’t need animation or data binding, instead of using a transform group containing multiple transforms, use a single xref:System.Windows.Media.Media3D.MatrixTransform3D, setting it to be the product of all the transforms that would otherwise exist independently in the transform group. |
| xref:System.Windows.Media.Media3D.Light | Minimize the number of lights in your scene. Too many lights in a scene will force [!INCLUDETLA#tla_winclient] to fall back to software rendering. The limits are roughly 110 xref:System.Windows.Media.Media3D.DirectionalLight objects, 70 xref:System.Windows.Media.Media3D.PointLight objects, or 40 xref:System.Windows.Media.Media3D.SpotLight objects. |
| xref:System.Windows.Media.Media3D.ModelVisual3D | Separate moving objects from static objects by putting them in separate xref:System.Windows.Media.Media3D.ModelVisual3D instances. ModelVisual3D is "heavier" than xref:System.Windows.Media.Media3D.GeometryModel3D because it caches transformed bounds. GeometryModel3D is optimized to be a model; ModelVisual3D is optimized to be a scene node. Use ModelVisual3D to put shared instances of GeometryModel3D into the scene. |
| xref:System.Windows.Media.Media3D.Light | Minimize the number of times you change the number of lights in the scene. Each change of light count forces a shader regeneration and recompilation unless that configuration has existed previously (and thus had its shader cached). |
| Light | Black lights won’t be visible, but they will add to render time; consider omitting them. |
| xref:System.Windows.Media.Media3D.MeshGeometry3D | To minimize the construction time of large collections in [!INCLUDETLA#tla_winclient], such as a MeshGeometry3D’s xref:System.Windows.Media.Media3D.MeshGeometry3D.Positions%2A, xref:System.Windows.Media.Media3D.MeshGeometry3D.Normals%2A, xref:System.Windows.Media.Media3D.MeshGeometry3D.TextureCoordinates%2A, and xref:System.Windows.Media.Media3D.MeshGeometry3D.TriangleIndices%2A, pre-size the collections before value population. If possible, pass the collections’ constructors prepopulated data structures such as arrays or Lists. |