Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in [Package]
Issue ID
1041652
Regression
No
Support for globals in CodeFunctionNode
So I need to accsess a larger set of vectors across multiple materials and shaders.
I've used Shader.SetGlobalVectorArray() in the past with code shaders, but I don't see any possiblity to accsess these values with a Vector node or with custom code node. The only way I currently see to work arround this is to pass the globals into a render texture and read the values, pixel by pixel. But this is really painfull, even 8 properties...
I think the best solution would be to allow global variables inside custom nodes, maybe like this:
This would also alow me to reuse my old code.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Character spacing value is not applied when using a specific font asset
- [Android][IL2CPP] Player crashes on __memcpy_aarch64_simd+276 when invoking native code via a plugin on some ARM64 Android devices
- [Android]Resources fail to load when the AAB build contains a large Addressables Bundle
- Unity is loading internal version of SharpZipLib instead of local version
- The Context Menu items are ordered incorrectly
Add comment