Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HLSL: VSInput semantics have no effect #318

Open
Jordandionduval opened this issue Oct 12, 2023 · 0 comments
Open

HLSL: VSInput semantics have no effect #318

Jordandionduval opened this issue Oct 12, 2023 · 0 comments

Comments

@Jordandionduval
Copy link

While working with the tool, I was trying some stuff with normal maps and I noticed that while inputs can be changed, the semantics have no effects.

For example, if I wanted to define a variable for the position, normal and Texture Coordinates in an HLSL, I would write it like this:

struct VSInput {
	float3 Position 	: POSITION;
	float3 Normal 		: NORMAL;
	float2 TexCoord		: TEXCOORD;
};

Now, if I tried this instead:

struct VSInput {
	float3 Position 	: POSITION;
	float2 TexCoord 	: TEXCOORD;
	float3 Normal		: NORMAL;
};

My Normal variable would contain texture coordinates data and vice versa.

This bug also makes it so you can't access the other inputs provided in the documentation.

I tried with Color on a mesh that had vertex color applied and it didn't work. I can't exactly confirm for Binormal and Tangent (new to HLSL so not sure I understand everything), but compared to results in other applications it didn't look like it worked either.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant