Jump to content

vimesUK

Supporter
  • Posts

    7
  • Joined

  • Last visited

Nexus Mods Profile

About vimesUK

Profile Fields

  • Country
    United Kingdom
  • Favourite Game
    Civ No Man's Sky Cities Skylines

vimesUK's Achievements

Rookie

Rookie (2/14)

  • First Post
  • Conversation Starter
  • Week One Done
  • One Month Later
  • One Year In

Recent Badges

0

Reputation

  1. Thanks, somewhat worked. It would not import from MO2, states that it could be portable, but it wasn't. Did work by importing from the Fallout stored mod folder, second option. But then it got messed up as it moved those files from MO2 and not copied them. It also placed them directly in the FO4 data folder. Took a lot to get MO2 back working.
  2. Hi I noted on the Vortex page is a link to click on to offer support if moving from another mod manager. However when using the link there is no text or anything shown within that section. Is there a known procedure that could make things a little easier to migrate over..? Also I see that there has been a beat recently offered, but where would that be downloaded from..? Or would it be a matter of installing the latest stable and, perhaps, updating to the beta from within that, if wanted..? Migration from a previous client Thanks
  3. I'll need to check the things noted in the first response as to what settings are applied.AFAIK my staging folder is on the same drive as the game is installed but, as it is for me, is I sub to a mod which is then handled by Vortex the pak file of that mod ends up within the games mods folder. Other factors might be working, but I'll know more when I get the chance to look. A misunderstanding on my part could be when I have combined mods using a utility that places the combined one within the games mods folder and I manually add that to Vortex, without first moving it from that folder. At that time Vortex will install it but replicate it as the install file is then marked as a Vortex backup. A change will be needed on my approach.
  4. Thanks for your detailed reply. Hopefully I'll have some time over weekend to test out the deployment method used against that of what you have kindly illustrated above. Most probably it will be there that my issues are found. That would not have been noted as an issue except for the game noted loading mods with the word "pak" within the file name and not just the extension.
  5. Just to let you know that whilst using Vortex, and its created backup files in place, the game will still try and load the backup file. It is the only game that I am aware of that will try and load a file with the word "pak" within the file name and not just the extension. So, as an example........ alchemist_Globals_Creature+GCreatures Life 150+GCreatures Predators Danger Dangerous+GCreatures Predators .pak.vortex_backup the above file is a combined number of mods and whilst Vortex created it as a backup, which is fine, it still loads even though the extension has changed. On noting the above someone else tried the following..... The game still loads those PAKs. I just tested by renaming a quick start mod from Mod.pak to Mod.pak.off and because .pak occurs in the name, the game loads it. perhaps if the file name of the backed up files no longer contained the word "pak" they would be fine and not loaded. EDIT: Just to add.... If you delete the mod within Vortex it removes the pak file from the game BUT it leaves the created backup file there and so that backup file is still being loaded with the game. Thanks
×
×
  • Create New...