Search Issue Tracker
Fixed
Fixed in 1.14.0
Votes
0
Found in [Package]
1.11.2
Issue ID
ISXB-757
Regression
No
“Binding is neither a composite nor part of a composite” errors are thrown when copying Composite Binding into non-composite Action
How to reproduce:
1. Open the “InputPackageBindingIssue“ project
2. In the Project window open the “TestControl” Input Action Asset
3. In the “Actions” category right-click on “New action” and select “Add Positive/Negative Binding”
4. Right-click on “Negative: <No Binding>” and select “Copy”
5. Right-click on “<No Binding>” and select “Paste”
6. Observe the Input Action window then the Console
Expected result: Binding is pasted and no errors are thrown
Actual result: “<No Binding>” is pasted and multiple “Binding is neither a composite nor part of a composite” errors are thrown to the Console
Reproduced with: 1.7.0 (2021.3.34f1), 1.8.0-pre.2 (2021.3.34f1, 2022.3.18f1, 2023.2.7f1, 2023.3.0b4)
Reproduced on: Windows 10 (by reporter), Windows 11
Not reproduced on: No other environment tested
Note: Reproducible when using “Cut” functionality
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Shader Graph Node information is briefly displayed in Graph Inspector when clicking on Category in the Blackboard
- Module installation fails with "Download failed: Validation Failed" errors when using beta.2 Hub version
- JsonConvert conversion fails trying to call GetCallbackMethodsForType when [OnDeserialized] is used in a class
- Shader Graph Category dropdown cannot be expanded/collapsed when clicking on the text
- Different text alignment in the column header in Entities "System" window
Add comment