What’s New in Graphics for 4.0 Beta 1

wpf3d — Thu, 25 Jun 2009 03:48:00 GMT

.NET 4.0 Beta 1 was released a few weeks ago and there’s a lot to it that you can read about elsewhere so I thought I would just stick to what’s changed for WPF graphics. These are the biggest things of note:

RenderOptions.ClearTypeHint: If WPF renders text into a potentially transparent surface (e.g. a layered window like a menu or popup) we use grayscale anti-aliasing instead of ClearType because if the transparent surface is blended with another transparent surface, the ClearType will get messed up. Now with ClearTypeHint you can tell us to use ClearType and we’ll trust you that things aren’t transparent.
The BitmapEffect classes are now no-ops. They are still there so your apps will compile but don’t expect them to do anything.
The default RenderOptions.BitmapScalingMode (Unspecified) is now Linear instead of Fant. If you still want Fant, you can re-enable it.
Pixel Shader 2.0 is now required for hardware acceleration. Yes, if your card was Tier 1 but did not have PS 2.0 it is now Tier 0.
The memory leak that was easy to hit with software 3D has been fixed. I already mentioned this.
A common VisualBrush.Visual disconnect crash has been fixed. It’s in the same KB article as the memory leak.

That’s not much but that’s because we’ve been saving things for Beta 2. Stay tuned!

-- Jordan

3.5 SP1 Software 3D Leak Fix Available

wpf3d — Tue, 09 Jun 2009 01:34:00 GMT

In 3.5 SP1 it was really easy to leak memory when doing software 3D rendering involving a VisualBrush or DrawingBrush. We got this complaint many times online and in person. Unfortunately, there is no work around. It’s described in “Issue 2” from this new Knowledge Base article. The fix should also be in 4.0 Beta 1.

-- Jordan

WPF3D Team Blog : 4.0 Beta 1

What’s New in Graphics for 4.0 Beta 1

3.5 SP1 Software 3D Leak Fix Available