IfIHadATail007

I know this is a bit tombstoned, but I wanted to add that with almost all of the new, higher-ended GPUs, Skyrim's algorithm is no longer capable "officially" detecting the hardware when you use the initial launcher function. It does indeed list your hardware in SkyrimPrefs.ini, but the GUI itself doesn't seem to have the intelligence to handle the specifics. I know that almost everyone on here wants to manually adjust settings since that's how we've always done that kind of thing with Skyrim/SSE, but I thought I'd point out that EVERYTHING that the launcher does can now be handled more easily than manual and most granularly than through the launcher's advanced settings via NVidia's GeForce Experience utility. I've quit using the launcher altogether since it's klewdgy AF, and I can tweak a lot more settings for SSE using GeForce Exp and the NVidia Control Panel (especially vSync stuff). Just and FYI for you NVidia players out there.

Double click on each mod, a panel will open up on the right, pick NEXUS MODS as the Source, then click "GUESS", now Vortex should have all the info it needs about your mods, and will check for updates when you tell it to. In future, if you download the mod with Vortex, Vortex will have all the metadata that goes along with it. You only need to do what I described if you downlaod manually of copy the file over manually. Way cool HTR, thanks!! This will take a little work since I used the copy\install process for my first go, but better than having to start over. (Not a complaint about Vortex, mind you, just a comment on my own learning curve.)

Long time Nexus user, long time NMM user and I've finally decided to jump to Vortex, starting with SSE (I'm delaying FO4 for the time being). So far, I'm digging it a lot, but the update notification issue described here is my current conundrum. I did NOT use the import function, instead opting to copy all of the mod archives from the NMM (from \Game\Nexus Mod Manager\SkyrimSE\Mods per the instructions), and have gone through the installation from scratch method (disable\delete from NMM, drag\drop into Vortex, install individually and resolve file conflicts\order). I have done no manual installations and have taken the stock suggestions that Vortex listed in each conflict state. All is goodness, and I've stated a new game, with no noticeable problems so far. The only problem I noticed as I did the installations of the individual mods was that just about every one kicked up a "cannot update masterlist" error, and I'm assuming that this is the locus of my update issue. At one point, a suggestion popped up to "Reset Masterlist", which since this was a first time run through, I went ahead and did. This solved the pop-up for a while, but eventually came back. So my question is this: Could my problem with Vortex recognizing a new version is available (and I've checked my downloaded files against last updated, finding 3 in the first 20 or so that have a new version which Vortex hasn't identified) by a result of my masterlist? Any advice\input would be helpful. Oh, and I'm going to submit a case as recommended above as well.