ComputeShader

Purpose

Set to True to enable GPU side Direct3D chart construction for Direct3D RenderEngine.

Comments

v10.0.0.26 now supports Pe3do PolyMode = SurfacePolygons, PolyMode = Scatter, and PolyMode = Bar. 

Pe3do supports ComputeShader for: 
Contoured Surface
Surface
Surface Wireframe
3d Bar
3d Scatter Line (thin, medium thick)
3d Scatter Point (symbols with max 8 vertices, 24 vertices)
3d Scatter Area (Waterfall)  
4d Surface (example 415)
TriangleData via PolyMode == 3 (example 406)
GraphAnnotTriangleData (example 415) 

Pesgo supports ComputeShader (plus optional Filter2d3d best when working with 1 million points and larger) for:
2d ContourColors

2d ContourLine

2d Line  now support dash and dot of varying thickness
2d Area
2d Point (symbols with max 4 vertices, 6 indices,  and ResourceBitmaps are supported)
2d Bar (Note, best if only one bar per axis)

Note: ComputeShader = True is most beneficial for real-time high performance charting, but it also make general rendering nice too.  Hot Spots octree logic is still built cpu side and is spawned in a separate thread after the gpu side render and usually takes 250-500ms for a large chart.  Important to note that hotspots will be enabled if any of these are true:
AllowDataHotSpots,  CursorPromptTracking, HighlightColor, so, if implementing high speed realtime, make sure none of these are being set. 

Only applicable with RenderEngine = Direct3D. 

For the Pesgo, Pego controls and RenderEngine = Direct3D, charts only support solid, dot and dash styles of varying sizes when ComputeShader is also True.  No Dash-Dot or Dash-Dot-Dot is supported.  When ComputeShader is False, only solid thin, medium, and thick lines are supported for cpu-side Direct3D construction.  See example 115 for Dash and Dotted lines via ComputeShader Direct3D. 

Version 10 adds 2 new demo projects in the GigaPrime3D and GigaPrime2D folders where ProEssentials is installed. 

Existing demos 115, 120, 122, 145, 400, 401, 402, 406, 408, 409, 415, and more have been updated to enable the ComputeShader property.  One should see a signficant performance boost when switching between these examples as compared to v9. 

PeData.ComputeShader members of Pesgo.PeData, Pe3do.PeData