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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Add comment