Checkout Greg Schechters’s blog! Finally we get hardware accelerated Bitmap effects, and it looks like they’re significantly easier to implement than those nasty slow ugly software based effects! <ugh> even thinking about throwing pixel around in a CLR based language makes me want to wash with carbolic soap.
Anyway enough moaning, I’ll dust off nVidia FX Composer and re-work my little pixel shaders into HLSL. It’s been a while since i’ve been this close to the metal 😉
If you’re feeling adventurous, you can download the .Net 3.5 SP1 beta from HERE!
Also, ScotGu‘s Blog outlining what’s new is well worth a read.
I’ll try to get round to the pixel shader version of my FX asap. Nothing like being on the Bleeding edge 😉
Enjoy!
Dude, I’m all ears if you can get the sample shader in Greg’s blog today to compile! Trying to compile the one at
http://blogs.msdn.com/greg_schechter/archive/2008/05/12/introduction-to-writing-effects.aspx
I get
EXEC : error X3501: ‘main’: entrypoint not found
from fxc!
Put away the carbolic soap, this is omnigeek-meets-designer-meets developer par excellence 😉
I haven’t had a chance to crack out the code yet (doing so in about an hour), but I know what you mean – this is geek-o-licious – I can’t begin to imagine what shader effects we can crank out. I have a couple of ideas but i want to get a nice workflow going for building these things, so i’ll start with my simlple greyscale/saturation/HLS effects..
Keep watching this space. 🙂
Hi Rob.
I don’t know about the post in the 12th, but the following post with the clickonce install is working ok for me.
cheers,
Rob
In re: Rob Burke’s post.
You can find a solution to your problem in this post:
http://blog.pixelingene.com/?p=224
It looks like fxc can’t handle Unicode files (or anything other than ASCII?)
that doesn’t surprise me a great deal. It all feels very command-line-dos-mode-old-stuff when you’re using it.
I dont know, something about the terse output maybe 😉
Are you still alive?!