```glsl in vec3 myInputtedColor out vec3 myOutputtedColor void main() { myOutputtedColor = myIn

in vec3 myInputtedColor

out vec3 myOutputtedColor

void main() {
  myOutputtedColor = myInputtedColor
}

in vec3 myInputtedColor

out vec3 myOutputtedColor

void main() {
  myOutputtedColor = myInputtedColor
}

in vec3 myInputtedColor

out vec3 myOutputtedColor

void main() {
  myOutputtedColor = myInputtedColor
}

in vec3 myInputtedColor

out vec3 myOutputtedColor

void main() {
  myOutputtedColor = myInputtedColor
}

AAqua the name doesn't matter either, as long as its an `out` you could name it `out m...

forniteOP•4/3/23, 12:25 PM

ohh

forniteOP•4/3/23, 12:25 PM

but how does it know that variable is for the color and not something else

Ffornite ```glsl in vec3 myInputtedColor out vec3 myOutputtedColor void main() { myO...

forniteOP•4/3/23, 12:25 PM

would this be how i would need to externally control a color in the shader?

Ffornite ```glsl in vec3 myInputtedColor out vec3 myOutputtedColor void main() { myO...

Aqua•4/3/23, 12:25 PM

yep, the

in

in

value in this case would come from the vertex shader
so you'd define vertex colors in your vertex buffer, set up the attribs, and then set this value in the vertex shader

Aqua•4/3/23, 12:26 PM

based on what you're trying to do though it could be done with a uniformuniform
but vertex colors is what i'd advise doing

Ffornite but how does it know that variable is for the color and not something else

Aqua•4/3/23, 12:26 PM

out

out

variables in fragment shaders are always for color

AAqua based on what you're trying to do though it could be done with a `uniform` but v...

forniteOP•4/3/23, 12:26 PM

oh yeah im reading about those right now

forniteOP•4/3/23, 12:26 PM

is this right

forniteOP•4/3/23, 12:27 PM

so this would output my color which i input from my c# externally

Aqua•4/3/23, 12:28 PM

that would work sure
just remember this only works if you do separate draw calls, uniforms have the same value throughout the draw call
this is why i'd advise using vertex colors, it allows you to change them even while still using one draw call

AAqua that would work sure just remember this only works if you do separate draw calls...

forniteOP•4/3/23, 12:28 PM

yeah im doing separate draw calls

Aqua•4/3/23, 12:28 PM

my sprite renderer passes through a bunch of vertex parameters, including stuff like rotation information. because of this I can draw up to 16384 sprites in a single draw call

forniteOP•4/3/23, 12:29 PM

maybe one day ill figure out how to do all this in one draw call but im gonna stick to this for now cus it works

AAqua my sprite renderer passes through a *bunch* of vertex parameters, including stuf...

forniteOP•4/3/23, 12:29 PM

im still confused though

forniteOP•4/3/23, 12:29 PM

so the fragment shader

forniteOP•4/3/23, 12:29 PM

sets the color of every individual pixel

forniteOP•4/3/23, 12:29 PM

i get that

forniteOP•4/3/23, 12:29 PM

but the vertex shader

forniteOP•4/3/23, 12:29 PM

sets the color of the vertices?

forniteOP•4/3/23, 12:30 PM

a vertice is just a corner though

Aqua•4/3/23, 12:30 PM

the vertex shader determines what position on the screen each vertex is

Linx145•4/3/23, 12:30 PM

only 16384? pfft

Aqua•4/3/23, 12:31 PM

it's an arbitrary limit i manually set

Aqua•4/3/23, 12:31 PM

my engine is a 3D engine so there's no need to waste GPU memory for a bunch of sprites that will never be drawn

AAqua the vertex shader determines what position on the screen each vertex is

Aqua•4/3/23, 12:32 PM

basically
vertex shader = position
fragment shader = color

forniteOP•4/3/23, 12:33 PM

OH MY GOD

forniteOP•4/3/23, 12:33 PM

IM SO HAPPY

forniteOP•4/3/23, 12:33 PM

I DID IT

forniteOP•4/3/23, 12:33 PM

I CAN DRAW MULTIPLE SHAPES AND I CAN HAVE THEM BE DIFFERENT COLORS

forniteOP•4/3/23, 12:34 PM

i simplified like 270 lines of code into like 15 lines of code

forniteOP•4/3/23, 12:34 PM

forniteOP•4/3/23, 12:34 PM

forniteOP•4/3/23, 12:34 PM

ive never been more happy to see some basic shapes on my screen

forniteOP•4/3/23, 12:35 PM

ive also made a thing for the coordinate system to be in pixels instead of floats

forniteOP•4/3/23, 12:35 PM

and instead of coming from the middle

forniteOP•4/3/23, 12:35 PM

the coordinate system comes from the top left and increases towards the bottom right

forniteOP•4/3/23, 12:36 PM

like most game engines have it cus im used to that

Aqua•4/3/23, 12:36 PM

your life will be a lot easier once you get to transformations in the learnopengl tutorial

AAqua your life will be a lot easier once you get to transformations in the learnopeng...

forniteOP•4/3/23, 12:38 PM

i will definitely read about that

forniteOP•4/3/23, 12:47 PM

do i even wanna know how to draw a circle

Aqua•4/3/23, 12:49 PM

circles are a lot harder. you either have to draw lots of small triangles, draw a circle texture, or do what I do which is to use an SDF which is a whole nother thing entirely

AAqua circles are a lot harder. you either have to draw lots of small triangles, draw ...

forniteOP•4/3/23, 12:51 PM

could i make a program that basically creates an empty array and then goes along bit by bit by the circumference of the circle until it makes a full circle and comes back to the start

forniteOP•4/3/23, 12:51 PM

and with each iteration it stores that coordinate into the array and then uses that as a buffer

Aqua•4/3/23, 12:52 PM

you have to make sure it creates triangles

Aqua•4/3/23, 12:52 PM

generally for that i'd use a triangulation algorithm. but i don't know, i never even bothered doing that, I just use SDFs

Aqua•4/3/23, 12:52 PM

the easiest thing to do though is almost certainly going to be to create a texture CPU side and then draw it

Aqua•4/3/23, 12:52 PM

won't be particularly fast but the other two ways are vastly more complicated

forniteOP•4/3/23, 12:56 PM

ah shit

forniteOP•4/3/23, 12:56 PM

on that note

```glsl in vec3 myInputtedColor out vec3 myOutputtedColor void main() { myOutputtedColor = myIn

Similar Threads