These are chat archives for bjz/gfx-rs
Sliceis created by the api user? They can upload a large geometry buffer and use this to split it up?
SubMesh(handles of them), but since the material logic does not exist yet, I figured that just
Slicewould require less code from both sides, at least for now.
fn set_env_uniform(&mut self, EnvironmentHandle, EnvUniformHandle, device::shade::UniformValue);avoid passing UniformValue in as as enum.
EnvUniformHandlebe type safe...
Thanks for looking into it!
would an environment be unique per shader?
User is free to mix and match environments with different programs
And environment is purely a lookup table into the shader's already bound parameters
EnvironmentShortcut is a lookup table, not the
If you try and use an environment with an incomparable shader you will get some type of error or warning
Yes, we'll need to handle these cases, they are inevitable regardless of the approach we take.
So in that way, it you only eat the cost of the validation the first time you use an environment with shader
avoid passing UniformValue in as as enum
We can have
render::Client to wrap that up, and to have multiple methods (
set_env_mat4, etc). I don't think this is needed, but we can vote on that ;)
So can EnvUniformHandle be type safe
Dunno if we can make it safer without adding overhead/complexity. Improvement proposals are welcome!