Pickysaurus

Looks like the fix didn't make it into 1.11.2 either, 1.11.3 will be hitting the stable branch today which will finally put this issue to bed! Sorry for the confusion.

You may need to ask the extension developer: https://www.nexusmods.com/site/mods/375

This error is "bubbling up" from the driver/operating system and is not caused by Vortex. It's either a hardware fault, a driver issue or something on your PC interfering with the normal operation of Vortex.

I'm fine for people to tell me off if I did something wrong. However, a lot of these knuckleheads post things like this:

More.

User's response to this ban. More childish ranting.

This post seems to be becoming a target for off-topic conversation so I'll lock it for now. If you have other questions, please use the Site Support sub forum.

Download the correct version of SKSE from the mod page and it will work.

A solution is pinned right at the top of this forum:

Beta version 1.11.2 should no longer show these warnings. If you're still seeing them you simply can't be on the latest beta. 1.11.1 did have an issue where the fix wasn't actually included.

Update Vortex manually. You are probably using a super old version. https://www.nexusmods.com/site/mods/1?tab=files

I asked @Nagev about this - as you seem to be the only person having this issue.

You can try reinstalling the mod and if the message still appears it means there's another one overwriting it.

That mod is (as far as I've seen) the only one using the new BA2 formats. Vortex isn't updated to support it yet, but you can opt into the beta if you'd prefer not to see the message under Settings -> Vortex. This is noted in the mod's sticky posts FYI.

We're only 8 days into the month - with some national holidays in the UK. Sometimes it can take a little while to be processed. Don't worry, we haven't forgotten.

Moved this to a better forum as it's not a bug report. We covered this here: https://www.nexusmods.com/news/14894

Redundant means the mod either contains no files (you deleted them) or all files from that mod are overwritten by another mod in your list.

This is caused by a faulty extension you've installed. It's the Battlefleet Gothic Armada 2 one. Go to %appdata%\Vortex\plugins and delete it from there.

Collections will always install automatically. It's how the feature is meant to work. It will not deploy until the installs complete.

@Franeurysm As this relates to the same issue, I've merged it with this topic.

It seems that when Vortex is scanning for PAK files it's getting an empty string somehow. This must be some kind of weird config issue on your end. What's actually in your PAKs folder for the game?

Whenever this doesn't work it's likely to be caused by something local to your PC. We're not aware of any issues at Cloudflare or on our end.

Most users having this problem have an outdated copy of Vortex. Outside of that we need the issue reported so the Devs can take a closer look.

Your mod staging folder is probably on a different HDD to the game so you're deploying via Symlinks. This requires elevation due to how Windows works. You have two options: 1. Move your staging folder to the same drive as the game in Settings -> Mods. Then change the deployment type to Hardlinks (recommended). 2. In Settings -> Workarounds there's a way to use Symlinks without the prompt

That log entry implies you did something to disabled it. Go to the extensions tab, click "show bundled" and reenable it