Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in
4.0.0b11
Issue ID
492329
Regression
No
Errors in the console when having long names for assets
Steps to reproduce :
- create a windows folder on the desktop
- name that folder the longest name possible that windows allows
- now create a new folder in Unity
- copy the long name from the windows folder and rename the Unity folder with that name
- notice the first error :
Failed to create folder
UnityEditor.DockArea:OnGUI()
- create a new script and rename it also with the long name and notice the second error
- also notice that the script is now invisible in the project browser
DirectoryNotFoundException: Could not find a part of the path "C:\Users\Marek\Documents\New Unity Project 16\Assets\Standard Assets\1234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234.js"
*note :
Following the Windows folders workflow, when entering a very long name the characters should stop at one point not allowing the user to enter more letters.
Also, the problem becomes more visible for hierarchies of folders, where a long top-level folder name affects the allowed length of child folder names (seems like we limit the allowed name length based on total path length?).
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Only the left screen is rendering when using Render Graph Fullscreen Blit in Meta Quest 2
- Context menu with the "Revert" option doesn't appear when pressing the right mouse button on a "Vector2" or "Vector3" property in the Inspector of a custom shader
- Missing Render Feature "Full Screen Pass Render Feature" in any “Universal Renderer Data” asset when upgrading from 2022.3
- Inconsistent ParticleSystemVertexStream.PercentageAlongTrail data range in Trail Texture Modes except "Stretch"
- The Graph Debug Window can be right clicked through and the Node Workspace is manipulated instead
Add comment