Jump to content

No deployment method available


kork1978

Recommended Posts

Posted

I'm currently trying to install some mods for X4: foundations with Vortex. X4 is installed via Steam on G:\Steam\steamapps\common\X4 Foundations. My staging folder is G:\Mods\Vortex\{game}. I read that you get this error when the staging folder and the game are not on the same hard drive but in my case they are. This is what I see in the settings:

 

 

 

There is a fix bubble that tells me that the folder is not writable, however the message is less than helpful as I should give write permissions to "[object promise]".

 

 

 

The same error message is shown for all deployment methods. How could I fix this?

 

Using Vortex 0.18.12 on Windows 10 Pro.

Posted

That means that you need to have your MOD STAGING FOLDER on the same drive as your game.

 

Read about it in the knowledge base, at SETTINGS------->Knowledge Base--------->Deployment Methods

 

Are you running Vortex or any of your games as ADMINISTRATOR?

If so, don't

 

 

Vortex-Staging-Folder.jpg

Posted
  On 7/4/2019 at 7:55 PM, HadToRegister said:

That means that you need to have your MOD STAGING FOLDER on the same drive as your game.

 

Yes, as I wrote both are located on the G drive. And I don't run the game or Vortex as administrator. I'm also a bit confused about this "[object promise]" thing in the help message. Shouldn't it display some folder name there?

Posted
  On 7/4/2019 at 8:33 PM, kork1978 said:

 

  On 7/4/2019 at 7:55 PM, HadToRegister said:

That means that you need to have your MOD STAGING FOLDER on the same drive as your game.

 

Yes, as I wrote both are located on the G drive. And I don't run the game or Vortex as administrator.

 

 

Oh wait.

Do you use Windows Defender?

 

If so, turn off that Ransomware feature

 

Posted
  On 7/4/2019 at 8:38 PM, 1ae0bfb8 said:

is the directory or files within it marked as read only?

 

I checked the permissions and my account has Full Control access over all involved folders.

 

 

  On 7/4/2019 at 8:38 PM, HadToRegister said:

Oh wait.

Do you use Windows Defender?

 

If so, turn off that Ransomware feature

 

It is turned off.

 

The thing is, Vortex worked in the past, but after I upgraded to the latest version I got this error.

Posted

I have no idea. Looks to me like the dialog wanted to print some javascript object (at least promise is a thing in javascript). But I don't know the code. Another thing, I just checked the logs and found this:

Thu, 04 Jul 2019 21:06:14 GMT - info: hardlink deployment not supported due to lack of write access _bitField=0, _bitField=1, _branchesRemainingToCancel=1, _bitField=1, _branchesRemainingToCancel=1, _bitField=1, _branchesRemainingToCancel=1,
_bitField=1, _branchesRemainingToCancel=1, _bitField=1, _branchesRemainingToCancel=1, _bitField=167772160, _branchesRemainingToCancel=58, _rejectionHandler0=[appid=228980, gamePath=c:\program files (x86)\steam\steamapps\common\Steamworks Shared, 
lastUpdated=2019-07-04T21:04:34.000Z, lastUser=76561198010387148, name=Steamworks Common Redistributables, appid=1046030, gamePath=G:\Steam\steamapps\common\Islanders, lastUpdated=2019-07-04T21:04:34.000Z, lastUser=76561198010387148, 
name=ISLANDERS, appid=230290, gamePath=G:\Steam\steamapps\common\Universe Sandbox 2, l

Could Vortex be confused by this Steamworks thing? Steam insists to have it installed and it insists to have it installed on the C drive.

Posted

So I tried for Kingdom Come: Deliverance, which is a GOG game, there it works. I also tried for Fallout 4 which is on Steam - no deployment methods available. So it must be something with the steam games (maybe with that damn Steamworks thing).

Posted
  On 7/4/2019 at 9:39 PM, kork1978 said:

So I tried for Kingdom Come: Deliverance, which is a GOG game, there it works. I also tried for Fallout 4 which is on Steam - no deployment methods available. So it must be something with the steam games (maybe with that damn Steamworks thing).

 

Are you updated to as STABLE release, or Beta release?

 

If you're updated to a Beta release, I'd roll back to a stable release and see if that fixes the problem, because [object promise] looks like Code Placeholder rather than the actual Error Message that should be showing.

 

 

I'd report that as a bug

Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

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