Hardlink Deployment on SMB Shares

[DefinitelyNotSade]

Hi all,

 

I have not seen someone encounter this issue yet, and I've searched through the forum to make sure. If I did miss a similar topic I apologize!

 

So I've moved and installed all my games to an SMB share on my FreeNAS box, including my Vortex mod library (downloads and setting up staging folders on the network drive).

 

(Games work surprisingly flawlessly so far for all game platforms as long you enable these two teaks (especially for Origin): One Two).

 

The only issue so far in my experience is trying to deploy my mods with Hardlink Deployment for BGS games, namely playing New Vegas right now.

 

I can safely enable one mod and deploy it, as soon as I enable and deploy a second mod I get a -4083 error code.

 

The details are such:

EBADF: bad file descriptor, stat 'Z:\Games\Vortex Mods\falloutnv\The Mod Configuration Menu-42507-1-5\textures\MCM\Check0.dds'
Error
    at Object.moveAsync (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\renderer.js:141:27)
    at C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\renderer.js:1843:152
    at tryCatcher (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\util.js:16:23)
    at Promise._settlePromiseFromHandler (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\promise.js:547:31)
    at Promise._settlePromise (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\promise.js:604:18)
    at Promise._settlePromise0 (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\promise.js:649:10)
    at Promise._settlePromises (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\promise.js:729:18)
    at _drainQueueStep (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\async.js:93:12)
    at _drainQueue (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\async.js:86:9)
    at Async._drainQueues (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\async.js:102:5)
    at Async.drainQueues (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\async.js:15:14)

So I've had to change the deployment scheme to the experimental Move Deployment option, which works so far as long as the ACL/Permissions on both the FreeNAS and Windows 10 sides have Full Control (and inherits full control), otherwise Vortex spits out permissions errors.

 

I can live with Move Deployment, but I was wondering if there is a way to implement Hardlink Deployment on network drives, to cut down on extra storage that Move Deployment takes up.

 

iSCSI is out of the question as I'm sharing the installs/data with more than one Windows 10 PC.

 

Any help is appreicated.