Jump to content

Recommended Posts

Working on getting the unofficial patch downloaded for VTM Bloodlines. Once I finished downloading through Vortex, it told me the mods can't be deployed. Tried opening the game with and without the mods enabled and it crashed instantly. I would have used the "apply fix" button but it's grayed out, and I don't know how to approach the solutions it gives me.

Link to comment
Share on other sites

Forgot to mention - the issue it gave me was saying that the user account needs to be given write permission to the program files in the computer. No idea how I would give myself permission to my own files

Link to comment
Share on other sites

Forgot to mention - the issue it gave me was saying that the user account needs to be given write permission to the program files in the computer. No idea how I would give myself permission to my own files

 

You probably have all of your games installed in the WORST, Most Overly Protected Folder in Windows

 

C:\Programs Files (x86)\ which Microsoft stupidly protects against itself to the point where things are barely usable

 

Your Mod Staging Folder needs to be on the same drive as your game, then you need to check which DEPLOYMENT METHOD you have enabled

 

 

Vortex-Staging-Folder.jpg

Link to comment
Share on other sites

 

Forgot to mention - the issue it gave me was saying that the user account needs to be given write permission to the program files in the computer. No idea how I would give myself permission to my own files

 

You probably have all of your games installed in the WORST, Most Overly Protected Folder in Windows

 

C:\Programs Files (x86)\ which Microsoft stupidly protects against itself to the point where things are barely usable

 

Your Mod Staging Folder needs to be on the same drive as your game, then you need to check which DEPLOYMENT METHOD you have enabled

 

 

Vortex-Staging-Folder.jpg

 

So I created an additional steam library folder under D and moved the Vortex app files there as well. Here's a screenshot of the dialogue when I changed the mod staging folder to the new one...

Link to comment
Share on other sites

 

 

Forgot to mention - the issue it gave me was saying that the user account needs to be given write permission to the program files in the computer. No idea how I would give myself permission to my own files

 

You probably have all of your games installed in the WORST, Most Overly Protected Folder in Windows

 

C:\Programs Files (x86)\ which Microsoft stupidly protects against itself to the point where things are barely usable

 

Your Mod Staging Folder needs to be on the same drive as your game, then you need to check which DEPLOYMENT METHOD you have enabled

 

 

Vortex-Staging-Folder.jpg

 

So I created an additional steam library folder under D and moved the Vortex app files there as well. Here's a screenshot of the dialogue when I changed the mod staging folder to the new one...

 

 

You only need to move the Mod Staging Folder to the same drive as the game, there's no need to move the Vortex APP.

 

OK, WHERE do you have VTM BLoodlines installed right now?

 

When you created the additional Steam Library Folder on D:\, did you install VTM bloodlines on it?

 

Also,

 

D:\Vortex\Vampirebloodlines\mods\

 

is a terrible terrible path to use, because vortex will stat putting any other games mods in that folder to, so eventually you're going to end up with...

 

D:\Vortex\Vampirebloodlines\mods\skyrimse\mods\

 

D:\Vortex\Vampirebloodlines\mods\stardewvalley\mods\

 

Etc.

 

That's why I posted my example, it should be \MODS\

 

And Vortex will create the GAME folder afterwards

 

 

Link to comment
Share on other sites

 

 

 

Forgot to mention - the issue it gave me was saying that the user account needs to be given write permission to the program files in the computer. No idea how I would give myself permission to my own files

 

You probably have all of your games installed in the WORST, Most Overly Protected Folder in Windows

 

C:\Programs Files (x86)\ which Microsoft stupidly protects against itself to the point where things are barely usable

 

Your Mod Staging Folder needs to be on the same drive as your game, then you need to check which DEPLOYMENT METHOD you have enabled

 

 

Vortex-Staging-Folder.jpg

 

So I created an additional steam library folder under D and moved the Vortex app files there as well. Here's a screenshot of the dialogue when I changed the mod staging folder to the new one...

 

You only need to move the Mod Staging Folder to the same drive as the game, there's no need to move the Vortex APP.

 

OK, WHERE do you have VTM BLoodlines installed right now?

 

When you created the additional Steam Library Folder on D:\, did you install VTM bloodlines on it?

 

Also,

 

D:\Vortex\Vampirebloodlines\mods\

 

is a terrible terrible path to use, because vortex will stat putting any other games mods in that folder to, so eventually you're going to end up with...

 

D:\Vortex\Vampirebloodlines\mods\skyrimse\mods\

 

D:\Vortex\Vampirebloodlines\mods\stardewvalley\mods\

 

Etc.

 

That's why I posted my example, it should be \MODS\

 

And Vortex will create the GAME folder afterwards

 

 

 

Ok so:

The game is currently installed under D:\ within the new Steam Library Folder. The Vortex app itself isn't in D:\, but the file contents. Are you saying to make a new folder for \MODS\? There isn't a preexisting one within the Vortex files. I only have individual mod folders within the file for each game I use with Vortex.

Also potentially useful information is that I had never had difficulties with mod deployment when my game files + Vortex files were all located in C:\Programs Files (x86)\. Not sure why this specific game set off the alarm.

Thanks for your help, sorry if I'm just confused lmao.

Link to comment
Share on other sites

Is D:\ a removable drive? If so it may not support the links required by the deployment method you want to use.

Yes, it is -- would that give it the same protected nature as C:\Programs Files (x86)\? If so, maybe I should keep stuff on C:\ and remove it from Programs Files.

Link to comment
Share on other sites

 

Is D:\ a removable drive? If so it may not support the links required by the deployment method you want to use.

Yes, it is -- would that give it the same protected nature as C:\Programs Files (x86)\? If so, maybe I should keep stuff on C:\ and remove it from Programs Files.

 

 

If the drive has a FAT32 or ExFAT file system it won't support symlinks or hardlinks (required for Vortex to use it as a staging location). If there's nothing else on the drive it might be worth backing it up, then reformatting it to NTFS.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

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