Search Issue Tracker
Fixed in 2020.2.X
Votes
0
Found in
2020.2.0a7
Issue ID
1234747
Regression
Yes
[Component] Dragging a VFX asset to the hierarchy or scene no longer assigns it.
Repro steps:
1. Open a VFX-enabled project
2. Create a VFX asset in the Project folder
3. Drag the VFX asset to the scene or hierachy
4. Select the newly created VFX game object and observe that the VFX asset is not assigned in the Asset Template field.
Expected outcome:
The VFX asset to be assigned to the template field
Notes:
- Works in 2020.2.0a5
- Issue happens in 2020.2.0a7
- Repros with 7.x and 8.x VFX; probably C++ issue.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Add comment