Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
1.3.0-pre.4 - Entities
Issue ID
ECSB-1284
Regression
No
"Argument 2: cannot convert from 'Unity.Entities.RefRW<ComponentFoo>' to 'Unity.Entities.EnabledRefRW<ComponentFoo>'" error when nesting enableable components in Aspects
How to reproduce:
1. Open the “isolated bug“ project
2. Open the “Sample Scene“
3. Observe the Console window
Expected result: No errors are shown in the Console window
Actual result: “error CS1503: Argument 2: cannot convert from 'Unity.Entities.RefRW<ComponentFoo>' to 'Unity.Entities.EnabledRefRW<ComponentFoo>'“ error shown in the Console window
Reproducible with: 1.3.0-pre.4 (2022.3.56f1), 1.3.2, 1.3.8 (2022.3.56f1, 6000.0.33f1, 6000.1.0b1)
Could not test with: 0.51.1-preview.21 (2021.3.42f1) (Aspect source generation is has not been introduced yet)
Reproducible on: macOS 14.5 (Intel), Windows 11 (User’s)
Not reproducible on: No other environments tested
Note: Possible temporary ability to work in the Editor can be achieved by changing the second argument of the “AspectFoo“ constructor to the “{{{}aspectbar_aspectfoo_componentfooRef{}}}“ value, but after every build in one session you will have to change the value again
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
- Opening Terrain Prefab in Prefab Editing Mode throws "NullReferenceException" error
- [Search] Dragging query pills put them behind the search text field
- A CustomPropertyDrawer that returns a PropertyField for a property named the same as a child field will not render all child fields
- Graphics Settings shows default values instead of the real values in the Rendering Debugger when Volume.profile is assigned via script
- Deleting multiple Tags throws “NullReferenceException”, and "Retrieving array element that was out of bounds" errors when holding the Enter key
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.