Search Issue Tracker
Won't Fix
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
- [Linux] Touch freezes in Player when any mouse button is clicked
- UnityEngine.Rendering.Volume.OnEnable() is called twice before OnDisable() creating multiple copies of the same volume when a volume is enabled right after Domain Reload when entering Play Mode
- Hinge Joint transforms are reset when toggling the "useMotor" property
- Motion Vector texture reports incorrect Mesh data when Mesh is coming from off-screen
- [macOS] Display flickers with bright colors when built Player uses 2 or more Displays
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.