HylianSteel

You can... which is true, and I do... but that still defeats the purpose of blocking the tag if most mod authors don't include the tag from the start.

To weigh in a bit, it more or less looks like the issue is that Reshade presets aren't getting the Reshade tag applied to them when the mod authors creates them. So even if you block the Reshade tag, those mods will still be visible. About categories though, afaik, there isn't an option to block a whole category. Or maybe I just missed it somewhere.

I've verified with two separate mods (newest versions and the second most recent versions of each mod) and I can confirm that fomod installer support is a bit broken in 0.15.5. Mods without fomod installers install just fine afaik. https://imgur.com/a/ihkRrJu

TLDR: Vortex 0.15.4 updated to 0.15.5 without issue! :laugh: So, it's been a little over a month and I've got an update. Fresh installing windows between here and now has helped (not completely though), but I think I've actually found the source of my woes: fast startup in Windows 10. For those that don't know, with fast startup turned on in Windows 10, your computer doesn't actually power off all the way when you click shut down. I turn my computer off every night (via shut down) and then flip the power strip switch as well. Since I do this, I've really been causing instability in my system since my RAM wasn't actually getting cleared before power loss. I'm 100% certain that that's been the real issue all along. @DarkDominion You can try this if you like. head to Control Panel\Hardware and Sound\Power Options\System Settings and disable Turn on fast startup (recommended), then restart your computer.

I've got an update.... one that i think clears vortex's installer of guilt. Origin (The EA Gaming platform) auto updated today and failed just like Vortex's installer does. Unless they use the same kind of installer and said kind of installer has a bug causing this, i'm lead to believe that Win 10 (or more precisely, my system itself) is at fault.

Status update. I've tried for nearly another hour to get vortex's installer to error out again, but I've had no luck so far. I'll try again tomorrow possibly.

This is rather strange. I've redone this a couple times to successfully cause the error, but old-uninstaller.exe is only in task manager for a fraction of a second. During that time, almost instantly, the vortex directory is emptied and the setup error pops up. Not once has UninstallVortex.exe been present during the error so I've had no luck so far in even using lockhunter on it. Edit: another side note unrelated to what we've discussed. Process Monitor is claiming that "C:\Program Files\Black Tree Gaming Ltd\Vortex\Vortex.exe" "C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar.unpacked\bundledPlugins\gamebryo-plugin-management\async.js" is causing a Buffer Overflow when vortex is launched. I don't know if that matters to you, but i think it's worth mentioning just in case. Edit 2: my last edit probably doesn't mean anything. reinstalling vortex again and running Process Monitor now claims that "C:\Program Files\Black Tree Gaming Ltd\Vortex\Vortex.exe" itself is causing a buffer overflow. Edit 3: It actually seems that a fresh launch of Vortex causes vortex.exe to be listed as the source of a buffer overflow. switching games after that launch (Skyrim SE to Fallout 4 or the reverse) causes async.js to show as the source of the buffer overflow.

I've got Process Monitor up and running and set some filters to see what's happening when I run Vortex (checking for and updating mods, enabling and disabling mods, game searches, etc.) and close it. I waited a couple minutes to see what happens. For the heck of it, I tried rolling back to 0.15.1 with the installer from github. The install error happened again. this time, without updating through vortex or anything. I've got a log and screenshot for you to check out then. you're probably better at diagnosing this than i am. https://www.dropbox.com/s/u3aeye1jhpy9psc/vortex%20issues.7z?dl=0 Edit: Clicking abort leaves the installer in such a state that it'll never finish or close on its own.

I've got doubts that it's Windows Defender or Malwarebytes since I've got Black Tree Gaming Ltd and my mods directories excluded from both of them. It could very well be the Spectre and Meltdown mitigation's causing the problems for all i know. I'll monitor vortex for a bit and see what's happening hopefully. I agree in that something is holding it up. This really only has happened because I updated vortex through the app first. So, If the updater inside vortex itself isn't giving Vortex enough time to properly shut down (thanks to vortex itself or something else), shouldn't there be a way to make it so that the installer pauses for a couple seconds before starting? some checks to see that vortex is actually completely shut down first? Edit: nothing major or anything yet. I only noticed that vortex itself still has processes going for about 5 or so seconds after closing it down. gonna keep looking.

probably not a good idea. don't .esl's load before .esps and whatnot? it'd kinda defeat the purpose of a bashed patch altogether.

Hey Tannin, I just updated to 0.15.2 from 0.15.1 (installation through Vortex itself) and it failed to install Vortex.exe again. I'm gonna grab the installer from github and see what happens. Edit: Aha! Caught the error i had last time when trying to install through the installer on github. https://i.imgur.com/bD3a4Re.png. clicking retry fails as i assumed it would. clicking ignore emptied the whole Black Tree Gaming Ltd folder out just as it did last time. running the installer a second time works perfectly fine though just like last time. Edit 2: side note, you still have 7-zip listed as 16.4.0 in the third party libraries list even though you included 18.05 with this update.

https://github.com/Nexus-Mods/Vortex/releases

I checked both Windows Defender and Malwarebytes and neither have anything in their logs about Vortex. The upside is that I reinstalled 0.15.0 and let it update itself to 0.15.1. It completed without issue this time.

So far, 0.15.1 has been pretty good. updating to 0.15.1 was a slightly bumpy road though. I had used Vortex 0.15.0 to download and install the update and everything seemed to be fine at first until Vortex didn't relaunch. It turns out that the installer had failed to actually put Vortex.exe in C:\Program Files\Black Tree Gaming Ltd\Vortex. I had to download the installer from github. Running the installer the first time gave me an error about being unable to write to the folder (it was referencing the uninstaller already in the folder at this point and I wish for the life of me that I took a screencap) and gave me three options. Skip, retry or abort. I choose skip and the installer finished. Vortex still won't launch and my desktop shortcut is broken. I go back into Vortex's folder to find that this time, there are no files at all in C:\Program Files\Black Tree Gaming Ltd\Vortex. Running the installer a second time worked like a charm though and all is well. Edit: Here's some system info so maybe we can identify similarities between myself and other users who may have experienced the same thing OS: Windows 10 ,Version 1803 (OS Build 17134.81) Antivirus: Windows Defender and Malwarebytes Intel i7-3770k with updated microcodes for Spectre and Meltdown Nvidia GTX 1070, driver version 398.11 Samsung EVO 850 SSD 16GB DDR3 RAM

If I've installed a mod recently, close vortex at some point and then open it again later on, Vortex has seemingly forgotten that the mod is installed. The mod reappears in the downloads tab with install as a selectable action. The mod is in fact still installed, so when you try to install again, you naturally get the prompt to cancel, rename. or replace. Replacing the mod will fix it and i haven't had a mod become a repeat offender later on. Other times, replacing the mod doesn't actually reinstall the mod either. Doing a second reinstall will actually install the mod. This has happened about 3-4 times since I've first started using Vortex around a month ago. The games i'm currently testing with and I've experienced this bug with are Skyrim Special Edition and Fallout 4.

Please go here and download the latest version of NMM so you can go back to using what works for you.

what version of FNVEdit are you using?

https://github.com/Nexus-Mods/Nexus-Mod-Manager/releases

From the official site. I've got this feeling that this update will launch with the GotY edition on September 26th.

I think there is already a mod for that, check nexus, otherwise id suggest maybe looking for the UIWidgetBlueprint thats responsible for drawing those elements and remove it from there Try this one: No Exclamation Marks (with options) by crazyjackal http://www.nexusmods.com/masseffectandromeda/mods/438/? or this No New Notifications by alineinabook http://www.nexusmods.com/masseffectandromeda/mods/240/? It just goes to show, I should of searched first instead of posting. Thanks for pointing those mods out to me.

With the news about Mass Effect Andromeda no longer getting patches or Single Player DLC, now is the time to invest in modding i'd say. Would anyone have any idea how to remove the exclamation marks from Journal, Codex and Skills through modding? I'd love to have someone make that as a mod, or point me in the right direction so I can make it myself.

Thanks, cdcooley. That clears it up.

I don't think I worded my question correctly. This is what i'm talking about. Normally, that option is deselected. are there any cases where I shouldn't select it when packing files into an archive?

Google has failed me for the most part on finding info about compressing archives. Are there any situations where you shouldn't compress an archive with Archive.exe?

In response to post #43806040. This. I opened the Bethesda.net launcher to enter the code and noticed the Skyrim SE Creation Kit was already in my library.