wpfshadergenerator Discussions Rss Feed

New Post: Adding Shader Effect File crashes VS2010

NickDarnell — Wed, 12 Jan 2011 23:35:10 GMT

Good to know, thanks. I'll try and figure out what I'm missing for the next version.

New Post: Adding Shader Effect File crashes VS2010

tlmii — Wed, 12 Jan 2011 22:30:16 GMT

Just an FYI on this - I was getting the same error as Joachim with the 1.7.1 install (VS2010, Win7, 64bit). I downloaded the DirectX runtime updater you pointed to here, ran it, then reopened my project and tried it and it worked fine. Since Joachim didn't respond to you, I thought you might be interested in knowing that your solution did work. Hopefully that leads you to being able to fix it in a future release so we can skip that step.

New Post: Adding Shader Effect File crashes VS2010

NickDarnell — Thu, 30 Dec 2010 22:25:07 GMT

Hmm...the 1.7.1 version is suppose to be able to function without the latest DirectX runtime installed. But perhaps I missed something. Download the DirectX runtime updater from Microsoft here, http://www.microsoft.com/downloads/en/details.aspx?FamilyID=2da43d38-db71-4c1b-bc6a-9b6652cd92a3&displaylang=en . That's the only thing I could imagine would cause it to crash, because as soon as you add the templated item, it's going to attempt to compile it. So if for whatever reason the dlls I packaged with the 1.7.1 version are not enough that would cause it to crash for sure.

New Post: Adding Shader Effect File crashes VS2010

joachimb — Thu, 30 Dec 2010 21:03:24 GMT

Hello,

I am very keen to use your VS2010 plugin to create my own Shader Effects, but I have no luck with Version 1.7.1. Every time I create a new project and add the Shader Effect File Template, VS 2010 crashes. I tried it on a 64bit machine and now also on 32bit and it is always the same! Any idea what I could try to get it running?

regards

Joachim

New Post: Pixel Shader .ps file in WPF Shader Effect Generator

NickDarnell — Thu, 23 Dec 2010 16:41:44 GMT

Not that I know of, WPF expects the pixel shader URI to point to an already compiled pixel shader. The WPF ShaderEffect Generator will compile the effect file when you compile your C# code, so that you don't have to run external utilities to recompile it.

New Post: Pixel Shader .ps file in WPF Shader Effect Generator

incandescent — Thu, 23 Dec 2010 10:10:38 GMT

I create a new effect in WPF Shader Effect Generator in Visual Studio 2010.

The File creates a main and a new .cs codebehind file and a compiled .ps file that is embedded in the .fx file.

So Effect1.fx contains the HLSL code for the effect inside a pixel shader called main.

Then the Effect1 ShaderEffect-derived class is contained in the code behind with the Effect1.ps in its PixelShader property. As the Uri to the PixelShader file.

Is it possible to assign the .fx file without compiling it to .ps as a binary pixel shader to the effect.

I have another effect called particle.fx, which I wrote earlier.

I either want to generate the .ps or .vs pixel shader file or vertex shader binary file. This I can generate from the fxc.exe command line tool.

Or does the WPF ShaderEffect Generator automatically generate the pixel code from the HLSL within the compiler.

I.e. Is the fxc compiler accessible from the Project Item Template inside Visual Studio 2010.

Without resorting to the command-line utility available on either the DirectX SDK or obtaining the compiled .ps or .fxo from NVidia's FX Composer 2.5?

New Post: DdxUvDdyUvRegisterIndex support?

rerdavies — Sun, 05 Sep 2010 05:18:17 GMT

Hey, I was about to fire up a new shader for a project I was working on, and I remembered that I had forgotten to say thank you.

Initially, I was very skeptical of the markup in in shader code, and the lack of direct control over the external c# wrapper; but it makes so much sense to do it the way you've done it.

Dropping into shader code for a quick effect used to be a daunting proposition. No longer.

Thanks.

New Post: Documentation Updated

NickDarnell — Thu, 12 Aug 2010 03:56:30 GMT

I've added some example usage and a table with the tags, example values and description information to the Documentation page. Let me know if there's anything else people would like to see on there that I can add.

New Post: Documentation Updated

NickDarnell — Thu, 12 Aug 2010 03:56:30 GMT

New Post: DdxUvDdyUvRegisterIndex support?

NickDarnell — Thu, 12 Aug 2010 03:08:43 GMT

There is not, but I can add that in, no problem. Check back some time over the weekend is when I'll probably get the time to build up a new installer with the change.

New Post: DdxUvDdyUvRegisterIndex support?

rerdavies — Thu, 12 Aug 2010 01:21:43 GMT

I rummaged through sources, and couldn't find anything. Is there any way to bind a shader constant to a DdxUvDdyUvRegisterIndex value? If not, yes please. It's kinda hard to write transition effects without this. (Very nice integration otherwise, by the way).

New Post: Compatibility with VS2010?

NickDarnell — Fri, 11 Jun 2010 06:14:03 GMT

Glad to hear it, I'll look into it for my next version.

New Post: Compatibility with VS2010?

WaltRitscher — Fri, 11 Jun 2010 05:46:38 GMT

I've got Shazzam working by copying d3dx10_xx.dll, D3DCompiler_xx.dll, D3DX9_xx.dll to the install folder. Hooray. You might want to test your app with those files,

I looked at your wrapper, looks like you are calling D3DXCompileShader. JMorrill wrote our PInvoke code and it is calling D3DX10CompileFromMemory in the d3dx10_xx.dll. I've tested on a clean Win7 VM and Shazzam successfully creates WPF and Silverlight shaders.

New Post: Compatibility with VS2010?

NickDarnell — Fri, 11 Jun 2010 05:22:26 GMT

As far as I know yes, but I've not tried packaging a specific version of the runtime's set of dlls with the install and just putting them in the same directory as the tool. Several games tend to do this even though they probably shouldn't. Might work for this usecase as well. Because these shaders are not full fx files, and only support a pixel shader and are realistically just a single HLSL function, you can just do what I've done and write a CLI/C++ wrapper around D3DCompiler_42.dll. I could probably get away with a version of that and the dx runtime dll matching that version number and be set if I dropped those into the same directory as my VS plugin.

New Post: Compatibility with VS2010?

WaltRitscher — Fri, 11 Jun 2010 03:00:22 GMT

For Shazzam we are using the FXC.exe file that ships with the DirectX SDK. FXC is the command line compiler for shaders. I want to remove our dependency on the SDK. We've tried a couple times in the past and ran into the same issues with virgin Windows 7 install.

I'd like to avoid installing the DirectX runtime too. Is it still true that you have to have the runtime installed for your dx9fxutil.dll to work on a fresh Win 7 box?

New Post: How to get dependency properties to be generated?

NickDarnell — Sat, 06 Mar 2010 01:41:43 GMT

I rushed out a new version (1.6) with several fixes to the comment parsing code. It had gotten pretty broken somewhere along the way. I've added a test project to exercise the functionality so that I can prevent these oversights from now on. You should now see your summary tags and register types correctly appearing, along with type overrides.

New Post: How to get dependency properties to be generated?

NickDarnell — Fri, 05 Mar 2010 05:23:41 GMT

Yeah, parser needs more work. If you make them float1 's it will work.

New Post: How to get dependency properties to be generated?

sbussinger — Fri, 05 Mar 2010 01:33:40 GMT

I just sent it to you via the contact page (in two parts because of message size limits). Thanks!

New Post: How to get dependency properties to be generated?

NickDarnell — Fri, 05 Mar 2010 01:07:45 GMT

There shouldn't be a trick. Those should just show up as dependency properties, could be the parser is getting confused and ignoring those constants.

If you don't want to post your shader code here, would you mind sending me the contents of the fx file using the "Contact <user>" link on my profile page, http://www.codeplex.com/site/users/view/NickDarnell

New Post: HLSL metadata markup supported?

NickDarnell — Fri, 05 Mar 2010 01:01:52 GMT

Documentation? I'm not familiar with this concept...

Not yet, it was the next thing I had on my list to do. I did improve the template for a new HLSL file in my 1.5 release which I was hoping would help. All the tags are optional, so not having one wont break anything unless you needed the pixel shader to be compiled with ps_3_0.