Search Issue Tracker
Won't Fix
Won't Fix in 2023.2.X
Votes
1
Found in
2021.3.5f1
2023.1.0a1
2023.2.0a1
Issue ID
UUM-533
Regression
No
VFX "Graph Output Particle HDRP Lit Mesh" is producing incorrect Shadows when used with "Orient: Along Velocity"
Reproduction steps:
1. Open the attached project
2. Open "VFX Shadow Bug Test Case.vfx" Visual Effect Graph located in the Assets folder
3. Disable the "Orient: Along Velocity" Block
4. Open the Game View
5. Observe the Shadows of the Particles
6. Disable the "Orient: Along Velocity" Block in the "VFX Shadow Bug Test Case.vfx" Visual Effects Graph
7. Observe the Shadows of the Particles in the Game View
Expected result: the Shadows are displayed correctly
Actual result: the produced Shadows are not displayed correctly as if they were calculated based on the cube before rotation
Reproducible with: 10.9.0 (2020.3.34f1), 12.1.6 (2021.3.3f1), 13.1.8 (2022.1.1f1), 14.0.2 (2022.2.0a14)
Could not test with: 7.7.1 (2019.4.39f1) - Visual Effect Graph Asset is not supported
Note: the user managed to fix the issue by editing Editor/Models/Blocks/Implementations/Orientation/Orient.cs script and passing the view matrices from a script (Camera.worldToCameraMatrix and Camera.cameraToWorldMatrix) instead of relying on UNITY_MATRIX_V and UNITY_MATRIX_I_V._14_24_34
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
- Required SpriteMask class (ID 331) is stripped when "Strip Engine Code" is enabled
- “Maximized serialized file backup not found” error is thrown when minimizing a window in a newly opened project
- Build stack trace contains invalid lines when building with IL2CPP using scripts with delegates containing generic types in the signature
- Entities Systems window has a “Show Full Player Loop” dropdown which does nothing when clicked after enabling “Show Full Player Loop”
- Entities Hierarchy Search “Show/Hide” button’s Lens Icon is blurry when the Editor is on an external monitor
Resolution Note:
After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix".This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
The case will now be closed, and will not be reopened unless new information arises that would change the issue’s impact. Please let us know if you have additional information relating to the severity of this bug.
Resolution Note (2023.2.X):
After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix".This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
The case will now be closed, and will not be reopened unless new information arises that would change the issue’s impact. Please let us know if you have additional information relating to the severity of this bug.