As you can see, i have a number of networked drives available to me in explorer, but when i migrate assets, and am prompted to choose the destination content folder, i cannot see any of the drives.
Is there a work-around for this? or is something wrong with the way my mapped network drives are set up. I have not had any other issues accessing these drives from any other software (3DS, photoshop, Sketchup, Rhino, Unity etc)
My work around for this so far, has been to of course create a project locally, but i’m quickly running out of space due to my C drive being an SSD.
Furthermore, it seems that local project creation has created over 40gb worth of project files. only 14gb of that is actually in the project folder itself, the rest is scattered in my user folder (user/roaming/local/Unreal Engine/…) and i have no idea what is safe to delete. Any help would be greatly appreciated. Thank you
Just how does UE4 eat so much disk space? … Still a work-in-progress but here’s some pointers…
Drive letters are quite 90’s. What about UNC does that work instead? \host-name\share-name\file_path
Unreal often keeps a master copy of source projects here…
There may be lots of needless duplicates eating space: …Program\Unreal Engine\Launcher\VaultCache
This cache also eats vast amounts of space and can be deleted…
Note: It’ll be recreated again which slows re-opening of projects first time: …Users*\AppData\Local\UnrealEngine\Common\DerivedDataCache
A lot of needless gigs are also lost to endless Launcher bloat located here: C:\Programs\Unreal Engine\Launcher\Backup
Unfortunately Epic seem to have taken Unity’s file model to heart.
Its a sprawling mess compared to the simplicity of UDK-GAD!
Do backups before purging anything! UE4’s gluttony appears endless.
Sorry for the necro post, but can confirm this is still an issue. Me and several other people have to work from network drives, and I can’t migrate individual assets without copying the whole project over first.
Any updates on this issue? Is it planned to be fixed, or is it at least being looked at? Anyone submitted a bug report for it yet?
Just had the same issue but figured it out, just go into windows explorer and copy the path of where you want to place the files and copy that path into the migrate folder window and press enter and it should migrate. Also the next time you go to migrate that network drive should be visible in the migrate window