Search Issue Tracker
Won't Fix
Won't Fix in 2023.1.X
Votes
0
Found in
2022.2.0b9
2023.1.0a15
Issue ID
UUM-16319
Regression
No
VFX shader dependencies can be assigned to Mesh Output
How to reproduce:
- Open the attached package
- Open Mesh Output VFX
- Open Shader Object Picker
- Notice that VFX are in the search results
- Assign any vfx to teh shader graph field
Expected result: VFXs are not listed in the search, and shader depenedencies cannot be assigned
Actual result: Errors are thrown to the console, VFXs are listed and can be assigned to the field
Not reproducible with: 2021.3.11f1
Error message: [Worker39] Shader error in 'Hidden/VFX/LitOutputs - Simple Lit Translucent - Cookie/System (1)/Output Particle HDRP Lit Cube': unrecognized identifier 'OUTPUT_GBUFFER' at line 2560 (on d3d11)
Scenario: sometimes it catches SG and then assigns that shader to several mesh outputs
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
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 (2023.1.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.