Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
0.3.0-preview.4
Issue ID
1219691
Regression
Yes
Invalid dependencies error is thrown when DOTS Editor and Hybrid Renderer packages are installed
How to reproduce:
1. Create an empty project
2. Open the Package Manager
3. Install DOTS Editor package
4. Install Hybrid Renderer package
5. Observe the results in the Console window
Expected results: no errors occur in the Console window
Actual results: invalid dependencies error occurs in the Console window
Reproducible with: DOTS Editor - 0.1.0-preview.2 & Hybrid Renderer - 0.3.0-preview.4, 0.3.4-preview.24 (2019.3.3f1, 2020.1.0a25, 2020.2.0a1), DOTS Editor - 0.3.0-preview.2 & Hybrid Renderer - 0.3.0-preview.4, 0.3.4-preview.24 (2019.3.3f1, 2020.1.0a25, 2020.2.0a1)
Not reproducible with: DOTS Editor - 0.1.0-preview, Hybrid Renderer - 0.3.4 (2019.3.3f1, 2020.1.0a25, 2020.2.0a1)
Could not test with: 2017.4.37f1, 2018.4.18f1 because DOTS Editor is not available
Note: invalid dependencies error does not occur when Entities package is installed before installing DOTS Editor and Hybrid Renderer packages
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
- Build fails when building a project containing an 18+ dimension array with IL2CPP
- [Android][Sentis] Human poses are not detected when using the BlazePose model
- Sprite Editor Outline Tool Overlay is not displayed when no Sprite is selected
- “No method with RuntimeInitializeOnLoadMethod attribute” warning from ReadmeEditor.cs is thrown after installing Project Auditor Rules
- Projection matrix is altered when using RasterCommandBuffer.ClearRenderTarget on DX12 and Metal
Resolution Note:
At time of writing this, the latest DOTS Editor release is 0.3.0-preview, which requires Entities 0.5.0-preview.17.
The version of the Hybrid Renderer that is compatible with that version of Entities is 0.3.2-preview.17.
When installing DOTS Editor 0.3.0-preview and then Hybrid Renderer 0.3.2-preview.17, there are no compile errors.
there are efforts in the Package Manager area towards improving the resolution of packages planned for the future, but nothing that would solve this issue right now.
The only solution right now is to notice the dependencies and install the right versions.