Mixing
Why does the 'f' suffix when defining floats sometimes cause GLSL compiler errors?
I've been making my own OpenGL game for fun to learn C++ (coming from Java). I was testing it on another computer I have so I could test it's performance on a weaker system, and I found that there was a shader compiler error.
It seems that on my computer running with Intel Integrated Graphics, the following line causes a syntax error.
float ambientLight = 2f;
The error is just 'f' syntax error, so naturally I removed the f, and it now runs fine on both machines. I'm guessing this is some sort of driver error, but I'm not really sure why there is this discrepancy and whether or not this means I should stop putting fs in my float declarations in glsl all together.
opengl glsl
asked Jan 2 at 3:16
RobertRobert
132
add a comment |
I've been making my own OpenGL game for fun to learn C++ (coming from Java). I was testing it on another computer I have so I could test it's performance on a weaker system, and I found that there was a shader compiler error.
It seems that on my computer running with Intel Integrated Graphics, the following line causes a syntax error.
float ambientLight = 2f;
The error is just 'f' syntax error, so naturally I removed the f, and it now runs fine on both machines. I'm guessing this is some sort of driver error, but I'm not really sure why there is this discrepancy and whether or not this means I should stop putting fs in my float declarations in glsl all together.
opengl glsl
asked Jan 2 at 3:16
RobertRobert
132
What#versionare you targeting?
– genpfault
Jan 2 at 14:31
@genpfault Commenter below was correct to say that I don't have a #version :) So I suppose it was defaulting to 110.
– Robert
Jan 2 at 18:24
add a comment |
I've been making my own OpenGL game for fun to learn C++ (coming from Java). I was testing it on another computer I have so I could test it's performance on a weaker system, and I found that there was a shader compiler error.
It seems that on my computer running with Intel Integrated Graphics, the following line causes a syntax error.
float ambientLight = 2f;
The error is just 'f' syntax error, so naturally I removed the f, and it now runs fine on both machines. I'm guessing this is some sort of driver error, but I'm not really sure why there is this discrepancy and whether or not this means I should stop putting fs in my float declarations in glsl all together.
opengl glsl
asked Jan 2 at 3:16
RobertRobert
132
I've been making my own OpenGL game for fun to learn C++ (coming from Java). I was testing it on another computer I have so I could test it's performance on a weaker system, and I found that there was a shader compiler error.
It seems that on my computer running with Intel Integrated Graphics, the following line causes a syntax error.
float ambientLight = 2f;
The error is just 'f' syntax error, so naturally I removed the f, and it now runs fine on both machines. I'm guessing this is some sort of driver error, but I'm not really sure why there is this discrepancy and whether or not this means I should stop putting fs in my float declarations in glsl all together.
opengl glsl
opengl glsl
asked Jan 2 at 3:16
RobertRobert
132
asked Jan 2 at 3:16
RobertRobert
132
asked Jan 2 at 3:16
RobertRobert
132
asked Jan 2 at 3:16
RobertRobert
132
asked Jan 2 at 3:16
RobertRobert
132
132
What#versionare you targeting?
– genpfault
Jan 2 at 14:31
@genpfault Commenter below was correct to say that I don't have a #version :) So I suppose it was defaulting to 110.
– Robert
Jan 2 at 18:24
add a comment |
What#versionare you targeting?
– genpfault
Jan 2 at 14:31
@genpfault Commenter below was correct to say that I don't have a #version :) So I suppose it was defaulting to 110.
– Robert
Jan 2 at 18:24
What
#version are you targeting?– genpfault
Jan 2 at 14:31
What
#version are you targeting?– genpfault
Jan 2 at 14:31
@genpfault Commenter below was correct to say that I don't have a #version :) So I suppose it was defaulting to 110.
– Robert
Jan 2 at 18:24
@genpfault Commenter below was correct to say that I don't have a #version :) So I suppose it was defaulting to 110.
– Robert
Jan 2 at 18:24
add a comment |
1 Answer
1
active
oldest
votes
For reasons that continue to elude me, the GLSL specification requires that floating-point literal suffixes (f, lf) only appear after unambiguously floating-point values. 2 is an integer literal, not a floating-point literal, so it cannot be adorned with f. A literal is not a floating-point literal unless it clearly has a decimal or exponent (1e4, for example) somewhere in it.
So you have to write it as 2.f.
answered Jan 2 at 14:28
Nicol BolasNicol Bolas
290k34481655
add a comment |
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%2f54000835%2fwhy-does-the-f-suffix-when-defining-floats-sometimes-cause-glsl-compiler-error%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
For reasons that continue to elude me, the GLSL specification requires that floating-point literal suffixes (f, lf) only appear after unambiguously floating-point values. 2 is an integer literal, not a floating-point literal, so it cannot be adorned with f. A literal is not a floating-point literal unless it clearly has a decimal or exponent (1e4, for example) somewhere in it.
So you have to write it as 2.f.
answered Jan 2 at 14:28
Nicol BolasNicol Bolas
290k34481655
add a comment |
For reasons that continue to elude me, the GLSL specification requires that floating-point literal suffixes (f, lf) only appear after unambiguously floating-point values. 2 is an integer literal, not a floating-point literal, so it cannot be adorned with f. A literal is not a floating-point literal unless it clearly has a decimal or exponent (1e4, for example) somewhere in it.
So you have to write it as 2.f.
answered Jan 2 at 14:28
Nicol BolasNicol Bolas
290k34481655
add a comment |
For reasons that continue to elude me, the GLSL specification requires that floating-point literal suffixes (f, lf) only appear after unambiguously floating-point values. 2 is an integer literal, not a floating-point literal, so it cannot be adorned with f. A literal is not a floating-point literal unless it clearly has a decimal or exponent (1e4, for example) somewhere in it.
So you have to write it as 2.f.
answered Jan 2 at 14:28
Nicol BolasNicol Bolas
290k34481655
For reasons that continue to elude me, the GLSL specification requires that floating-point literal suffixes (f, lf) only appear after unambiguously floating-point values. 2 is an integer literal, not a floating-point literal, so it cannot be adorned with f. A literal is not a floating-point literal unless it clearly has a decimal or exponent (1e4, for example) somewhere in it.
So you have to write it as 2.f.
answered Jan 2 at 14:28
Nicol BolasNicol Bolas
290k34481655
edited Jan 2 at 19:41
answered Jan 2 at 14:28
Nicol BolasNicol Bolas
290k34481655
answered Jan 2 at 14:28
Nicol BolasNicol Bolas
290k34481655
answered Jan 2 at 14:28
Nicol BolasNicol Bolas
290k34481655
290k34481655
add a comment |
add a comment |
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%2f54000835%2fwhy-does-the-f-suffix-when-defining-floats-sometimes-cause-glsl-compiler-error%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
What
#versionare you targeting?– genpfault
Jan 2 at 14:31
@genpfault Commenter below was correct to say that I don't have a #version :) So I suppose it was defaulting to 110.
– Robert
Jan 2 at 18:24