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
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
- White lighting artifact when a point light with a small emission range and "Hard Shadows" touches an object while a directional light with "Soft Shadows" and another point light are present
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.