Search Issue Tracker
Active
Under Consideration for 1.11.X
Votes
0
Found in [Package]
1.8.0-pre.2
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 Asset icon is not shown on creation unless you confirm the name
- APV Sky occlusion doesn't consider the terrain
- [iOS] "EXC_BAD_ACCESS" Player crash when Script Debugging is enabled
- Cursor skips input fields when tabbing between two sets of input fields
- "Shader error redefinition of 'Varyings'" error appears when selecting the shader
Add comment