like if you only ever need 1 shader you dont *need* a shader abstraction
like if you only ever need 1 shader you dont need a shader abstraction
ZI mean it's probably still good to have a basic abstraction in case you might need it later
ZBut depends
Lyeah it really depends
Zarchitecture can really get wild sometimes
Lmy engine has a shader abstraction that i really havent needed in months (i have cut my engine down to only need a single shader for everything) but i havent deleted them since they are helpful incase i do ever need it in the unlikely scenario
ZIs your engine GL-based?
Lit was originally built for GL, but has expanded much further
Zoh wow
ZThat sure is a lot
Lthis is after i culled veldrid too lol
LD3D9 is on another branch
Land GL is technically 2 separate backends, one for FFP and one for modern
ZWas there something wrong with it?
Lunneeded, and buggy
Leverything veldrid handled was handled better by specialized code
ZOh well I suppose I won't use it then (Not like I was going to but I considered it before)
Ltechpizza's fork of veldrid fixes a lot of the bugs with veldrid, but since i no longer had a use for veldrid, i just didnt bother switching to it
Lless code to maintain is always better too
ZHm I suppose I'll just stick to plain Silk.NET
ZI doubt I'll have to write THAT much code anyways
ZIt already does a lot for me
Li just like learning graphics APIs
ZDon't really have any major graphic programming experience
ZProbably will go with OpenGL
ZSeems like the right start
LOpenGL or D3D11 are good starting choices
Lam trying to abstract shit in vulkan rn and its painful and I have no clue where im going
ZIs D3D11 hard or Silk does some extra stuff as well other than bindings?
LD3D11 isnt hard, its about the same difficulty of GL, just a little bit more explicit and with less old cruft
ZWell, I heard you can do some impressive stuff with modern GL in terms of performance
Lyea performance from GL wont matter for 99% of cases
Lwhat makes D3D11 a decent option is the arguably better API than GL
ZHmmm well I still have time to choose as I don't have as much time right now to code so
Lif you've already started it doesnt matter, stick with GL
Lhopping APIs isnt good for a beginner
ZHaven't started yet but thanks for the tip
ZBtw has anyone ever implemented ECS (doesn't matter which specific implementation) with Silk?
LECS implementations are generally independent of windowing and even rendering, so any ECS implementation can generally be made to work
ZYeah, just thinking about possible implementation and handling input and etc.
ZBut I think it's still manageable
ZFrom what I've seen Silk seems nice and flexible
ZWanted to try it out with Arch
ZSeems pretty user-friendly while also retaining one of the best performance results
ZProbs gonna take a while to get used to ECS
FThanks, I will take tutorial classes as base. They look logical, even though I don't need multiple shaders to draw simple unlit object.
ZGood luck!
FWatched “water rendering” tutorial on YT, they used image of landscape for reflections on water. In this case two shaders (landscape and water) are merged in code in one wall of code.
But this aproach looks not very manageble. What if we add some new effect for our “Landscape”, will need to redo water. Must be some “Manager” class which will glue all together
But this aproach looks not very manageble. What if we add some new effect for our “Landscape”, will need to redo water. Must be some “Manager” class which will glue all together
RAbsolutely! That being said, GL also makes it harder to do anything performantly and the moment you want to try and do any form of multi-threaded rendering or multi-threaded resource creation. You're fucked
RSo if you're looking at writing a multi-threaded engine, you end up either passing a context around a lot (which kills all the perf advantages), or doing a lot of deferred object creation (which might end up being faster but more complicated and requires quite a bit more synchronization).
RSo it really depends on what you're trying to do. DirectX 11 has no bindless texturing, or more accurately only 11.1 and newer has it, Don't bother targeting 11.1 exclusively, especially not with something as intrusive as that, there's literally no reason. Everything DirectX 11.1 compatible is probably fully DirectX 12 compliant as well, so it's kinda pointless. (Like nvidia 9xx and older IIRC don't have support for it)