Search Issue Tracker
By Design
Votes
0
Found in
2019.1.0a9
2019.1.0f2
2019.2
2019.3
Issue ID
1146504
Regression
No
[Android] "NdkUseEmbedded" key is non-existent when installing Unity first time on a machine through Hub with the built-in tools
Repro steps:
1. Delete the “Unity Technologies” key from the registry ( command: reg delete “HKCU\Software\Unity Technologies” )
2. Open QA attached project “repro_1146504”
3. Enter Play Mode and observe the Console
Key "NdkUseEmbedded" doesn't exist
4. Exit Play Mode and recheck the “Android NDK Installed with Unity (recommended)” option in Preferences -> External Tools
5. Enter Play Mode and observe the Console
Actual: "NdkUseEmbedded" appears after rechecking the checkbox
Reproducible with: 2019.1.7f1, 2019.2.0b6, 2019.3.0a6
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
- [Rendering Debugger] Shortcut in documentation to open window doesn't work
- The "Compress Tilemap Borders" function is not working when used via the Context Menu or through Script
- HDRP Sorting Priority not working when Render Pass is locked on a parent material
- [XR] Camera view rendered by the RenderTexture is not updated at runtime when XR is enabled
- Lens Flare occlusion is slightly delayed when Anti-aliasing is set to TAA
Resolution Note:
Unity Editor in general does not write settings to Windows Registry on install/first run. Settings are in general written to registry on first change, there is no policy that all settings must be in the registry.
Whenever the setting is not in the registry, it means it has it's default value.