KhronosGroup / KhronosGroup/WebGL
WebGL reports the wrong MAX_COMBINED_TEXTURE_IMAGE_UNITS?
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 2.9k
- Forks
- 704
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 4
Description
This probably doesn't matter but ... checking MAX_COMBINED_TEXTURE_IMAGE_UNITS on webglstats I see lots of GPUs that support up to 192 combined texture units but only support 32 fragment shader texture units and 32 vertex shader texture units.
Checking my own MBP on webglreport it reports 16 vertex texture units, 16 fragment texture unit but 80 combined texture units.
I'm guessing this issue comes from desktop GL where MAX_COMBINED_TEXTURE_IMAGE_UNITS is including other things like tesselation shaders and geometry shaders.
Does it make sense that WebGL and WebGL2 should never report a number higher than MAX_TEXTURE_IMAGE_UNITS + MAX_VERTEX_TEXTURE_IMAGE_UNITS for MAX_COMBINED_TEXTURE_IMAGE_UNITS?
Should that be specified or is it fine that it's reporting a number that makes no sense to WebGL?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the WebGL and WebGL2 specification treatment of MAX_COMBINED_TEXTURE_IMAGE_UNITS alongside MAX_TEXTURE_IMAGE_UNITS and MAX_VERTEX_TEXTURE_IMAGE_UNITS. Compare the reported values described in the webglstats and webglreport links, then determine whether the behavior is incorrect or needs specification clarification. Done means the expected behavior and any required specification change are agreed.
Written by the indexing model from the issue text.
Assessment
- Domain
- computer-graphics
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100