Search Issue Tracker
In Progress
Votes
0
Found in
2023.1.4f1
6000.0.0b11
6000.3.0a1
6000.4.0a1
6000.5.0a1
Issue ID
UUM-43487
Regression
No
VFX Graph gets corrupted and has no properties when manually adding the VFX Graph from the older versions
How to reproduce:
1. Open the user-attached project “vfx-test.1” and then close it
2. Unzip the user-attached project “vfx-test.2” into the “vfx-test. 1” folder and replace all similar files
3. Open the “vfx-test.1” project
4. In the toolbar, click Test → Go
5. Observe the Console
Expected result: There are no errors displayed
Actual result: An error is logged in the Console because there are no properties, and VFX shader dependencies are missing (we need to recompile the effect in order to render VFX properly)
Reproducible with: 2023.1.4f1
Not reproducible with: 2021.3.28f1, 2022.3.5f1, 2023.2.0b1
Notes:
-After deleting the Library or reimporting the project into the different versions, the issue is resolved
-All affected versions can’t be properly tested because this issue is resolved by upgrading the project
-Also reproducible in Player
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
- [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
Resolution Note:
N/A (for this branch)