Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2020.1.X
Votes
0
Found in
2019.3.0f4
2020.1
2020.2
2020.2.0a10
Issue ID
1244305
Regression
No
External tool path slashes are inconsistent and does not represent MS-DOS standard
How to reproduce:
1. Open any project with android support
2. Navigate to Preferences > External Tools
3. Check the "Recommended" checkboxes
4. Observe the JDK/SDK/NDK paths
Expected Behaviour: All paths have the same slashes (Preferably "\" as it is MS-DOS standard)
Actual Behaviour: Path slashes are not the same (Observe SDK and JDK last slashes), also, the slashes do not represent MD-DOS standard
Reproducible with: 2019.3.13f1, 2020.1.0b9, 2020.2.0a10
Could not test on 2018.4 since it does not have the visible path when the checkbox is checked
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Shadows flickering when a Mesh's Cast Shadows are set to Shadows Only and Camera is moving with Spotlight
- AudioMixer exposed parameters cause assertions when hidden and prevent the drop-down from functioning
- Package Manager/My Assets: 401 Response code trying to download a paid asset store package
- TrailRenderer.SetPosition will log a Index out of bounds error when index is in bounds of the positionCount property
- [URP] Graphics.DrawMeshInstancedIndirect rendering correctly after clicking an another application/refreshing Assets
Add comment