Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
10.0.0-preview.27, 9.0.0-preview.33, 8.2.0, 8.1.0, 7.4.1
Issue ID
1268411
Regression
No
[VFX] Input value of "Capacity" is not changing when a mouse is dragged over it under VFX Basic Initialize in the Inspector
On dragging the mouse cursor over the input field of "Capacity" under "VFX Basic Initialize" in the Inspector when the "Initialize particle" node is selected in the VFX Graph, Refer attached video.
Steps to repro:
1. Create a new project with HDRP Template
2. Project window > Create > Visual Effects > Visual Effect Graph > Open
3. Create Node > Initialize Particle > Select > Inspector
4. Change the input value of "Capacity" using mouse dragger
Actual Result:
The Input value of the "Capacity" property is not changing on dragging the mouse over it
Expected Result:
Input value for the "Capacity" property is changed using mouse dragger
Reproducible in:
2020.2.0a20, 2020.1.1f1, 2019.4.7f1 with Package version 10.0.0-preview.27, 9.0.0-preview.33, 8.2.0, 8.1.0, 7.4.1
Environment:
Occurring on Windows 10 & Mac 10.15.
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
- 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
- Addressables content build fails but the Player build is successful when building a development build
Resolution Note:
Small issue, capacity can still be changed by manually entering a number, and within the VFX Graph it can be changed both by manually entering a number or via dragging. The team has decided to not look into it further in favor of larger issues.