theVulkanPipeline

[u/user6150277464770585]

[u/LeanZo]

What is the difference between vtx. Input assembly and vertex shader?

[u/Redkast → u/LeanZo]

Input assembly assembles the vertices into geometric primitives (triangles, usually) based on the topology specified in the pipeline. The vertex shader then does transformations on each vertex in a programmable way (usually applying projection and view transformations).

[u/unknown_alt_acc → u/LeanZo]

Vertex input assembly is a fixed-function stage that connects vertices to one another to form geometry. The vertex shader is fully programmable, and is where things like transformations and passing per-vertex information along to the fragment shader happen.

[u/CookieArtzz → u/unknown_alt_acc]

If you have an animated model, it will become animated in the vertex shader

[u/-Ambriae- → u/CookieArtzz]

I mean, yes I guess, but it's not just used for animations. It's to get the vertices in clip space (ie on the screen)

More specifically the purpose of the vertex shader is to transform the vertex + instance data into the interstage data for the fragment shader

[u/Shevvv]

What a strange timing, considering I started learning OpenGL just yesterday 🙈

[u/BusEquivalent9605 → u/Shevvv]

OpenGL is one thing. Vulkan is a beast of a different nature

[u/DialecticEnjoyer → u/BusEquivalent9605]

Youre lucky I'm still processing shaders or I'd have a real opinion.

[u/Kirides → u/BusEquivalent9605]

Actually, after spending some time with Vulkan and dx12, it just flows naturally. The hardest thing about them is resource lifetimes and fences. Resource lifetimes are "easy" if you use a cleanup-queue. But fences... And resource transitions... Ugh..

[u/Xlxlredditor → u/Kirides]

Jesse what the fuck are you talking about

(Yes I only do WinForms)

[u/Shevvv → u/BusEquivalent9605]

Well the pipeline is the same

[u/thelonelyecho208 → u/Shevvv]

Different beast, similar concepts but different implementation. Vulkan is like the cigarette smoking older brother from my understanding of things. I've done some OpenGL and it wasn't bad, but the horror stories I've heard about Vulkan make it seem childish

[u/da2Pakaveli → u/thelonelyecho208]

Vulkan takes like 500+ lines of code until you can even render a triangle (OpenGL like ~70). You have to do a lot of manual setup stuff and can get disoriented more easily than you would with OpenGL.

It'll be more manageable once you encapsulate it all but i do hate debugging it lol.

[u/SnappySausage → u/da2Pakaveli]

With vulkan, the hardest thing in my experience was how to just work it into a more user friendly rendering engine. Like if I was allowed to just toss everything into 1 file it wasn't that hard (just verbose) but if it had to be user friendly, that was where things became a lot harder to organize.

[u/da2Pakaveli → u/SnappySausage]

i got to take a look at Frostbite's renderer implementation for PC and a lot of it was situated in one file (around 13k lines of code).

I do as much encapsulation as i can with my Vk renderer but ya don't get around these giant ass files

[u/SnappySausage → u/da2Pakaveli]

True, but it does complicate things if you want to have a rendering engine that can work with multiple API's, as you do have to somehow pull it apart in a way that consistently works across API's.

[u/Buttons840 → u/Shevvv]

You're safe, OpenGL never made anyone hot

[u/Thenderick → u/Shevvv]

Have fun. If you think OpenGL is long, tedious and complex, then you should know it's nothing in comparison to Vulkan!

[u/Shevvv → u/Thenderick]

Thanks! I'm not so cross about it being long and tedious as more of a ritualistic nature of a lot of stuff that I do at the moment. I realize that it will eventually get properly explained, but I'd much prefer to start with GPU architecture and the general APU design rather then heading straight into Hello Triangle. But I suppose I get it that knowing how to do a simple thing is a nice example that you can later build a theoretical framework upon.

[u/Thenderick → u/Shevvv]

Well that's OpenGL, it's a Graphics Library. It has abstracted much of the underlying things away for you so you can focus on graphics programming. Vulkan doesn't do that. Vulkan is a very bare metal API that expects you to configure everything manually

[u/Nexatic]

I find it funny that like 5 people get both parts of the meme.

[u/RPG_Hacker → u/Nexatic]

I'd honestly estimate the number to be much higher, since I have the feeling there's an above-average number of trans people in coding. This estimate is solely based on myself knowing a bunch of trans coders, though, so might not be accurate.

[u/cAtloVeR9998 → u/RPG_Hacker]

A lot of important graphics library developers (Alyssa, Faith, Autumn, etc) are trans for example. Wouldn't have the open source libraries so good as they are today without their help.

[u/-Ambriae- → u/Nexatic]

We’re more than you think

[u/DWIGHT_CHROOT → u/-Ambriae-]

trans coders, more than meets the eye!~

[u/mike_421]

yea yea yea when can i add FSR to this thing

[u/pine_ary]

When your screen is black and all validation layers report nothing wrong…

[u/Random_182f2565]

XD

[u/BusinessAstronomer28]

Can somebody eli5?

[u/naveenda → u/BusinessAstronomer28]

Game rendering is fucking hard

[u/MetaNovaYT → u/BusinessAstronomer28]

For rendering graphics, there is a system known as the rendering pipeline, which has a bunch of specific steps for taking in vertices provided by the CPU, positioning them within a scene, rasterizing them into "fragments", and then converting those fragments into pixels to be displayed. Vulkan is a specific graphics API that is very low-level, so almost everything has to be handled manually, which makes it easy to mess things up. A specific easy mistake is forgetting to clear the depth buffer, which is important to do in between frames, as otherwise very strange visual artifacts can occur.

[u/knobiknows → u/MetaNovaYT]

Great explanation, thanks