`FWindowsPlatformFile::GetFilenameOnDisk()` uses GetFinalPathNameByHandle, which returns the final path. According to the windows documentation:
A final path is the path that is returned when a path is fully resolved. For example, for a symbolic link named “C:\tmp\mydir” that points to “D:\yourdir”, the final path would be “D:\yourdir”.
The documentation for `IPlatformFile::GetFileNameOnDisk()` says “For case insensitive filesystems, returns the full path of the file with the same case as in the filesystem”. So theoretically, `GetFileNameOnDisk()` should be returning the same path, but with correct casing, instead of the fully resolved canonical path. I’m curious to know if Epic is aware of this discrepancy and if there are any plans to update the Windows implementation to return the actual path with correct casing, rather than the final path.
For context, my project uses a mapped T drive (my computer doesn’t have an actual T drive) and the asset registry is spamming warnings “LogAssetRegistry: Warning: FPathExistence failed to gather correct capitalization from disk for T:\p4\…\<filename>, because GetFilenameOnDisk returned non-matching filename C:\p4\…\<filename>”.
[Attachment Removed]