Jump to content

  • Log In with Google      Sign In   
  • Create Account

FREE SOFTWARE GIVEAWAY

We have 4 x Pro Licences (valued at $59 each) for 2d modular animation software Spriter to give away in this Thursday's GDNet Direct email newsletter.


Read more in this forum topic or make sure you're signed up (from the right-hand sidebar on the homepage) and read Thursday's newsletter to get in the running!


ingramb

Member Since 16 Apr 2009
Offline Last Active Dec 11 2014 02:57 PM

Posts I've Made

In Topic: Multipass rendering with depth compare EQUAL

09 November 2014 - 02:29 PM

No fixed function.

 

I ended up just using LEQUAL for the main pass, and running alpha test again, at least on PC D3D9.  I'd still be curious if anyone has any ideas.


In Topic: Multipass rendering with depth compare EQUAL

05 November 2014 - 06:04 PM

Thanks for the replies.

 

I'm targeting D3D9 on the PC, so sadly no precise keyword.  No trickery with changing primitive types.  I've looked at the D3D bytecode, and it appears to match, but I could be missing something.

 

I'll keep looking.


In Topic: Beginning D3D11, missing pixel shader

09 November 2013 - 11:01 PM

Problem was setting 0 as the sample mask for OMSetBlendState.  It's always the little things.  Thanks for suggestions everyone.


In Topic: Beginning D3D11, missing pixel shader

09 November 2013 - 04:33 PM

 

 

do you pass the debug flag when creating your shaders?

Yes.

 

 

And are you getting any output from the pixel shader, despite not being able to see the stage.

Not as far as I can tell.  When I check the pixel history, I only see the ClearRenderTarget.

 

 

The 'Graphics Pipeline Stages' tab doesn't have pixel shader stage. It only shows 'Input Assembler->Vertex Shader->Output Merger'.

When I run D3D sample apps through the graphics debugger, I do see pixel shader stage.

 

 

To make sure your PS is set correctly, in the 'Graphics Event List' go to your draw call and click on the ID3D11DeviceContext. It will open a new window with the entire state, you can check that your PS is set.

The pixel shader is set in the device context.  All the states in the device context look correct, as far as I can tell.

 

 

If you want to debug a specific pixel, right click anywhere on the image, select 'Pixel History', then click on a pixel. This will open a new window where you can see the graphics history and debug the vertex and pixel shaders.

When I check pixel history, I don't see my pixel shader anywhere.  Only the framebuffer clear.

 

Anyway, thanks for the suggestions so far.


In Topic: Lighting shader, high level optimizations?

23 July 2013 - 05:32 PM

Rather than store your light values in array-of-structures form, store things as a structure-of-arrays.

 

This explains what I'm talking about very nicely: http://zeuxcg.org/2007/10/28/my-own-lighting-shader-with-blackjack-and-hookers/


PARTNERS