roflolol Posted May 26, 2018 Share Posted May 26, 2018 As the title says mod deployment fails for FO4. The logs show nothing. I've included the log file which from what I can see says nothing about the failed deployment. It just seems like the deployment wasn't tried at all. After swapping what drive I use from my external SSD (Samsung t5) to my internal storage HDD (Seagate Barracuda) deployment works just fine. I posted an issue in the NMM forum the other day with a similar issue, but have not tried NMM since swapping. If anyone with a bit more HW knowledge could weigh in on this I'd appreciate it. Link to comment Share on other sites More sharing options...
Rattledagger Posted May 26, 2018 Share Posted May 26, 2018 Since Vortex hardlinks the files then you deploy where are two possibilities: 1: FO4 and the /mods/-directory for FO4 must be on the same partition. If example FO4 is on HD and /mods/-directory on SSD it will never work. 2: Hardlinking is a feature of the NTFS file system. Some file systems like FAT, exFAT etc. does not support hardlinking. The Samsung t5 as default uses exFAT, meaning it will never work unless you re-format to using NTFS. Link to comment Share on other sites More sharing options...
roflolol Posted May 26, 2018 Author Share Posted May 26, 2018 Since Vortex hardlinks the files then you deploy where are two possibilities: 1: FO4 and the /mods/-directory for FO4 must be on the same partition. If example FO4 is on HD and /mods/-directory on SSD it will never work. 2: Hardlinking is a feature of the NTFS file system. Some file systems like FAT, exFAT etc. does not support hardlinking. The Samsung t5 as default uses exFAT, meaning it will never work unless you re-format to using NTFS.Thanks, at least I know what the problem is then. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.