Voit lisätä twiitteihisi sijainnin, esimerkiksi kaupungin tai tarkemman paikan, verkosta ja kolmannen osapuolen sovellusten kautta. Halutessasi voit poistaa twiittisi sijaintihistorian myöhemmin. Lue lisää
Hmm mainly, I've been finding the cross-section of what's being shared from stage to stage is shrinking. Many studios I've worked with have had thousand+ lines of code in a single shader file, so I've found that just separating them (grouping within directories) helps my sanity
What holds me up here is explicit bindings. Sure, vertex shader may rarely, if ever, use the same buffers/textures as the fragment shader, but they still have to agree on binding. No overlapping, for instance. If spread across files, how do they all agree?
Are you using GLSL, HLSL, or a custom dialect of sorts? I think the solution sort of depends.
Well... At the moment glsl. I've tended toward this design in hlsl as well. At a previous job, this sort of thing was more or less strictly enforced by a technique-like wrapper language. I'm interested in what makes a difference. Literally trying to sponge knowledge rn.
Twitter saattaa olla ruuhkautunut tai ongelma on muuten hetkellinen. Yritä uudelleen tai käy Twitterin tilasivulla saadaksesi lisätietoja.
