Search Issue Tracker
By Design
By Design in 6000.4.X
Votes
0
Found in
6000.3.0b7
6000.4.0a3
Issue ID
UUM-122502
Regression
No
Default Shader Graph in the VFX Graph Output block can't be reselected when switched to the custom Shader Graph
How to reproduce:
1. Open the attached project "DefaultBug"
2. Create any VFX Graph
3. In the VFX Graph, create the "Output Particle Shader Graph" block
4. Navigate to the "Shader Graph" field, open the selector and observe the results
5. Select the "New Shader Graph"
6. Reopen the selector and observe the results
Expected results: The same amount of Shader Graphs is available in both cases (custom and default ones)
Actual results: After selecting the custom Shader Graph, all default ones can't be selected
Reproducible with: 6000.3.0b7, 6000.4.0a3
Can't test with: 6000.0.60f1, 6000.2.8f1 (No default assets)
Reproducible on: macOS Sequoia 15.6 (M1)
Not reproducible on: No other environment tested
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
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
Resolution Note:
Unable to reproduce the issue exactly as described.
The observed difference in available Shader Graphs appears to be related to a hidden toggle in the selector UI. This toggle controls whether assets from packages or only those from the project are displayed. In one case, the toggle was enabled, showing both default and custom assets; in the other case, it was disabled, resulting in only project assets being listed.
Resolution Note (6000.4.X):
Unable to reproduce the issue exactly as described.
The observed difference in available Shader Graphs appears to be related to a hidden toggle in the selector UI. This toggle controls whether assets from packages or only those from the project are displayed. In one case, the toggle was enabled, showing both default and custom assets; in the other case, it was disabled, resulting in only project assets being listed.