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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Add comment