Search Issue Tracker
Won't Fix
Won't Fix in 2023.2.X
Votes
0
Found in
2023.2.0a8
Issue ID
UUM-32086
Regression
Yes
[HDRP/VFX] Particles flicker when SG is assigned and Receive Decals and Debug symbols are enabled in Output
How to reproduce:
- Import the attached package
- Drag VFX Graph to the scene
- Select VFX and switch to rotation gizmos
- Rotate VFX along Y axis
- Observe the Scene View or Game View
Actual result: particles do flicker
Notes:
- Not reproducible in URP
- Reproducible in Editor&Player
- Reproduced on macOS M1
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
- Different text alignment in the column header in Entities "System" window
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- 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
Resolution Note:
Reading the various comment it seems to me that it could be a code generation problem with FXC. When outputing debug symbol it disable optimization as well and maybe this is the root cause of the problem.
Given the issue only appear with debug mode, it is of low priority for users to be solve and if it is an FXC bug, as FXC is not maintain anymore by microsoft we will not go anywhere either. Only possible fix in such context would be to rewrite/refactor the code to not met this issue, but this is too low priority to be investigated. Closing
Resolution Note (2023.2.X):
Reading the various comment it seems to me that it could be a code generation problem with FXC. When outputing debug symbol it disable optimization as well and maybe this is the root cause of the problem.
Given the issue only appear with debug mode, it is of low priority for users to be solve and if it is an FXC bug, as FXC is not maintain anymore by microsoft we will not go anywhere either. Only possible fix in such context would be to rewrite/refactor the code to not met this issue, but this is too low priority to be investigated. Closing