Hello fellow UE developers:
I’ve been working with UE for a few years now, and I’m hunting down a warning that’s been appearing all over my projects:
Warning: FPathExistence failed to gather correct capitalization from disk for
K:/UEFN/FirstIsland_/Plugins/FirstIsland/Content,
because GetFilenameOnDisk returned non-matching filename
'//UNC_PATH/UEFN/FirstIsland_/Plugins/FirstIsland/Content
I work off a network drive, as I’m constantly working on new stuff and it’s the cheapest way to have lots of space available.
First thing to notice here, is that “K:” is a drive letter assigned by mounting the network drive.
“GetFilenameOnDisk” wants to access the file using the UNC path, which is the network drive’s “IP_ADDRESS/Shared_Folder”
I have tried getting around this using two methods:
Define the shared folder as a “Network Location” rather than a “Network Mapped Drive”
This causes UEFN to not be able to properly read the location, as it uses backslashes, and UE is expecting forward slashes on paths.
Define a symbolic link using mklink /d, which results in the same problem as the above solution, conflicts with slash orientation.
Does anyone know what is the best way to mount/declare network drives so we can get rid of these warnings?
Cheers,
L
Best thing you can do is implement some SVN to check out the files locally, edit them, and subsequently push them back to the network disk.
I see, so SVN could be one solution, but it seems then that P4 would be the way to go?
UE has its own Source Control that I have to admit have never used, but seemed like a promising (and Engine native) alternative to go all out and use P4. I work by myself so I haven’t really looked into it but if it’s the most elegant way to handle this sort of thing, I’ll gladly try it out.
Thanks for your reply! @MostHost_LA
Could be anything - even cygwin and tortoisesvn if that is what you know.
The only thing it needs to do is to pull the files to your local drive as a check out and push them back into the networked drive as a check in.
I think even github desktop can do this, being a git management system instead of a full svn…
I see. I’m gonna try to set up P4 which may be overkill, but to me it’s very odd that I only get this warning on some random files in projects where I have tens of thousands of other files. I sort of understand checking in and out locally and then pushing to the server, but would this mean needing to have a local copy of the project somewhere on the local drive?
I’ve been meaning to setup P4 on my file server for years now and have been avoiding digging into that but it seems the time has come.
Yes, but you really should only be working that way, and preferibly off an m.2 with max write speeds.
Otherwise, everything is ran off the networked drive which limits your evrrything based on the network speed (which hoevever good will never even match the speed of an m2…)
Oh I see. Well I’ve been working off 10G networks for almost 10 years now and they perform great. I get up 800 Mb/s read/write, so you can read a heavy format like exr and still get realtime playback at 60fps on Resolve for instance. It’s roughly twice as fast as an SSD. But still slower than an M.2.
Thanks for your replies. It’s really been helpful and insightful.
Nice week!
1 Like