Jump to content

Grestorn

Premium Member
  • Posts

    616
  • Joined

  • Last visited

Everything posted by Grestorn

  1. @Impact88: I don't necessarily disagree with your request, but I don't think that you'll see a measurable difference in performance. The fact that a process exists and that some memory is applied to it, doesn't necessarily mean that it's actually using any of the resources while being idle. Also, you are aware that you can start the game directly without using Vortex?
  2. There are not 4 copies. Just two (the archive and the installed version). If you import a file into Vortex manually, you create a copy, true. But that's your own doing. You can delete the original, if you want. If Vortex would delete the original by itself, then I would agree that this would be more than questionable.
  3. The download screen aggregates all downloads for all games, while the Mod screen only shows the installed mods for a single game.
  4. What do you mean with 'install manually'?
  5. On A:? Are you sure? I don't think you can use A: in Windows. But honestly, I've never tried. The download directory is set here: This can be set onto ANY disk drive (doesn't have to be the place the game is installed to). Vortex saves the downloaded archives there. The mod staging path is where the mods are installed to (unpacked, FOMOD installer started). This must be on the same disk drive as the game, but outside of the game directory:
  6. @sopmac: No, Vortex doesn't need to installed on the same drive. It should be installed on c: in the default location. Only the mod staging path needs to be on the same drive as the game. The download path can be anywhere, however.
  7. Well, it seems to work for me. Could be game related, though. Or a temporary outage of Nexus?
  8. Does the link in the property panel of the mod work correctly, i.e. brings up the correct page?
  9. It looks like to set the Mod Staging Folder into the game directory itself. The mod staging path has to be on the same drive as the game (C in your case), but not in the game directory. Since you seem to use the GoG version of FO:NV, you might have to change the access rights for the game's installation directory. Could be that you only write there with admin rights, which is not a good thing.
  10. It's certainly not normal. Where is your game located? On an SSD, a mechanical HDD or even on a network drive?
  11. Well, the error message was created by .net which has certain security measurements in place to deny loading dlls ("assemblies") from a network path. This is put into place by Microsoft for good reason. Why that actually affects you is quite puzzling, but noone programmed that intentionally. So yeah, let's just f... Vortex, of course. People these days just don't have any manners anymore. Actually, you really should not use Mod Organizer 2, since it has been written by the same f...er as Vortex.
  12. Where did you install Vortex to? C:\Applications? Why? Windows itself seems to have an issue loading binaries from there, because it's deemed unsafe. yis this directoy a mounted network drive by any chance?
  13. Use the "Deploy Mods" button on the Mods page. If that doesn't help, you'd have to reinstall the mods. However, are you sure you've installed them through Vortex? It sounds to me like you just use Vortex to manage an existing mod setup, which you have created with another mod manager, which is bound to cause problems.
  14. As a general advice: Stay clear of so-called "security suits", "optimizing suits" and other voodoo software. Including virus scanners. They always tinker with the system in an unpredictable way, often ruining basic system functions on the way. Many, if not most problems people have with Windows - especially when updating - are caused by these "security tools". These days, Windows is quite competent to protect and manage itself, if you just let it do its job. Of course, it still can't protect you from bad mistakes, like starting an executable from an unknown source, but that's always on you anyway. A third-party virus scanner just gives you a false sense of security, which makes people think "oh well, I can just start this attachment on this mail, I'm safe, because I have this security software installed!" ... and BAM!.
  15. Unless Nexus itself changes the way the download links work (and that's unlikely), there's nothing Votrex can do about it. Which mod you're actually download is controlled in the Nexus website (THAT's where you click the link), and this link gets invalid after a while. Vortex is just not able to fix that on its own.
  16. It's not a list of downloads (which is what a browser is showing) but a list of mod archives in the download directory. And I'm pretty sure that there is a warning when deleting one of those files.
  17. Simple: Just use the built in virus scanner in Windows. There is just NO reason to use a third-party product. It only causes problems and gives you a false sense of security.
  18. I don't get where you deleted files? If you update, you either replace the existing mods in Vortex or you end up with new entries for the already existing mods. In the latter case, you just disable or even remove the previous versions and should be fine. In no way you have to manually delete any files UNLESS you installed the mods manually (without using Vortex) in the first place.
  19. The issue that the download of Vortex ends up with the wrong file extension is still a mystery. That shouldn't happen, and for the vast majority it doesn't. It would help to get to know some details about the system of the affected people, to find a common denominator. Like the browser, the virus scanner etc. I'd suspect the virus scanner, it sounds like it doesn't like the executable and just renames it so it can't be executed. So please tell us something about your system!
  20. The Bethesda Launcher is known to alter the list of plugins. Don't use that. Just go to the "Plugins" Tab in Vortex and reenable all your plugins in there, and you should be fine.
  21. That could actually be an issue. Please use Vortex to purge all mods. Fix your Windows time. Reboot. And then click "deploy mods" again in Vortex. See if that makes any difference.
×
×
  • Create New...