Changes to Pixel Shader aren't being Saved
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
I'm working on a DirectX program (I'm not using any wrappers). I'm trying to make a Pixel Shader. I made some changes to the Pixel Shader, it is not reflecting in the code when it is running.
This is the code I wrote for the Pixel Shader. (It is just returning the colour to white).
float4 main(PS_INPUT input) : SV_Target
{
//float4 baseTexture = txDiffuse.Sample(samLinear, input.Tex);
return float4(1.0f, 1.0f, 1.0f, 1);
}
Before I changed my code to this, my pixel shader was returning the colour from the vertex.
When I'm running my graphics debugger I see this pixel shader running. (The old code)
The graphics debugger running
I'm making my HLSL into a .csh.
Also, I'm making my PIxel Shader like this
hr = m_Device->CreatePixelShader(PS_Mesh, sizeof(PS_Mesh), nullptr, &m_PixelShader[PIXEL_SHADER_TYPE::ENUM::PS_MESH].p);
Why are the changes not reflecting? I have tried to give all the information. Please ask any other questions you need to. I have been stuck on this problem for quite some time.
Build settings for the project..
directx shader directx-11 pixel-shader
asked Nov 22 '18 at 23:10
Siddharth JainSiddharth Jain
65
add a comment |
I'm working on a DirectX program (I'm not using any wrappers). I'm trying to make a Pixel Shader. I made some changes to the Pixel Shader, it is not reflecting in the code when it is running.
This is the code I wrote for the Pixel Shader. (It is just returning the colour to white).
float4 main(PS_INPUT input) : SV_Target
{
//float4 baseTexture = txDiffuse.Sample(samLinear, input.Tex);
return float4(1.0f, 1.0f, 1.0f, 1);
}
Before I changed my code to this, my pixel shader was returning the colour from the vertex.
When I'm running my graphics debugger I see this pixel shader running. (The old code)
The graphics debugger running
I'm making my HLSL into a .csh.
Also, I'm making my PIxel Shader like this
hr = m_Device->CreatePixelShader(PS_Mesh, sizeof(PS_Mesh), nullptr, &m_PixelShader[PIXEL_SHADER_TYPE::ENUM::PS_MESH].p);
Why are the changes not reflecting? I have tried to give all the information. Please ask any other questions you need to. I have been stuck on this problem for quite some time.
Build settings for the project..
directx shader directx-11 pixel-shader
asked Nov 22 '18 at 23:10
Siddharth JainSiddharth Jain
65
It depends on how you have your build set up, but in this case you'd typically need to make a chain of dependencies so that updating our source HLSL file results in building the.cshwhich results in rebuilding the.cppfile that consume it.
– Chuck Walbourn
Nov 24 '18 at 5:39
I have edited the post to add the setup of the build. I'm sorry I still didn't understand how to solve this issue. Maybe the settings will make it clear.
– Siddharth Jain
Nov 25 '18 at 10:58
Okay, I fixed this issue. I was making my shaders in the C drive and not to a relative path and that is why it always had the old shader. I fixed the issue of where I was outputting the .csh and then included the correct file too.
– Siddharth Jain
Nov 27 '18 at 17:21
add a comment |
I'm working on a DirectX program (I'm not using any wrappers). I'm trying to make a Pixel Shader. I made some changes to the Pixel Shader, it is not reflecting in the code when it is running.
This is the code I wrote for the Pixel Shader. (It is just returning the colour to white).
float4 main(PS_INPUT input) : SV_Target
{
//float4 baseTexture = txDiffuse.Sample(samLinear, input.Tex);
return float4(1.0f, 1.0f, 1.0f, 1);
}
Before I changed my code to this, my pixel shader was returning the colour from the vertex.
When I'm running my graphics debugger I see this pixel shader running. (The old code)
The graphics debugger running
I'm making my HLSL into a .csh.
Also, I'm making my PIxel Shader like this
hr = m_Device->CreatePixelShader(PS_Mesh, sizeof(PS_Mesh), nullptr, &m_PixelShader[PIXEL_SHADER_TYPE::ENUM::PS_MESH].p);
Why are the changes not reflecting? I have tried to give all the information. Please ask any other questions you need to. I have been stuck on this problem for quite some time.
Build settings for the project..
directx shader directx-11 pixel-shader
asked Nov 22 '18 at 23:10
Siddharth JainSiddharth Jain
65
I'm working on a DirectX program (I'm not using any wrappers). I'm trying to make a Pixel Shader. I made some changes to the Pixel Shader, it is not reflecting in the code when it is running.
This is the code I wrote for the Pixel Shader. (It is just returning the colour to white).
float4 main(PS_INPUT input) : SV_Target
{
//float4 baseTexture = txDiffuse.Sample(samLinear, input.Tex);
return float4(1.0f, 1.0f, 1.0f, 1);
}
Before I changed my code to this, my pixel shader was returning the colour from the vertex.
When I'm running my graphics debugger I see this pixel shader running. (The old code)
The graphics debugger running
I'm making my HLSL into a .csh.
Also, I'm making my PIxel Shader like this
hr = m_Device->CreatePixelShader(PS_Mesh, sizeof(PS_Mesh), nullptr, &m_PixelShader[PIXEL_SHADER_TYPE::ENUM::PS_MESH].p);
Why are the changes not reflecting? I have tried to give all the information. Please ask any other questions you need to. I have been stuck on this problem for quite some time.
Build settings for the project..
directx shader directx-11 pixel-shader
directx shader directx-11 pixel-shader
asked Nov 22 '18 at 23:10
Siddharth JainSiddharth Jain
65
asked Nov 22 '18 at 23:10
Siddharth JainSiddharth Jain
65
edited Nov 25 '18 at 11:03
Siddharth Jain
asked Nov 22 '18 at 23:10
Siddharth JainSiddharth Jain
65
asked Nov 22 '18 at 23:10
Siddharth JainSiddharth Jain
65
asked Nov 22 '18 at 23:10
Siddharth JainSiddharth Jain
65
65
It depends on how you have your build set up, but in this case you'd typically need to make a chain of dependencies so that updating our source HLSL file results in building the.cshwhich results in rebuilding the.cppfile that consume it.
– Chuck Walbourn
Nov 24 '18 at 5:39
I have edited the post to add the setup of the build. I'm sorry I still didn't understand how to solve this issue. Maybe the settings will make it clear.
– Siddharth Jain
Nov 25 '18 at 10:58
Okay, I fixed this issue. I was making my shaders in the C drive and not to a relative path and that is why it always had the old shader. I fixed the issue of where I was outputting the .csh and then included the correct file too.
– Siddharth Jain
Nov 27 '18 at 17:21
add a comment |
It depends on how you have your build set up, but in this case you'd typically need to make a chain of dependencies so that updating our source HLSL file results in building the.cshwhich results in rebuilding the.cppfile that consume it.
– Chuck Walbourn
Nov 24 '18 at 5:39
I have edited the post to add the setup of the build. I'm sorry I still didn't understand how to solve this issue. Maybe the settings will make it clear.
– Siddharth Jain
Nov 25 '18 at 10:58
Okay, I fixed this issue. I was making my shaders in the C drive and not to a relative path and that is why it always had the old shader. I fixed the issue of where I was outputting the .csh and then included the correct file too.
– Siddharth Jain
Nov 27 '18 at 17:21
It depends on how you have your build set up, but in this case you'd typically need to make a chain of dependencies so that updating our source HLSL file results in building the
.csh which results in rebuilding the .cpp file that consume it.– Chuck Walbourn
Nov 24 '18 at 5:39
It depends on how you have your build set up, but in this case you'd typically need to make a chain of dependencies so that updating our source HLSL file results in building the
.csh which results in rebuilding the .cpp file that consume it.– Chuck Walbourn
Nov 24 '18 at 5:39
I have edited the post to add the setup of the build. I'm sorry I still didn't understand how to solve this issue. Maybe the settings will make it clear.
– Siddharth Jain
Nov 25 '18 at 10:58
I have edited the post to add the setup of the build. I'm sorry I still didn't understand how to solve this issue. Maybe the settings will make it clear.
– Siddharth Jain
Nov 25 '18 at 10:58
Okay, I fixed this issue. I was making my shaders in the C drive and not to a relative path and that is why it always had the old shader. I fixed the issue of where I was outputting the .csh and then included the correct file too.
– Siddharth Jain
Nov 27 '18 at 17:21
Okay, I fixed this issue. I was making my shaders in the C drive and not to a relative path and that is why it always had the old shader. I fixed the issue of where I was outputting the .csh and then included the correct file too.
– Siddharth Jain
Nov 27 '18 at 17:21
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53438945%2fchanges-to-pixel-shader-arent-being-saved%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53438945%2fchanges-to-pixel-shader-arent-being-saved%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
It depends on how you have your build set up, but in this case you'd typically need to make a chain of dependencies so that updating our source HLSL file results in building the
.cshwhich results in rebuilding the.cppfile that consume it.– Chuck Walbourn
Nov 24 '18 at 5:39
I have edited the post to add the setup of the build. I'm sorry I still didn't understand how to solve this issue. Maybe the settings will make it clear.
– Siddharth Jain
Nov 25 '18 at 10:58
Okay, I fixed this issue. I was making my shaders in the C drive and not to a relative path and that is why it always had the old shader. I fixed the issue of where I was outputting the .csh and then included the correct file too.
– Siddharth Jain
Nov 27 '18 at 17:21