• Announcements

    • khawk

      Download the Game Design and Indie Game Marketing Freebook   07/19/17

      GameDev.net and CRC Press have teamed up to bring a free ebook of content curated from top titles published by CRC Press. The freebook, Practices of Game Design & Indie Game Marketing, includes chapters from The Art of Game Design: A Book of Lenses, A Practical Guide to Indie Game Marketing, and An Architectural Approach to Level Design. The GameDev.net FreeBook is relevant to game designers, developers, and those interested in learning more about the challenges in game development. We know game development can be a tough discipline and business, so we picked several chapters from CRC Press titles that we thought would be of interest to you, the GameDev.net audience, in your journey to design, develop, and market your next game. The free ebook is available through CRC Press by clicking here. The Curated Books The Art of Game Design: A Book of Lenses, Second Edition, by Jesse Schell Presents 100+ sets of questions, or different lenses, for viewing a game’s design, encompassing diverse fields such as psychology, architecture, music, film, software engineering, theme park design, mathematics, anthropology, and more. Written by one of the world's top game designers, this book describes the deepest and most fundamental principles of game design, demonstrating how tactics used in board, card, and athletic games also work in video games. It provides practical instruction on creating world-class games that will be played again and again. View it here. A Practical Guide to Indie Game Marketing, by Joel Dreskin Marketing is an essential but too frequently overlooked or minimized component of the release plan for indie games. A Practical Guide to Indie Game Marketing provides you with the tools needed to build visibility and sell your indie games. With special focus on those developers with small budgets and limited staff and resources, this book is packed with tangible recommendations and techniques that you can put to use immediately. As a seasoned professional of the indie game arena, author Joel Dreskin gives you insight into practical, real-world experiences of marketing numerous successful games and also provides stories of the failures. View it here. An Architectural Approach to Level Design This is one of the first books to integrate architectural and spatial design theory with the field of level design. The book presents architectural techniques and theories for level designers to use in their own work. It connects architecture and level design in different ways that address the practical elements of how designers construct space and the experiential elements of how and why humans interact with this space. Throughout the text, readers learn skills for spatial layout, evoking emotion through gamespaces, and creating better levels through architectural theory. View it here. Learn more and download the ebook by clicking here. Did you know? GameDev.net and CRC Press also recently teamed up to bring GDNet+ Members up to a 20% discount on all CRC Press books. Learn more about this and other benefits here.
Sign in to follow this  
Followers 0
experiment

Help with hlsl

8 posts in this topic

This has been driving me mad for a while now...

 

Asuming the vertex data is created and fed correctly, shouldn't this HLSL code show my object in uniform white color?

struct VS_INPUT
{
	float3 posL	: POSITION;
	float3 normalL	: NORMAL;
};

struct VS_OUTPUT
{
	float4 posH	: SV_POSITION;
	float3 posW	: POSITION;
	float3 normalW	: NORMAL;
};

//--------------------------------------------------------------------------------------
// Vertex Shader
//--------------------------------------------------------------------------------------

VS_OUTPUT VS(VS_INPUT vsIn)
{
	VS_OUTPUT psIn;

	float4x4 mWVP = mWorld * mView * mProjection;

	psIn.posH = mul(float4(vsIn.posL, 1.0f), mWVP);

	psIn.posW = mul(float4(vsIn.posL, 1.0f), mWorld);
	psIn.normalW = mul(float4(vsIn.normalL, 1.0f), mWorld);

	return psIn;
}


//--------------------------------------------------------------------------------------
// Pixel Shader
//--------------------------------------------------------------------------------------
float4 PS(VS_OUTPUT psIn) : SV_Target
{
	return float4(1.0f, 1.0f, 1.0f, 1.0f);
}

Instead I'm just seeing the clear color background.

 

0

Share this post


Link to post
Share on other sites

Yes it should. So your vertex data or your matrices must be incorrect, putting your object outside the view frustum. Or,

- your vertices have the wrong winding order (turn culling off to see if this is the problem)

- you're trying to draw try behind another object (or the depth buffer was cleared to the wrong value) and the depth comparison is failing (turn the depth buffer off to see if this is the problem).

 

Also, the w component of your normal should be 0, not 1.

 

 

(NOTE: my answer is incorrect... you need to use the mul intrinsic for matrix multiplication, as unbird points out below)

Edited by phil_t
1

Share this post


Link to post
Share on other sites

Not sure about the order of multiplication for your matrices, but thats one to double check. Also, while we are on the subject, I would recommend calculating the model-view-projection matrix CPU side instead of having to do it for each vertex in the vertex shader...

1

Share this post


Link to post
Share on other sites

Yes it should. So your vertex data or your matrices must be incorrect, putting your object outside the view frustum. Or,

- your vertices have the wrong winding order (turn culling off to see if this is the problem)

- you're trying to draw try behind another object (or the depth buffer was cleared to the wrong value) and the depth comparison is failing (turn the depth buffer off to see if this is the problem).

 

Also, the w component of your normal should be 0, not 1.

 

 

Not sure about the order of multiplication for your matrices, but thats one to double check. Also, while we are on the subject, I would recommend calculating the model-view-projection matrix CPU side instead of having to do it for each vertex in the vertex shader...

 

Okay. Here is the thing. I had a working example of a simple cube model with color shading. This problem started happening while I was trying to implement lights, and I have no clue what I did to make it not show up at all. I know I changed the Vertex structure, input layout, fixed vertex data to match (basically replacing color with normals) added some shader variables

 

Okay. I figured out while I was typing this response. I checked everything 10 times, I just knew it would be something ridiculous like it always turns out to be. the "eye" coordinates were inside the cube.

 

Interestingly enough there is something odd about having that matrix multiplication in the shader code. It doesn't work (aside from being very inefficient). Tried changing the order combination, nothing. Works ok having calculations on cpu and passing WVP though.

 

Whatever it is, thanks for your help!

0

Share this post


Link to post
Share on other sites

I could be wrong and it could be as you intend it to be but, it looks like your normal calculation will be wrong, you might want to change it to:

float4(vsIn.normalL, 0.0f)

note: the 1.0f changed to a 0.0f

 

This stop the matrix multiplication translating the vsIn.normalL value as it would a position value and only rotates as it should for a direction value.

1

Share this post


Link to post
Share on other sites

I tried changing that. The results look the same. It depends what you do with it probably. To be completely honest I don't know if there is a difference in vec3 * mat vs. vec4 * mat as far as first 3 members are concerned. (I suck at maths)

 

If what you say is true then.. the more you know.

Edited by Sanjin B.
0

Share this post


Link to post
Share on other sites

Interestingly enough there is something odd about having that matrix multiplication in the shader code. It doesn't work (aside from being very inefficient)


It doesn't work because * is a component-wise multiplication (aka modulate), not a matrix multiplication. For the latter you need to use mul(), just like with the vector-matrix multiply later. Edited by unbird
2

Share this post


Link to post
Share on other sites

As for the side topic here, when using a 4x4 matrix, always use a vector 4, even if the compiler/language allows the combination of 3/4 sizes it will help avoid confusing. You might want to do some reading on the construction of world matrices (scaling, rotation, and translation of the mesh) so that you understand why we use a 1.0/0.0 in the w component. This free course might be quite beneficial for you: https://www.udacity.com/course/cs291

 

Good Luck

1

Share this post


Link to post
Share on other sites

 

Interestingly enough there is something odd about having that matrix multiplication in the shader code. It doesn't work (aside from being very inefficient)


It doesn't work because * is a component-wise multiplication (aka modulate), not a matrix multiplication. For the latter you need to use mul(), just like with the vector-matrix multiply later.

 

and take a look at this http://msdn.microsoft.com/en-us/library/windows/desktop/dd607354(v=vs.85).aspx

0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0