Jump to content

Nagev

Staff
  • Posts

    83
  • Joined

  • Last visited

  • Days Won

    1

Nagev last won the day on August 7

Nagev had the most liked content!

Nexus Mods Profile

2 Followers

About Nagev

Profile Fields

  • Staff Role
    Vortex Developer
  • Country
    United Kingdom

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Nagev's Achievements

Enthusiast

Enthusiast (6/14)

  • Dedicated
  • Reacting Well
  • Problem Solver
  • First Post
  • Collaborator

Recent Badges

17

Reputation

16

Community Answers

  1. You basically have to make sure that Steam is started up and logged in with the user that owns the game and the "You're trying to run a Steam version..." error will go away when running obse directly. But yes, having it crash at the exact same location does highlight a mod specific issue.
  2. Hi there, this is down to a bug we just fixed. Will be releasing this as part of 1.13.0-beta.4 https://github.com/Nexus-Mods/vortex-games/pull/141
  3. Game freeze/lock on alt+tab/minimize is a common issue with Oblivion and Skyrim too I believe. Can't say for sure what may be causing the game to minimize, but it's not Vortex (Unless you're downloading/installing mods in the background). You can confirm this by running `obse.exe` without starting up Vortex.
  4. Hi there - why do you suspect Vortex is the culprit in this case? Vortex only grabs focus if you're actively downloading mods from the website. Any in-game issues are always down to the mods you have installed, or potentially a different application grabbing focus.
  5. Nagev

    Plugins

    It's also possible libloot wasn't able to parse those plugins correctly. Can't do anything without log files and the list of mods.
  6. > closing the application doesn't help If the application isn't running, there's no way for it to eat your resources. This isn't a Vortex issue.
  7. Hey - no I meant Vortex 3rd party extensions, game extensions, API extensions, etc. Can view which ones you have installed through the Extensions page inside Vortex. Vortex's state is located separately from the actual application. State is stored in `%appdata%/vortex`, as long as you back that up alongside your mods and downloads you should be able to keep your data. That being said, I can't guarantee that just re-installing Vortex would fix anything; it's more likely that your OS itself is corrupt in some way. run `sfc /scannow` in a terminal window to give Windows a chance to fix itself.
  8. Then I'm afraid we're at an impasse as I can guarantee that the official Vortex installer contains no malicious code whatsoever. As Zanderat mentioned, the issue is unique to your system. We've never had any reports of Vortex installing Windows updates/AMD drivers or anything of the sort. The recent update (I'm assuming you're using the 1.13.0-beta.3 release) would've never caused the issues you're describing. On the other hand, Vortex "removing itself", has been encountered by users that were running the application through the Vortex installer itself rather than the application shortcut (causing it to re-install every time they would run the installer). Alternatively there have been instances where some cloud storage services would revert Vortex changes (removing the `%appdata%/vortex` folder); so if you do use any sort of cloud storage solution, make sure it knows to leave Vortex's data alone. Please note that I can't rule out hardware failure, especially given that you're encountering BSOD. Out of curiosity, which 3rd party extensions do you have installed?
  9. Hey again, didn't feel right to leave you guys with this issue over the weekend so I found a workaround. Made an improvement to the Clear Update extension which will help in this instance. 1. Please ensure you've downloaded version 1.0.3 of the Clear Update extension. (The update should become available within the next 15-20 minutes) 2. Choose to ignore the update for the mods you've confirmed are having this issue, and wait for the version column to clear up. 3. Once you confirm that the columns have cleared correctly, run the full update check. 4. You're done.
  10. Hey guys, looks like I'll need to write-up a state verifier to clean-up leftover update metadata. Will have that in beta.4 which will be released Monday next week at the latest. Sorry you're still affected by this
  11. Hi there, the file conflicts and missing masters notifications will never be suppressed by core Vortex functionality; community extensions however can potentially cause that. Although I doubt any extension developers would decide to do that, can you guys give me a list of 3rd party extensions you have installed? Also please specify the version of Vortex you're using. The number of suppressed notifications isn't a relevant indicator, given that many game extensions may suppress some of their notifications based on the version of the game itself. e.g. Starfield will suppress the ASI loader notification past a certain game version. If Vortex increments the number of suppressed notifications on its own - that's the game extension doing it explicitly.
  12. Hey Kilo64, The beta.3 update should've indeed fixed the incorrect update notifications as I highlight in the below .gif. I'm pretty certain that the incorrect update notifications on your end may be down to some items hanging in your state. Can you please record a short video or gif which still exhibits the false update notification behaviour to see if I can spot the issue? Please note that some mod update chains are just broken beyond what Vortex can handle, so some mods will always display the external update link icon; but that's down to the lax versioning requirements when uploading/updating a mod on the website.
  13. Hi there - Vortex is an open source project https://github.com/Nexus-Mods/Vortex any sort of tampering in the official code will be immediately apparent to everyone using the software (over 100k daily users and developers). Unless you have sourced the application outside of the Nexus Mods site/the official Github page, Vortex's functionality would never cause the issues you described. Are you perhaps confused by the Fallout New Vegas sanity checks extension which mentioned you may need to update your AMD drivers for the game to function correctly?
  14. Hey all, thanks again for reporting this issue. Good news is - the bug has been fixed; bad news is we can't release anything on Thursdays as we can't provide support over the weekend. Beta.3 will be released early on Monday to fix this, in the meantime please just ignore any update notifications that point you to the website asking you to choose the update yourselves.
  15. Thanks for that, looks like it's the non-semantic version comparison improvement - will have a look and let you guys know once we fix it.
×
×
  • Create New...