Search Issue Tracker
Won't Fix
Votes
0
Found in
3.16.0-beta.1
Issue ID
UUM-134505
Regression
No
Unity Hub checks the "Documentation" module by default on the 6.4 and 6.5 streams despite that it was unchecked with the previous installs
How to reproduce:
1. Open the installation of any reproducible version in Unity Hub
2. Make sure to uncheck the documentation and proceed to install
3. Open the installation of another reproducible version in Unity Hub
4. Observe the Documentation module
Expected results: The Documentation module is unchecked
Actual results: The Documentation module is checked
Reproducible with: Unity Hub 3.16.0-beta.1 with 6000.4.0b9, 6000.5.0a7
Not reproducible with: Unity Hub 3.16.0-beta.1 with 6000.0.68f1, 6000.3.9f1
Reproducible on: Ubuntu 24
Not reproducible on: macOS Tahoe 26 (M1)
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
- GameObjects made using "GameObject.CreatePrimitive" appear pink in the Player when the default material is used
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
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 as this is an issue with non-promoted Editor versions only.
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.
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 as this is an issue with non-promoted Editor versions only.
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.