Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.4
2019.4
2020.3
2021.2
2021.2.0b6
2022.1
Issue ID
1354815
Regression
No
'No <...> module loaded' screen remains after adding module to the open editor
How to reproduce:
1. Create a new Unity project
2. Without closing Unity, open Unity Hub
3. Add any module to the opened editor
4. After the component is installed, return to Unity editor
5. Select recently downloaded platform
Expected result: Build settings are shown related to the selected platform.
Actual result: 'No <...> module loaded' screen is shown. Although, the platform can be switched to the selected one.
Workaround: reload the editor.
Reproduced with: 2022.1.0a4, 2021.2.0b6, 2020.3.15f2, 2019.4.29f1, 2018.4.36f1.
Didn't reproduce with: 2022.1.0a1, 2021.2.0a1, 2020.3.0f1, 2019.4.0f1, 2018.4.0f1.
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
- Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
Resolution Note:
Unity must be restarted after installing a platform module.