-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Extensions UBOs #9001
Extensions UBOs #9001
Conversation
name: 'clip-fs', | ||
fs: shaderFunction | ||
const shaderModuleFs: ShaderModule<ClipModuleSettings> = { | ||
name: 'clip', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Any risk sharing the name between the modules?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Any risk sharing the name between the modules?
I am not quite sure what the context is but I would avoid using same name for two modules if that is the question.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Luma assumes that the uniform block will be called ${moduleName}Uniforms
- which for starters means we cannot use clip-fs
.
It also means that if we cannot share the same uniformBlock across multiple modules. Perhaps we should add an optional ShaderModule.uniformBufferName
in luma?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[Luma assumes] the uniform block will be called ${moduleName}Uniforms
Yes... was really a hack, not an intentional design. There are some restrictions to using the same name for both block names in shaders - so I added this logic to unblock things.
It also means that if we cannot share the same uniformBlock across multiple modules. Perhaps we should add an optional ShaderModule.uniformBufferName in luma?
Agreed, at some point we will want to revisit that. Perhaps a more explicit system would be better as you suggest.
which for starters means we cannot use clip-fs.
If the hyphen is the problem, we could easily add a hyphen-case to camelCase converter or just call the module clipfs
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
name: 'clip-fs', | ||
fs: shaderFunction | ||
const shaderModuleFs: ShaderModule<ClipModuleSettings> = { | ||
name: 'clip', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Any risk sharing the name between the modules?
I am not quite sure what the context is but I would avoid using same name for two modules if that is the question.
For #8997
Change List
BrushingExtension
ClipExtension
CollisionFilterExtension
FillStyleExtension
PathStyleExtension
TerrainExtension