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
- Rendering locks up when not looking at a transparent material on Meta Quest 2
- Volumetrics break when using a Custom Pass to create a Thickness Buffer for Alpha Clipping
- All tests are run instead of only the failed ones when the "Rerun Failed" button is pressed
- GameObject is not masked when the "Render PostProcessing Effects" pass executes with a resolved non-MSAA Color target and MSAA DepthStencil target
- [Android] Gfx.WaitForGfxCommandsFromMainThread high performance usage and inconsistency when built Player scene has Canvas GameObject on a specific Project
Add comment