HardwareSc8

Tab works fine for FNV, FO4, Oldrim, and SSE. At least for me.

Doubtful. It did that error for me as soon as I switched to FO3; I didn't even get to the plugins tab. There's artifacting in the code somewhere, from something else.

Yes. Check the news posts on any Nexus game page.

Hmm...well, that would explain the crash, if it's looking for an .esp that never existed on your system, but that doesn't explain why it's looking for that .esp... Let me try and replicate that, see if it happens to me, too. EDIT: Yep, I get the same error for the same .esp that I've never downloaded. EDIT 2: And if you ignore the error and try to continue anyway, the render crashes out.

If you don't have monthly-membership status, you have no option besides going to the page and manually starting the download yourself. Downloads from within Vortex will only be available to Premium members.

Given that Tannin has stated that .bsa extraction was the worst mistake he made with MO, probably not... My guess is that some sort of conflict detection will be implemented along with per-file override functionality somewhere down the line.

Oh. Derp. That's why I've been such an idiot trying to explain this... I assumed you were part of the test group and, therefore, looking at the program. Mea culpa...

In a practical sense, the only effect that Vortex's Mods tab has on plugins is determining which ones show up as installed, i.e., available to activate on the Plugins tab. Changing the order of the plugins on the Plugins tab will do nothing whatsoever to the Mods tab; they are completely separate entities. I think, though (and this may be a linguistic issue), what you're asking is: does Vortex sort the mods on the Mods tab by whether they have a .bsa or not? No, it does not. Or at least, I haven't noticed an option to that effect yet. By default, it sorts your mods on that tab alphabetically by the first word of the mod name. While there is a column on the Mods tab named Install Order, it is hidden by default, and at least right now for me doesn't show anything anyway. Probably means that particular bit of code hasn't been implemented yet... EDIT: After rereading that last post, I should probably clarify: The only way the sort on the Mods tab is going to change is if you do something manually to change it - pick a different sort such as name or status, etc., or install a new mod.

Just to clarify, which Vortex tab are we talking about here, Mods or Plugins? I don't want to babble on about the wrong subject again...

I wonder if maybe I screwed up somewhere in my import process and derped the md5 hash on my files... Hmm...have to investigate this. Well, as long as it's just me that's borked, I can work around it.

Okay, emotions aside, this is a problem that can be dealt with. Somewhere in your UI, you've got a setting that got messed up, or something. Mine shows my plugins in their actual load order, exactly like MO2. Now, I will admit that I've clicked around on just about everything, so I might have changed something from the default; I don't remember... The first step to try is to make sure that the Mod Index column is visible on the Plugins tab. Then, do an ascending sort by Mod Index. The order will then be the actual load order that the game's engine is going to use.

I actually haven't heard anything one way or the other about the open release.

It's probably not FCO. Vortex has been having issues dealing with FOMODs, particularly the older (pre-NMM) versions, like what most of the NV mods I've dealt with recently have.

I have noticed that what b3snik describes about not getting asked about replacing old versions with new ones happens to me with every mod I imported from MO2 for Fallout 4. It seems like Vortex doesn't really recognize the mod/version on import.

Oh, sorry. Guess I was confused, too... No, as far as I know the "loose files over .bsa" behavior is hard-coded into the game engine, so no, nothing you can do will change that.

No, the tabs stick to whatever sorting scheme you've got selected at the top of the window; by default in the Mods tab, alphabetically by name. The only way that would change is if you selected another way to sort them, or added new mods.

Basically, it works like this: If you want a file from B (like a texture, say), let's call it "C.dds," to overwrite the file C.dds in A, you would set up A to load before B in the Mods tab. Therefore the file C.dds that the game reads as installed is the one from B. As far as it's concerned, the C.dds from A doesn't exist at all. No matter what order the plugins are in, only the C.dds from B is going to load in-game, because as far as the game engine can see, it's the only one there. So, no, plugin ordering and rules have no effect whatsoever on what assets are installed by install ordering and rules.

And also, sometimes Vortex isn't really good about taking the red lightning bolt away; the conflict may be resolved but it still shows as red.

Or, we could install New Calibers and get an actually useful bullet size...

The point of this alpha test was to throw users in with no guides, no YouTube videos, no instructions at all... Probably, when it goes open Monday, then some instructions will be forthcoming.

Unless you're using a guide (e.g., STEP) there ISN'T any tool that I'm aware of that will tell you what order to place conflicting mods in. The thing is, you have to figure out what files are conflicting, and order the mods based on what you want to take priority.

I've gotten it after attempting a DD:DA install; reported it through the crash-report button on the popup.

Qapla'!

Hm. I like that last idea...It would also make finding updates easier.

Hrm. I installed the Tactical Armor just fine before I was even made aware there was a problem, so I'm afraid I apparently can't help much with this issue...