Search Issue Tracker
Fixed
Fixed in 2023.3.X, 2023.3.0b5
Votes
0
Found in
2021.3.5f1
2023.2.0a1
2023.3.0a3
Issue ID
UUM-566
Regression
No
[Output Mesh] Shadows forced on Output Mesh when particle outputs are casting shadows
(This is a recent regression of the fix for case 1312649, thus it's logged separately)
Repro steps:
1. Import the attached package and open the repro scene
2. Observe that both the particles and the capsule are casting shadows.
Expected outcome:
- The capsule to not cast shadows as the Mesh Output's 'Cast Shadows' is 'Off'
Notes:
- Looks like when 'Cast Shadow' is set to 'On' for the particle output, it overrides the 'Off' of the Mesh Output.
- If the Mesh Output is set to cast shadows, but the particles are not, it works as expected.
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
Add comment