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
- Animator state transition preview clips are flickering when zooming in
- [Tile Palette] Sprites not rendering when brush tool "Paint a filled box with active brush" is used for the first time
- Longer Shader Graph Property Reference names breaks VFX Graph Output Particle Node
- "DebugAllocatorMode" option changes when changed in another Editor instance
- UITK Debugger new Classes element is not created with no information or warnings thrown when adding more than one element with the default name
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.