Search Issue Tracker
Won't Fix
Won't Fix in 2023.2.X
Votes
0
Found in
2022.3.3f1
2023.1.0f1
2023.2.0a19
Issue ID
UUM-40720
Regression
No
Blocks are disabled when copying and pasting whole system in a new project
How to reproduce:
- You will need two different projects , let's say one in 2021 and another in 2022.3, or 2022.3 and trunk.
- In 2021.3 project create a simple particle system
- Open graph and copy the system
- In 2022.3 project open any graph, delete it, and paste the copied system to it
Expected result: blocks are enabled
Actual result: blocks are disabled
Note:
- When copying and pasting system withing the same project block state is preserved
- Unsure if it is a regression. Seems to be not a regression, it might be coming from bool ports feature (22.2). It is not reproducible when copy pasting from on e 21.3 project to another 21.3 and QA hasn't done such test during the feature testing. Nevertheless let me know if more in depth testing is needed.
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
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.
Resolution Note (2023.2.X):
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.