here's a reason you can't understand it:
here's a reason you can't understand it:
أooooooh u are very smart
أwhy skiasharp is 9mb and skia is 3.4
?
?
Pthat isn't a question any of us can answer
أok the question: is there a other lib wrap skia in C# his size is small or what?
أ
Pyeah again, we don't make skia
Pso we can't answer that question
MI've got a general OpenGL question: Does the
0GitHub
The high-speed OpenGL, OpenCL, OpenAL, OpenXR, GLFW, SDL, Vulkan, Assimp, WebGPU, and DirectX bindings library your mother warned you about. - Silk.NET/Program.cs at main · dotnet/Silk.NET
Athe first or the last 0? the first 0 refers to the location in the shader
F%disclaimer
VWe’re happy to answer any questions you might have when using Silk.NET! You can count on us for answering Silk.NET-specific questions, and being a first port of call for help using our bindings, but we’re not experts in everything so we may redirect you to a more specialised resource for API-specific info. Of course we will help where we can though, so try us and ask away!
Requested by Furball#4119.
أoh thanks
Athe last 0 refers to the offset
MYeah, the first param
indexyep that's the location in the shader
Aso in the shader where you see
layout (location = 0)Ohhh that makes a ton more sense!
PVertexAttribPointer is a horrible function, but yeah it's basically telling OpenGL what the layout of your shader is
MBasically it's telling OpenGL how to pass individual bits data to the vertex shader?
AHave you read the tutorial on the website? It goes over this in detail https://dotnet.github.io/Silk.NET/docs/opengl/c1/2-hello-quad.html#setting-up-the-attributes
MNope. Reading that now, thank you
MI've been wondering if as a complete noob to 3d graphics I should learn OGL first or go straight into vulkan? Just doing this for fun, don't intend to switch careers into game-dev
Aopengl
Fdont do vulkan
Avulkan will scare you away and you will never want to touch it again
Fyou will quit before you get even a clear color going
Pnot even AAA devs want to do vulkan
Pand they're the ones it's designed for
Fdo opengl or d3d11
MHeard it loud and clear 
No Vulkan
No VulkanFd3d11 is saner than opengl imo but it has the issue of kinda being windows specific
HI thought I knew my stuff with ThreeJS, which is a high level wrapper around OpenGL. Then I tried Vulkan and failed twice. Spent some time learning raw OpenGL (in Silk.NET) and now I'm working in Vulkan after a LOT of pain and suffering.
HDefinitely start with OpenGL....
Fdxvk exists but idk if the developer experience on linux would be great
MI wonder if D3D11 + DXVK would be easier then?
Athere is also my pie abstraction layer that has a similar API to dx11 but runs on both opengl + dx11 so its fully cross platform
MI imagine I'd have to run my dotnet code through Wine/mono to get DXVK tho?
Fdxvk alone would be enough iirc
Fim pretty sure you lose the ability to debug with renderdoc though
For you have to debug but still partially have to know what vulkan does
Pyeah d3d11 is best developed on windows, as at least you know your code works against the real thing before brining dxvk in the loop
Pbut dxvk pretty much works ootb with silk.net 2.17, no mono/wine needed
MGotcha. For now I'll stick to opengl and take it easy, baby-steps
Pyeah fair
Pif you do want to give yourself a little treat you could use OpenGL 4.5, the glNamed* functions are very nice to use
HI definitely agree with that, they are super nice
Fbut also come with the issue that renderdoc absolutely hates DSA
Pdid not know that
Pthat sucks
Hoof