Search Issue Tracker
Won't Fix
Won't Fix in 6000.4.X, 6000.5.X, 6000.6.X
Votes
0
Found in
6000.0.66f1
6000.3.4f1
6000.4.0b5
6000.5.0a5
6000.6.0a1
Issue ID
UUM-133722
Regression
No
Solid gray or black areas are present when using ShaderGraph with Custom Function nodes without manual reimport
Reproduction steps:
1. Open the attached project "ReproProj"
2. Open the “/Assets/Resources/Scenes/Game.unity” Scene
3. Enter the Play Mode
4. Use scroll wheel and observe the Game view
5. Exit the Play Mode
6. Build And Run (File > Build Profiles > Build And Run)
7. In Player use scroll wheel and observe the Player
Expected result: Expected pattern seen in Game view is present
Actual result: Solid gray or black areas are present
Reproducible with: 6000.0.66f1, 6000.3.5f1, 6000.4.0b6, 6000.5.0a5
Reproducible on:
Windows Standalone Player
Play Mode
Testing environment: Windows 10 Enterprise 21H2
Not reproducible on: No other environment tested
Note:
- Reproducible in Play Mode before clicking "Compile and Show Code" or reimporting the .shadergraph
Workaround:
- Add a pre-build script that calls AssetDatabase.ImportAsset() on the .shadergraph with ImportAssetOptions.ForceUpdate
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
- Performance Markers Search window shows an empty entry in the list
- Enabling Deep Profiling in Performance Markers Search window breaks Inspector panel buttons when navigating through the marker items
- Dragging selector from selector row background shows preview but does not apply class in UI Builder
- An "InvalidOperationException" error is thrown when TryRemoveItem is used with rebuildTree set to false
- Build fails with IL2CPP error when building on Android platform in a specific project
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Resolution Note (6000.6.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Resolution Note (6000.5.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Resolution Note (6000.4.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.