GGraycious Posted February 16, 2016 Share Posted February 16, 2016 This ( http://www.nexusmods.com/fallout4/mods/6796/? ) is the 2nd enb that this has happened to. Im not sure whats happening, and I want a way to fix this. Link to comment Share on other sites More sharing options...
wax2k Posted February 16, 2016 Share Posted February 16, 2016 (edited) Maximum Path Length LimitationIn the Windows API (with some exceptions discussed in the following paragraphs), the maximum length for a path is MAX_PATH, which is defined as 260 characters. A local path is structured in the following order: drive letter, colon, backslash, name components separated by backslashes, and a terminating null character. For example, the maximum path on drive D is "D:\some 256-character path string<NUL>" where "<NUL>" represents the invisible terminating null character for the current system codepage. (The characters < > are used here for visual clarity and cannot be part of a valid path string.)Source: https://msdn.microsoft.com/en-us/library/windows/desktop/aa365247%28v=vs.85%29.aspx#maxpath That mod has some pretty long paths in its .zip file. Some of them are already quite close to that limit on their own. If you try to unpack it somewhere on your harddisk, the path you're unpacking it to will be added upon that and as soon as it tries to unpack a file in a cumulated path that is longer than 256 characters (including the filename), this error will occur. Solutions: 1. ask the mod author to provide a zip with shorter paths, especially since there are a lot of unnecessarily long folder names in there. 2. unpack the mod to the root folder of your harddrive so you at least get access to all files/folders. Then rename unnecessarily long folder names to reduce the max path length and copy the whole structure to the desired destination. There could be issues though in case some part of that mod relies on certain paths. Edited February 16, 2016 by wax2k Link to comment Share on other sites More sharing options...
Recommended Posts