Writing custom GPU-based Effects for WPF

re: Writing custom GPU-based Effects for WPF

zzz — Tue, 13 May 2008 05:37:26 GMT

> You need to compile it into the binary bytecode that DirectX natively accepts

has this part of DX gone through security review? I assume the idea is that you can do gpu effects from XBAP so they run without any prompts from the browser, which would be nice. Seems like a good place to poke for holes if that bytecode or something it addresses gets passed to drivers. Is there a risk that old driver bug could allow intrusion through this feature or does DirectX verify everything. Though ASLR/dynamic base probably mitigates a lot of the risk if it's used.

re: Writing custom GPU-based Effects for WPF

Sven Groot — Tue, 13 May 2008 09:06:25 GMT

zzz, in the previous post Greg said that effects currently require full permissions, so you can't use them in an XBAP.

re: Writing custom GPU-based Effects for WPF

joewood — Tue, 13 May 2008 19:49:54 GMT

Very nice. It would be nicer when you have an IL->FX->PS converter so that we can write the effect as a simple delegate.

Any chance of making the FX compiler a separate download?

re: Writing custom GPU-based Effects for WPF

robburke — Wed, 14 May 2008 07:14:02 GMT

Greg, thank you so much for this continuing series.

Along with these articles and sample code snippets, even a very simple but complete (.sln to .ps) "hello pixel shaders in WPF" sample would be very helpful.

Would it be possible for you to zip up the Color Complement example and post it for us to check out?

No need to sort out MSBuild steps or clean up anything, we will be grateful for anything and everything we get :)

WPF 3.5 SP1 (Beta) GPUベースのカスタムエフェクトのサンプル

川西裕幸のブログ — Thu, 15 May 2008 08:16:21 GMT

Greg Schechterのブログに、.NET Framework 3.5 SP1 の GPU ベースのカスタムエフェクトのサンプルが掲載されています。HLSLのコードとWPFへのその組み込み方は

re: Writing custom GPU-based Effects for WPF

Greg Schechter — Thu, 15 May 2008 22:10:59 GMT

joewood asks about an IL->FX->PS converter. Microsoft Research had a research project called Accelerator (you can find their Technical Report at ftp://ftp.research.microsoft.com/pub/tr/TR-2005-184.pdf) that produced something like what you describe. However, for WPF shaders, it's not really a goal to come up with a "managed language" way of implementing shaders that run massively parallel on the GPU. We feel that the sweetspot is having a top-notch mechanism for integrating shaders (as we're doing with the features I describe in this series). Further, ultimately the best way to write shaders is not going to be through some textual language at all (whether HLSL or C#), but rather through visual tools, which don't really care (or at least not nearly as much) about what the underlying language they need to emit is.

robburke asks about getting a sample posted. You can now find one (along with a ClickOnce app) in the next post in this series.

re: Writing custom GPU-based Effects for WPF

SysRq2000 — Sun, 18 May 2008 17:44:39 GMT

Greg, have you guys looked at making the fx->ps transition easier by extending VS with something similar to the XNA Game Studio content pipeline? The pipeline in XNA solves the problem and you simply have to include the fx file in the project and then just let the content pipeline take care of the fx compilation into a ps file.

WPF 3.5 SP1 (Beta) GPUベースのカスタムエフェクトはどんな Visual にも適用できる

川西裕幸のブログ — Mon, 19 May 2008 11:10:08 GMT

先週書いた.NET Framework 3.5 SP1 の GPU ベースのカスタムエフェクトのサンプルをちょっといじるだけで、ModelVisual3DにもMediaElementにも同じエフェクトが適用できます。

re: Writing custom GPU-based Effects for WPF

Greg Schechter — Wed, 21 May 2008 19:07:04 GMT

SysRq2000 asks about automating the compilation of HLSL to pixel shader bytecode. Yes, we're working on a VS build task that will help here.

re: Writing custom GPU-based Effects for WPF

robburke — Wed, 21 May 2008 19:29:10 GMT

Greg, one question I had is what you would recommend as a good practice for detecting and potentially disabling shader effects on a low-spec machine? Using System.Windows.Media.RenderCapability.IsPixelShaderVersionSupported I can detect if the shaders are supported - but what to do if they aren't, and the effect isn't essential? Setting the Effect to null can cause troubles if you have Storyboards that animate the Properties of the Effect. Is there any chance that Effects could contain an IsEnabled DP?

re: Writing custom GPU-based Effects for WPF

Greg Schechter — Fri, 23 May 2008 01:37:39 GMT

robburke: This is a good scenario, and you're right, our primary expectation is that one would "turn an Effect off" by setting it to null, but yes, that can mess with storyboards.

I think for this release, you're going to need to either:

a) keep your effect modifying animations in a separate storyboard you either use or don't depending on the presence of the effect.

b) runtime remove those timelines from a storyboard.

c) maintain two storyboards, one with, one without, and instantiate the right one.

I know that none of those are the best answers here. I'm going to put this in as an potential addition for the next version.

Greg

GPU based effects

Lester's WPF blog — Mon, 02 Jun 2008 19:26:41 GMT

A hot new feature in 3.5 SP1 is GPU based effect. Greg Schechter has has a series of posts on this topic.

A Series on GPU-based Effects for WPF

Greg Schechter's Blog — Tue, 12 Aug 2008 07:52:11 GMT

GPU-based Effects are a hot new feature in WPF for .NET 3.5 SP1.  I'm going to be blogging a series

Working with Effects and HLSL

The Sneaky Peek — Tue, 09 Sep 2008 22:58:30 GMT

So I hit the trail of trying to understand all that I can about HLSL and Effects in general, and to be honest, the whole subject is a bit like reading a book that you can never get past the first 10 pages without falling asleep… it just goes on and on

流水账 5.5 WPF Effect

Tue, 05 May 2009 10:03:09 GMT

BitmapEffect已经过时了。UIElement.BitmapEffectpropertyisobsolete没办法，BitmapEffect的效率过于低下，有时还有莫名其妙的界面闪...