Search Issue Tracker
Fixed
Votes
1
Found in
4.1.0f4
Issue ID
533268
Regression
No
Resources.LoadAll does not accept Path.DirectorySeparatorChar characters in the path.
Resources.LoadAll only accepts Path.AltDirectorySeparatorChar characters in the path. using Path.DirectorySeparatorChar fails.
if you try to construct a path using Path.Combine the Combine method uses Path.DirectorySeparatorChar to join paths.
Also a user could specify a path to a resource to load and they could type Path.DirectorySeparatorChar or Path.AltDirectorySeparatorChar.
This behavior is not in line with .net (and probably mono) behaviors.
Resources.LoadAll should treat Path.DirectorySeparatorChar & Path.AltDirectorySeparatorChar slashes the same.
Also the documentation does not mention this about using only Path.AltDirectorySeparatorChar characters.
NOTE: I did not test Resources.Load but I am assuming it behaves the same.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Mono Windows Builds don't produce full log callstacks when generating logs
- 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
Add comment