Search Issue Tracker
Fixed
Fixed in 6000.0.10f1, 7000.0.0a1
Votes
0
Found in
6000.0.7f1
7000.0.0a1
Issue ID
UUM-74375
Regression
Yes
The Visual Effect Graphs Custom HLSL node does not generate errors when the HLSL code used is incorrect
How to reproduce:
1. Open the “2024-06-11 VFX graph custom HLSL“ project
2. Open the “SampleScene“
3. Open the “New VFX“ in the Visual Effect Graph window
3. Observe the Game/Scene view and the Console window
Expected result: Shader errors are displayed in the Console window that shows the issue and the “New VFX“ visual effect is not displayed
Actual result: No shader errors are displayed in the Console and the “New VFX“ visual effect is displayed without the Custom HLSL Block effect
Reproducible with: 2023.3.0a7, 6000.0.7f1
Not reproducible with: 2023.3.0a6
Could not test with: 2021.3.39f1, 2022.3.34f1 (No feature of the Custom HLSL Block)
Reproducible on: macOS 14.5 (Intel), Windows 10 Pro (User’s)
Not reproducible on: No other environments tested
Notes:
- The “Custom.hlsl“ script line “_attributes.scale = float3(1, size, 1); “ should throw the errors
- Might need to test every version with a freshly uncompressed project
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
- Animator Controller throws MissingReferenceException after undoing Layer Creation
- Full stack trace is always printed when an exception occurs in an IL2CPP build
- Licensing Client fails to launch when opening Unity Hub (licensing client path is not found)
- Licensing Client fails to launch when opening Unity Hub
- Different custom Shader behavior when GPU Resident Drawer is enabled
Resolution Note (fix version 6000.0.10f1):
Verified in build 6000.0.10f1