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
- 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
- Shader Graph "Zoom Step Size" can be set to 0 even though the zoom still works
- Enabling/Disabling the Deprecated Nodes doesn't apply to the opened Shader Graph unless any Variable is added to the Blackboard
- Group Selection title text size is smaller in renaming than the actual font size
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.