Jump to content

Symlink Deployment (Run as Administrator) only available deployment method


G0nk
Go to solution Solved by Pickysaurus,

Recommended Posts

Installed Vortex on my new PC to spice up BG3 only to find that I can only use Symlink Deployment, which seems to be unsupported. Vortex even prompts a user access control dialogue every time I try to deploy (which I always say yes to) but several mods outright fail to deploy when this happens. Is there a fix for this? As I cannot find any mention anywhere for this specific issue.

Link to comment
Share on other sites

  • Solution

To enable hardlinks you need to do the following:

 

  • Ensure the mod staging folder and the game folder are on the same Hard drive on your PC.
  • Ensure the Hard drive holding both folders is using an NTFS file system (removable drives often don't have this by default and need reformatting).
Link to comment
Share on other sites

  • 3 months later...
  • 4 months later...

As Pickysaurus mentioned, there are two typical causes for this. The first, and most common, is that the Staging folder is not on the same drive as the game installation. The second and less common reason is that the drive in question is not formatted as NTFS. 

To fix the first one, click Settings from the left column and then the Mods tab. Use suggest and select apply if the suggested location is in fact on the same drive. If the suggested location either does not populate or is incorrect, point it to a location on the same drive as the game installation. It's important to note that the Staging folder should not be within the game's folder (choose a location outside of the root folder). Also note that if you are moving the Staging folder, make the change in Vortex and let Vortex make the move, rather than moving the folder/contents yourself.  

It was stated above that there is no reason to click "apply" as hardlink is not available. This is not accurate. Applying the change to a suitable location will (should) then make the hardlink option available. It will remain unavailable until the change/correction is actually applied. 

The fix for the second typical cause would be choosing another drive, if possible, or reformatting the drive itself. There are guides online on how to achieve this if that is the route you're taking. 

If neither of the above fit your situation, post here and someone will take a look

Good luck!

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...