Jump to content

FlamingCheeseMonkey

Premium Member
  • Posts

    62
  • Joined

  • Last visited

Nexus Mods Profile

About FlamingCheeseMonkey

Profile Fields

  • Country
    None

FlamingCheeseMonkey's Achievements

Contributor

Contributor (5/14)

  • First Post
  • Collaborator Rare
  • Week One Done
  • One Month Later
  • One Year In

Recent Badges

0

Reputation

  1. Go to "Settings" and turn off the Deploy mods on install feature. Install and enable all of your mods, solve the conflicts (you know if the conflicts are solved if there are green thunderbolts instead of red), then hit "Deploy Mods". It brings up that notification as a safety feature to make sure that you want to install the mod on another drive (which is kind of a good thing in that you know that Vortex isn't doing anything sneaky, but also bad because of it's frequency, hence the disabling of that setting option for now). As for not installing mods easily, I disagree. I find it just as easy as the other mod managers out there (used NMM, MO, and MO2), just with certain bonus features or limitations. Although, that could be because I play around with the mod manager to learn as much as possible before actually using it. What's your deployment setting set to? Because I don't recall it bring up the notifications with "hard-links". As for deployment failing all the time, what's the game directory path, Mod Staging path (can be found in Settings -> Mod Staging), and the deployment set to?
  2. Have you tried hitting "Deploy Mods" before installing the mod that is giving you trouble?
  3. Going off of the about page for Vortex, Vortex doesn't support Resident Evil 6. Vortex only supports the games that it's either made to support, or games that people have made extensions for. Currently, the only Resident Evil game that is supported is Resident Evil 2 (Re-make).
  4. The website doesn't know what mod manager you use. It simply says "Download with Vortex" because that's the mod manager that Nexus recommends using. Pressing on it will open up whatever software is assigned to open up that file type for downloading. So if you see a "Download with Mod Manager/Vortex" button, click it and NMM will open up (as you haven't downloaded Vortex, Vortex won't open as it's not installed. NMM will though since it is installed [assuming that you don't have another mod manager installed and assigned to open up the file type]).
  5. Personally I disagree. It's really bad practice to add features to a software that deliberately messes with the features/functions of another software. Also, that's the exact reason why both the Knowledge Guide and the import process tells you to uninstall the mods from NMM before using Vortex. Edit: Third sentence was referring to the issues you had encountered and not the sentence before it. Just wanted to clarify as looking at it now, it's a bit confusing as it was.
  6. I mean, if you're talking about the LOOT from a year and a half ago, than yeah. But if you're talking about the LOOT version that was released since then, your statement makes no sense. I'm not sure why, but people seem to love to blame the developers of LOOT when no one bothered to read their announcement that LOOT is changing their system and adapt to it.
  7. Without the name of the games that are missing it makes it harder to help you out. With that being said, not all games on the Nexus are supported by Vortex. While Nexus hosts mods for more than 700 games, Vortex supports 60-80 of them (not sure the exact number as I haven't bothered to check in a while and I'm about to go to work).
  8. The majority of the issues back then was because Vortex was legitimately a buggy mess. It was released to the public as an alpha around March of last year, and a bunch of people, for some reason, expected the software to work without issues. Despite the articles (that they should have read through) stating that there will be issues and to not use it unless if you don't mind using an alpha program and reporting the bugs. Then it was officially released as a beta in August and a bunch of new people starting using it, but the issue is that they tried and forced how they used other mod managers (whether it's NMM or Mod Organizer) onto Vortex. As long as you're willing to learn how to use the software properly, you won't run into as many issues that other people have. For example. Vortex relies on LOOT to hand the ordering of the plugins. With NMM you can drag and drop plugins without too much of a visual hassle (but textures not being changed at the same time as the re-ordering means that the mod may not be working properly). This also gave the user the notion of install order. Where the order of mod files (textures, meshes, sounds... etc) is dependent on install order. With Mod Organizer, you can handle the ordering of the mod files and plugins through drag and drop and it displays nicely in a red/green plus to let you know if the mod is getting overwritten by something, or if it overwrites another mod. But this granular control of the mod files, along with the ability to adjust the plugins on the fly gave the users the impression that (especially plugins) needs to be placed directly after the conflict to work fine. Vortex on the other hand uses the idea of sorting things based off of conflict, and conflict only. Which makes a lot of sense in the long run. After all, why do you need to care about the placement of a sound mod priority if it doesn't touch the three dozen texture/mesh mods? Why do you need to worry about the placement of a plugin that touches weight if it doesn't touch item placement in the world, lighting changes, and other environmental changes? As for the issues, over the past few months though, at least on Reddit, a lot of the issues that I've seen are from people importing mods from NMM, then not uninstalling the mods from NMM and purging before using Vortex. Then keep NMM open while installing and doing the ordering on Vortex, before closing Vortex and then NMM. Meaning that the plugins are still relying on NMM's list, and complain that Vortex is breaking the game. Or some version of that. Which is frustrating as hell because they post later going, "Oh, MO2 works perfectly, but I also did the proper uninstall procedure of NMM, removed NMM entirely from my computer, before opening MO2". So... basically the same thing that was needed to get Vortex running? Lovely. That, or they hate the UI of Vortex (or they say that, "Oh, Vortex doesn't have this feature but MO2 does". And that is a load of bull. Vortex probably had that feature for ages but because they used Vortex when it was Alpha or go off of what other people said when they used the Alpha version, they believe that nothing changed. True, Vortex is missing a few features of MO2, but that's probably less than three at this point, and the same could be said vice versa. But it's definitely not as many as people say it is). Gah, sorry for ranting. As you can probably tell, I've been really frustrated with Reddit users when it comes to Vortex. And it doesn't help that there are people there who immediately down vote if it sounds like Vortex is even getting the slightest of praise and up vote anyone that says anything bad about it (even if the entirely of the thing that was said is a lie, or was no longer the case since September of last year). Edit: A word was missing >.>'.
  9. As it says on the home page, NexusMods itself is a site that hosts files for games that can be modified. Just because the mod managers they created don't support all of the games doesn't mean they won't host files for said games. With that being said, the number of games that Vortex does support is expanding, slowly as it may be. Whether it's due to the development creating the extensions themselves (to allow Vortex to support the game), or due to other people creating extensions and submitting them to the dev team for publishing.
  10. Ah, okay. Another way you can do it, is that if you still have all of the archives (the path to them should be somewhere in NMM's settings), you can copy/cut and paste them into Vortex's download folder (so whatever the download path is + /{GameName}. It's just that the meta data won't be copied over so you'll have to go through the list that I had in my edit to get them.
  11. Whelp, this is actually really interesting. I did the update through Vortex within a few days of 1.0 being released and Windows Defender didn't pick up anything then, nor did it pick up anything when running Vortex (although, does Defender even check files when said program is ran?). So it's curious as to what changed. In any case, I checked what Detours is even about and according to https://www.npmjs.com/package/detour , Detour is used for routing purposes. So that can be anywhere between Knowledge Base, the dashlets, and retrieving and displaying mod information when double clicking on mods. Last update on it was 3 years ago so unless if Nexus made changes to it, it helps to close certain reasons.
  12. Oh. Well, that's lovely. You've formed an opinion on a software you've never even actually used. Great? I'm not sure what the issue you're having with importing as it sounds like it's doing what you want? Vortex is basically going, "Hey, can you confirm that you want to import Fallout 3 mods (given as '\Nexus Mod Manager\Fallout3\Mods')?". Is there no "Confirm" option or something? Can't tell due to a lack of information in this regard. As for the "Mods can't be deployed". If I recall correctly, that comes with a "More" option which should then describe why it isn't deploying. The most common reason is that the Mod Staging folder (which is set through Settings > Mods) isn't set to the same drive (and partition) as the game. Edit: Oh, also forgot to add. But did you bother to check the Knowledge Base section of Vortex? It contains articles containing information on the features that Vortex provides along with help on troubleshooting certain topics. One of them is importing. I'm going to try and summarize the steps to save you the time of reading through it. After either copying the archive files into Vortex's download folder (appropriate paths are something like .../downloads in Vortex, .../downloads/Fallout3 in File Explorer), or using import function, uninstall all mods from NMM. Run the purge function through NMM to make sure all files have been removed and game has been reset to it's original state. (Optional) Delete data folder and verify game through Steam to redownload vanilla files. Uninstall and reinstall mods so that if they have custom options, the mod will get installed properly. Once everything is installed, hit the "Deploy Mods" button to make sure mods are deployed into game folder.Note: You're going to want to deal with conflicts as you go. You'll know there are conflicts when a red lightning bolt shows up. Click on it to deal with the conflict. Things to do to make it easier on yourself when updating mods: Once mods are installed, CTRL + A to select all. Hit "Guess ID's" that shows up in the bottom toolbar that popped up. For mods that it was not able to guess the ID's of, double click to bring up additional mod information. Change "Source" to "NexusMods". Select appropriate file to grab the meta data. If it still fails, remove mod through Vortex (along with checking the archive option) and redownload mod from site to grab the metadata. Hit "Deploy Mods" after installing.
  13. If you can't find FO:NV in games (whether under Managed, Discovered, or Supported with Show Hidden Games enabled), you may have to re-install Vortex as something may have went screwy on install/update.
  14. For the most part, the developers of Vortex won't be adding in support for games (well, they aren't focused on it right now). If they did, then they would have to also add in support for other games that people pitch in, and for games that come out. With the amount of games that comes out every year, each having mod functionality, or people who find ways to mod the game, and that would end up eating away time that could be spent on making Vortex better. So Vortex Beta for example. It's been, what, a year? If they focused on adding game support that could have easily been four times as long (especially as there are so many games that can be modded that are not in the supported list, as can be seen by the games list on NexusMods home page), and Vortex would have the functionality it had around October. So yeah, they probably won't. If you know people that are programmers though, you can ask them if they would be interested in making a Vortex extension for the game, which the dev's will check over and add in the next Vortex patch. Edit: Whelp, disregard quite a bit of my message. Just read the Vortex news post. So yeah, while we can expect them to release support for games, people pitching in and creating extensions would help speed up the process.
  15. If you go to the "Mods" section of Vortex, you just need to click the "Purge Mods" button to remove the generated links from the game folder. You can then do a fresh install of the game. Afterwords, as long as the game is in the same location and you've ran it once, you should be able to hit "Deploy Mods" and run the game with all your mods installed just as it was before (you may also need to click on "Fix" when it brings up the BSA Redirection thing again).
×
×
  • Create New...