-
-
Notifications
You must be signed in to change notification settings - Fork 18.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Godot crashes when trying creating an import file whose name would be longer than the filesystem would allow #24395
Comments
Have you tried these Win10 workaround with long path names? https://www.howtogeek.com/266621/how-to-make-windows-10-accept-file-paths-over-260-characters/ https://www.quora.com/What-is-the-maximum-character-limit-for-file-names-in-windows-10 |
Still valid in 0287508 Here's backtrace:
|
Apparently, for this workaround to work, the application's manifest must allow it: https://www.tenforums.com/tutorials/51704-enable-disable-win32-long-paths-windows-10-a.html I guess we need to carry out this change in Godot first, so that the tweak can work. |
Update for Godot4, Beta4: The editor no longer crashes, but the file is simply not imported. There is no feedback to explain why the import failed. This happened organically for me, on a downloaded file with a long name. Reproducable by naming a file 'aaaaaa....aaaa.png` (max out the length). |
Godot 3.1 alpha 3
Windows 10 x64
Windows apparently won't allow file names to be longer than a set length. Godot automatically creates import files in the .import directory when an image is found in the project directory. If the file that would automatically be created would have a file name longer than Windows would allow, then Godot crashes.
Steps to reproduce:
In the project folder, add an image file. Change the file name to be as long as Windows will allow (put a bunch of dummy text in the file name until Windows forces no more characters from being added to the name). As soon as Windows accepts the new name, Godot crashes when trying to import the file.
The text was updated successfully, but these errors were encountered: