Hundreds of errors in Visual Studio, we meet again! After refactoring shaders to support hot reloading (which is awesome) I realised the way textures were bound to shaders wasn't great. So now, I'm refactoring shaders... again... - ThreadSky

About ThreadSky

vercidium.com • 88 days ago

Hundreds of errors in Visual Studio, we meet again!

After refactoring shaders to support hot reloading (which is awesome) I realised the way textures were bound to shaders wasn't great.

So now, I'm refactoring shaders... again...

Comments

vercidium.com•88 days ago

I previously had a ShaderUniform class which was used to set a value on a uniform in a shader. It had functions like SetInt, SetVec3, SetMat4, etc.

However this meant I could call SetMat4 on an integer uniform, and it won't throw an error.

vercidium.com•88 days ago

So I changed ShaderUniform to be an abstract class, with multiple ShaderUniform classes that inherit from it.

To define uniforms for a shader, I can now call AddUInt(...), AddFloat(...), etc:

vercidium.com•88 days ago

The best change is that textures are now bound at the same time uniforms are set.

This uniform class is the only time that glActiveTexture is called, which means uniforms and textures will never be out of sync.

vercidium.com•88 days ago

The TextureUnitHelper just keeps track of a counter that resets when a shader is bound, to ensure two different textures / sampler types aren't using the same texture unit.

Bindless textures would also solve this, but I'd like to maintain support for older GPUs

Posting Rules

Be respectful to others
No spam or self-promotion
Stay on topic
Follow Bluesky's terms of service

Comments

Posting Rules

Reply