Faking 3D with PlaneProjection
Silverlight has no built-in true 3D rendering engine with meshes, lighting, or a z-buffer. Instead, the Projection property on a UIElement can be set to a PlaneProjection, which applies a perspective transform to the element's flat 2D content, letting it appear rotated in 3D space around X, Y, or Z axes even though the underlying visual remains a single rendered plane.
Cricket analogy: A broadcast graphic tilting a flat player photo on an axis to give it a sense of depth on a stats card, without actually modeling the player in 3D, is exactly how Silverlight's PlaneProjection tilts a flat 2D visual to fake perspective rather than rendering true 3D geometry.
PlaneProjection Properties
PlaneProjection exposes RotationX, RotationY, and RotationZ for rotating the plane around each axis, CenterOfRotationX/Y/Z for choosing the pivot point relative to the element's own bounds, and GlobalOffsetX/Y/Z for repositioning the already-projected result within the parent's coordinate space, distinct from LocalOffsetX/Y/Z which shifts the element before rotation is applied.
Cricket analogy: Adjusting a trophy display's tilt angle around its own base versus shifting the whole display case across the room works the same way RotationY paired with CenterOfRotationY pivots an element around its own axis while GlobalOffsetX moves the whole projected result across the scene.
<Grid x:Name="Card" Width="220" Height="320">
<Grid.Projection>
<PlaneProjection x:Name="CardProjection"
CenterOfRotationX="0.5"
RotationY="0" />
</Grid.Projection>
<Border Background="#FF262B36" CornerRadius="8">
<TextBlock Text="Tap to flip" Foreground="White"
HorizontalAlignment="Center" VerticalAlignment="Center" />
</Border>
</Grid>CenterOfRotationX/Y/Z use normalized 0-to-1 coordinates relative to the element's own bounding box by default, where 0.5 means the exact center, so a card flip usually pivots around CenterOfRotationX=0.5 to rotate around its vertical midline rather than an edge.
Combining with Animation for Card Flips
The classic Silverlight card-flip pattern animates PlaneProjection.RotationY from 0 to 180 degrees inside a Storyboard, while a code-behind handler swaps the visibility of a front Grid and a back Grid at the 90-degree midpoint, since a value near 90 degrees renders the plane edge-on and invisible, making it the ideal moment for an imperceptible content swap.
Cricket analogy: A player-of-the-match card flipping from photo to stats on the broadcast graphic mid-innings is built by animating PlaneProjection.RotationY from 0 to 180 degrees inside a Storyboard so the front swaps to the back visual exactly at the 90-degree mark.
Limitations vs True 3D
Because PlaneProjection transforms a single flat plane rather than a mesh, there is no z-buffering between overlapping projected elements, no lighting model, and no way to represent true occluding geometry like the back face of a rotated object; two intersecting rotated planes will simply render in XAML z-order rather than physically correct depth order. For genuine 3D meshes, materials, and cameras, WPF's Viewport3D or a dedicated engine like XNA is required — Silverlight's projection system is intentionally limited to convincing 2.5D UI effects.
Cricket analogy: A paper cutout of a player can be tilted convincingly for a graphic but can never truly turn to show his back the way a real 3D scanned model could, the same way PlaneProjection can rotate a flat plane but can't render true occluding geometry the way a full 3D engine can.
Because PlaneProjection has no z-buffer, stacking multiple independently rotated elements in the same panel can produce visually wrong overlaps at certain rotation angles; if you need physically correct depth sorting between several rotating 3D-like elements, you must manage z-order manually in code rather than relying on the projection system.
- Silverlight has no true 3D engine; PlaneProjection fakes perspective on a flat 2D plane.
- RotationX/Y/Z rotate the element; CenterOfRotationX/Y/Z sets the pivot point.
- GlobalOffsetX/Y/Z repositions the projected result; LocalOffsetX/Y/Z shifts before rotation.
- The classic card-flip pattern swaps front/back content at the 90-degree RotationY midpoint.
- There is no z-buffering, lighting, or true mesh occlusion in PlaneProjection.
- Overlapping rotated elements render in XAML z-order, not physically correct depth order.
- True 3D meshes and cameras require WPF's Viewport3D or a dedicated engine like XNA.
Practice what you learned
1. What does Silverlight's PlaneProjection actually transform?
2. Which property defines the pivot point an element rotates around in PlaneProjection?
3. In a classic card-flip animation, at what RotationY value is content typically swapped between front and back?
4. What key capability does PlaneProjection lack compared to a true 3D engine?
5. Which technology would you use instead of PlaneProjection for true 3D meshes, lighting, and cameras?
Was this page helpful?
You May Also Like
Silverlight Graphics and Animation
How Silverlight's vector shape system, brushes, and Storyboard-driven animations combine to build smooth, scalable interactive UI.
Silverlight Deep Zoom
How Silverlight's Deep Zoom technology uses multi-resolution tile pyramids and the MultiScaleImage control to smoothly pan and zoom into gigapixel-scale imagery.
Related Reading
Related Study Notes in Microsoft Technologies
Browse all study notesWindows 10 / UWP Development Study Notes
.NET · 30 topics
Microsoft TechnologiesWindows Batch Scripting Study Notes
Batch · 30 topics
Microsoft TechnologiesMFC (Microsoft Foundation Classes) Study Notes
C++ · 30 topics
Microsoft TechnologiesXAML Study Notes
.NET · 30 topics
Microsoft TechnologiesWPF (Windows Presentation Foundation) Study Notes
.NET · 30 topics
Microsoft TechnologiesMVVM Design Pattern Study Notes
.NET · 30 topics