Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.3.0a1
2018.3.1f1
Issue ID
1122769
Regression
No
Assertion Errors are thrown when Shadergraph has a custom SamplerStateNode
To reproduce:
1. Open user's attached project ("SamplerState")
2. Open SamplerState.shadergraph
3. Inspect the Console
Expected: Errors are not thrown
Actual: Errors are thrown
Reproduced with: 2018.3.5f1
Notes:
- Was not able to test with 2019.1 and 2019.2 since script SampleStateNode.cs breaks
- Was not able to test with 2017.4 due compilation errors and missing namespaces
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note:
This API has been removed in 2019.1 and therefore this issue will not be fixed. A new solution for custom nodes will be available for 2019.1 soon.