Search Issue Tracker
Fixed
Fixed in 6000.1.0b7, 6000.2.0a4
Votes
0
Found in
2021.3.47f1
2022.3.55f1
6000.0.33f1
6000.1.0b1
6000.2.0a1
Issue ID
UUM-91833
Regression
No
"'isfinite': no matching 1 parameter intrinsic function" error when trying to output a Texture2D from a custom function node
Reproduction steps:
1. Create a new 3D project
2. In the Package Manager (“Window → Package Manager”), install the “High Definition RP“ package
3. Import and open the “Test.shadergraph”
4. Observe the “Yeah (Custom Function)“ node
Expected result: No errors appear
Actual result: “'isfinite': no matching 1 parameter intrinsic function; Possible intrinsic functions are: isfinite(float|half) at line X“ error appears
Reproducible with: 2021.3.47f1, 2022.3.55f1, 6000.0.33f1, 6000.1.0b1
Reproducible on: Windows 10 (22H2), Windows 11 (24H2) (reporter’s environment)
Not reproducible on: No other environments tested
Note: Adding a vector or float output as the first slot fixes the issue and works as a workaround
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Redoing creation of Sub Scenes and Cube GameObjects in Hierarchy throws “Assertion failed on expression: 'targetScene != nullptr’” error in Console window
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Group Selection title text size is smaller in renaming than the actual font size
- Rich Text is not correctly highlighted when searching through Debug Logs in the Console window
- Shader warning in 'Hidden/Core/DebugOccluder' thrown after building High Definition 3D Sample Template
Add comment