Search Issue Tracker
Won't Fix
Won't Fix in 1.0.X
Votes
0
Found in [Package]
1.0.9
Issue ID
BEHAVB-296
Regression
No
Assigning the same variable to 2 RunSubgraph's fields throws errors and breaks the graph window
Steps to reproduce:
- Download and import the attached "Behavior Repro Subgraph Error.unitypackage"
- Open "Parent"
- Click on the "Run SubGraph node" to view it in the inspector
- Assign both "Self" and "Target" to the Self variable
- Save (an error is thrown)
- In the project view, open the subgraph
Actual results: The console throws errors and the subgraph can not be opened
Expected results: No errors are thrown and the subgraph can be opened
Reproducible with versions:
1.0.9
Tested on (OS): MacOS
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
- UI Builder windows text rendering breaks when using Rich text combined with an underlined emoji
- [Linux] Crash on mono_runtime_invoke when executing a specific script
- Installing the HDRP Water Samples doesn't notify the user to enable the "Water" on HDRP Asset
- Persistent Memory Leak in `ChunkDrawCommandOutput` and `CullingSplits.InitializeSplits`
- 1 KB or more of GC is allocated when Debug logging
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Resolution Note (1.0.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.