Search Issue Tracker
Feature Request
Feature Request in 6000.0.X
Votes
0
Found in
2020.3.46f1
2021.3.21f1
2022.2.12f1
2023.1.0b9
2023.2.0a7
2023.3.0a3
6000.0.0b11
Issue ID
UUM-31304
Regression
No
Texelsize node does not return the correct value when you reduce the texture quality in quality settings.
The shadergraph node "texelsize" does not return the correct value when you reduce the texture quality in quality settings. I discovered this while working with the surface gradient framework, where stepsize become mismatched once the texture resolution is reduced in project quality settings (Master texture limit).
Documentation has this to say:
"The width and height of the texture object report the original, non-limited sizes. You may have to take this into account if you perform special sampling or processing with textures subject to the master limit quality setting, and you use masterTextureLimit > 1."
We have no way that i know of to access the master texture limit in shadergraph so it is hard for users to compensate (and somewhat obscure to discover that you need to do so)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note:
We need to provide a generic way of getting the texel size that takes into account the project settings.
Resolution Note (6000.0.X):
We need to provide a generic way of getting the texel size that takes into account the project settings.