#1.16 Collection Issues (FO4; StoryWealth)

1 messages · Page 1 of 1 (latest)

quaint minnow
#

Vortex v1.16.0-beta.5
Attempting to install A StoryWealth (Fallout 4)

  • Most files are already downloaded from previous attempts
  • Only very large files are currently installed (e.g. HD texture mods)
  • Only enabled mod is my own pre-downgraded game binaries
    Notable video events:
  • 19:28 - Deployment Occurs during collection install
    Collection appeared to be hung afterward
  • 22:35 - Clicked resume
  • 22:38 - Post-Install: Unresolved Conflicts & Redundant Mods
    Restarted Vortex and Applied Collection Rules to fix
#

CC @edgy verge @vale jungle

#

I've had a fair bit of trouble with attempts to install this collection on the betas.
This was the first that appears to have eventually succeeded, though with the issues I'm still left wondering if it actually did install properly for stuff like binary patching.

quaint minnow
#

Cloned it into the Workshop and clicked upload

#

There's no indication that the collection isn't fully installed, so I guess the install failed invisibly?

#
  • Viewed the collection and then removed and reinstalled that mod.
  • Collection was showing incomplete so clicked resume. It didn't seem to actually need to install anything.
  • Deleted from the workshop and re-cloned.
    Still unable to upload; same error.
#

Removed the collection, leaving everything installed, then installed it again.
It did another deployment during the install, I assume due to multiple phases?
As it was deploying I was getting "Mod removed" toasts though. Is that safe to do duing a deployment?

#

I can never tell what its doing

#

do I wait? is it hung?

#

I left the collection view and then went back.
Now there's no progress bars

#

If I can't figure out how to install this collection, I feel like there must be a lot of failed installs out there :/

quaint minnow
#

Unsure why it's waiting to install

#

This time I chose to defer installs until downloads were complete. I guess that bug isn't entirely fixed.
I don't think there were any downloads necessary this run

velvet relic
#

Also had similar failures reported by team member who tried to install the collection fresh using Beta.
Asked them to share feedback but they prefered to downgrade Vortex and just get things up and running rather than trying to troubleshoot the beta.

quaint minnow
#

I'll keep giving feedback until it works Hehe

vale jungle
#

So there was an issue with binary patches/replicate for optional mods. Which is probably why cloning was being weird

velvet relic
#

Quite sure none of our optional patches use either binary or replicate though.

#

So it's live now? Starting out well.
They reverted to 1.15.x and was able to get back to normal.

vale jungle
#

1.15.x mod reference checks were flawed. If 1.16.x is stating that the references are incorrect, 1.16.x is correct.

If they're happy with their 1.15.x setup then that's fine, no need to worry about the incomplete flag, but chances are they have the wrong reference installed.

velvet relic
#

Not even sure what that means to be honest.
What reference? Could the collection itself be potentially broken then?

vale jungle
#

Not necessarily the collection, it could be the user's environment itself that has a wrong version, or at least partially incomplete data.

velvet relic
#

Well, assuming people want to use 16 forward, how would they resolve this specific issue?
I recall another of ours tried to add the collection testing beta and got some revision -1 and just reverted after things just kept cascading with isntallation pending and stuff.

vale jungle
#

They can have a look at the dependencies unfulfilled notification to see exactly which mods are considered missing/incomplete and try to investigate whether the rule in the collection.json file has been applied correctly.

Stuff like patches, installerChoices, fileList etc. Double clicking the mod entry on the mods page will show them the applied installerChoices in case those don't match up.

But easiest would probably be to allow Vortex to install the mods it considers incomplete (as long as they didn't apply any external changes to their installed mods)

#

Is the collection using the "prefer" update policy?

velvet relic
#

Since it's hard to just do 2nd hand stuff, I'll just send anyone who reports weird new issues to #🟧︱vortex going forward.

velvet relic
vale jungle
#

Basically whether the collection uses the "exact" version for some mods, or if it uses "prefer exact"; the latter can potentially break a collection if a mod's file gets removed/archived for some reason.

#

"Latest" will potentially break installerChoices/patches/fileList settings upon mod update.

velvet relic
#

Ah, don't think I use any Latest, use exact only or prefere exact.

#

prefer exact always was the default setting so only changed if I had to.

vale jungle
#

Going forward "exact only" is the default value, and we encourage everyone to use that over other update policies as it ensures it always matches that specific mod version, with no chances of forked installerChoices or defunct binary patches/replicate options

velvet relic
#

Did you also fix the whole "mod dependency missing" if you update it?

vale jungle
#

I'm afraid we couldn't reproduce it :/ cloned StoryWealth several times this morning

velvet relic
#

I mean mod dependency missing might been fixed then. Hopefully.

quaint minnow
#

And if I reinstall a mod, does it get those steps done again?

vale jungle
#

So if you open the collection.json file in an IDE or text reader, you'll notice that some mods will have choices/patches properties. Choices are the installerChoices, basically the FOMOD choices that the curator exported, patches signifies that the mod has binary patches assigned to it. hashes means that the mod was exported using replicate

#

Re-installing the mods directly from the mods page will not re-apply those

quaint minnow
#

But it will from the collection page?

vale jungle
#

To re-apply you need to install through the collection - uninstall the mod and resume the collection.

#

It will in stable yes

quaint minnow
#

Collections could probably do with some health checks or being made inmutable

vale jungle
#

beta.5 had an issue on that front but that should be resolved now

quaint minnow
#

Doing another install of StoryWealth (most mods already downloaded and installed)

#

I assume any that it does a reinstall for are due to patches and replicate

vale jungle
#

Very likely yes

quaint minnow
#

Did you experience a long UI hang when Checking Dependencies?

vale jungle
#

It's unfortunately due to the huge amount of collection rules that are exported as part of that collection.

#

It hangs for a very long time trying to dispatch those to the main process

quaint minnow
#

I got a pop-up that it was done installing, but the collection screen is still at waiting to install

#

Yeah the installs are still processing

vale jungle
#

Show me a screenie

quaint minnow
#

I'm recording a video

#

seems hung so i stopped the recording haHAA

#

the install complete screen popped up at 5:58

#

Current app state:

#

It seems to rotate logs quite frequently. wondering if there's a better place to export them from or if a long session just ends up losing logs

vale jungle
#

We definitely need to raise the allowed size for those logs

#

Which mods is it actually complaining about in the unfulfilled dependencies notification?

quaint minnow
#

I suspect these arent actually an issue and it just isnt done with the collection

#

in a previous test reapplying collection rules cleared up such messages

#

If a remote session would ever be useful I don't mind 🙂

vale jungle
#

Yeah try to re-apply the rules, it should clear that up once the collection is complete

#

I'm running another check now and may take you up on the remote debugging session

quaint minnow
#

What's the best thing to do when hung like in that screenshot? Resume?

vale jungle
#

Yep, but something odd is happening on your end - it looks like it had completed the collection, but then the progress meter reverted back to 94%

#

When did you last download those archives?

#

Beta.5?

quaint minnow
#

It was either 4 or 5. Not entirely sure

velvet relic
quaint minnow
#

yeah, it seems like it stays that way until post-install

#

Clicking resume "fixed" the install/errors, but I'm not convinced its installed properly

velvet relic
#

It is showing the right revision on my end for 16.1, but it did fizzle a lot of binary patching mods.

quaint minnow
#

Without any sort of health checks I'm kinda left guessing

#

oh duh, it tells me when it was downloaded

#

that's probably beta 5

vale jungle
velvet relic
#

That's good to hear 🙂

quaint minnow
#

Removing and re-adding the collection ends up at the same issue.
Popup says install complete, but notification still says installing and progress bar at 95% Waiting to install.
Nothing on the collection mod list is pending. All Enabled except for these 39 in disabled status (also show disabled on the main mods tab)

vale jungle
#

Oh, in that case it should just be the case of re-enabling the mods. If the collection overview screen doesn't do that on resume, try enabling them on the mods page and then apply collection rules

#

Then see if the install progress changes

velvet relic
#

The invalid primary tool I think is Bethini?

#

Not sure, but it's the one that's not a Fallout 4 mod, but a "tool" mod, that ends up showing up kinda weird in vortex due to it.

#

Those disabled stuff are our optional mods.

#

I think, not 100% on the protectron, but quite sure I made it optional at some point.

vale jungle
#

Primary tool should be F4SE I think, unless people have migrated to a different script extender/tool and I didn't notice 🤔

velvet relic
#

More would tell which.

#

Speaking of which. That one has a been a pain since we downgrade.

#

A lot of people end up getting both versions of F4SE which are incompatible with each other preventing deployment.

vale jungle
#

Top of the overview screen are definitely optional, bottom ones are required.

velvet relic
#

Ah yeah, missed that.

#

2nd half is the binary patching mods

#

actually

#

so hopefully this fixes itself once I'm done.

#

That and some replicate mods in there as well, but yeah.

vale jungle
velvet relic
#

Yeah, usually why. A few rare users do hint that there been a case of it somehow merging it. Usually we say "remove new version" but some had to remove old version and have it reinstall.

#

Not the end of the world, but yeah :p

vale jungle
#

All the hoops we have to jump through to mod Bethesda games ha

#

I downloaded and installed your collection again from start to finish btw. Really annoying that I can't reproduce what those users are experiencing

velvet relic
#

Yeah. This is one I can mostly live with though, especially the whole "accidently installed both".
It's the possible merge one that's a pain assuming they didn't mess it up xD

#

But rare enough though.

quaint minnow
velvet relic
#

I was able to replicate some issues, but it all points to the same issue I had in the past with vortex crashing on me, which I think we were able to figure out why now 😛

quaint minnow
#

The primary tool warning was probably due to me disabling everything before install

velvet relic
#

In short, once I get next update out. It should fix most of the issue of a select section of mods not installing.

#

I hope xD

quaint minnow
#

Weird that Nagev hasn't been able to reproduce this. I fairly regularly blow away my Vortex install for testing so it's pretty clean

quaint minnow
#

Also, are you doing install while downloading? that might make a difference

velvet relic
#

Also really happy that I don't have to readd everything and the collection itself remembers the settings I had for the mods (even if I have to redo the patching on it)

#

Quite sure earlier versions was not as forgiving xD

#

Since 90% is just "mark as light" it's easy enough of a process.

vale jungle
velvet relic
#

Ohh, way before that.

#

I was still on 11.6 until now.

vale jungle
velvet relic
#

Yeah, was close to adding a step to disable it due to failed installs, but 16 hopefully fixes the need for that.

quaint minnow
#

Since noticing the bugs I reported, I've been deferring installs to see if it breaks 😅

quaint minnow
#

This time I removed the collection, leaving everything installed/enabled, then restarted vortex and installed the collection

#

with install while downloading enabled

vale jungle
#

How many collections/profiles do you have and do they have common mods?

quaint minnow
#

I have very few mods that arent from testing this one collection

#

Default is supposed to be empty but I forgot to switch back to the storywealth profile

vale jungle
#

Right then that shouldn't be connected

quaint minnow
#

this is the only collection I have installed

#

Like I said, I blow it away a fair bit 😅

vale jungle
#

Right, if the revision update doesn't work, we're doing a remote session

quaint minnow
#

haha

velvet relic
#

Same ammount I'm stuck at btw 😛

#

922 xD

#

I'm like 70% done on updating stuff

quaint minnow
#

Do you want me to leave mine as-is, or cancel/remove the collection?

velvet relic
#

I'd leave it, then update later.

vale jungle
#

yep

#

Then if it still happens, remote session time

quaint minnow
#

Oh, a new aSW revision. gotcha

#

well right now its still hung mid-install

#

just restart vortex?

velvet relic
#

Yeah, there was an issue with a bunch of mods in upload. Somehow worked in earlier versions of vortex but not in later.

#

Mostly related to binary patching and replicate.

quaint minnow
#

Did you flip everything from Prefer Exact to Exact Only?

velvet relic
#

Issue was something with archives.

#

Got 4 more mods out of 19 to reinstall to fix it, then upload :p

#

Which hopefully fixes it.

quaint minnow
#

Really glad they extended the Collectionathon so I could focus on breaking vortex for a bit 😅

vale jungle
#

I'm 11 hours into this workday, so going to call it a day for now. (collection installation with downloads pre-existing is still running - hopefully I'll manage to repro)

quaint minnow
#

jeez

vale jungle
#

Speak to you later guys

#

Yeah release day ha

velvet relic
#

Good call on doing it early in the week xD

#

Btw, just 2 more. Getting there 😄
Totally forgot what I changed on these last two so I'm just pulling the file out, reinstalling, pulling back in xD

vale jungle
#

@quaint minnow, downloads were present, removed collection, started re-installing it; it just finished 😬

#

I'm even using the production build just for the sake of making sure I match your env ha

#

Drives me nuts

#

Anyway, I'm gone

quaint minnow
#

So weird

#

you sure do have a lot more plugins than I do

velvet relic
#

Seems one of the mods didn't get the archives updated properly so have to redo the deploy/upload.
But getting there 😄

#

@quaint minnow Revision 270 is up. Hopefully it fixes the issues.

#

Also trying to update it now on my test rig that had the same mods fail.

#

It asked me to remove 22 mods... I wonder what exactly considering technically no mods got changed :p

#

But no big deal there if things installs proper.

#

ohh wait I know why.

#

the 19 that failed before plus 3 more that I figured I'd enable binary patching on that failed in the past that I just kept off.

#

Figured I'd test them again now.

#

Okay... not great. So far I had mixed results with it installing...

#

Restarted Vortex to hopefully work it out.

#

I mean if I have to add a step "restart Vortex if things seems to stall" I can live with that I suppose.

#

Good news is that restart did resume downloading stuff taht seemed to have fizzled initially... oddly some stuff that shouldn't in previous revision... but oh well

quaint minnow
#

Updating to rev270 didn't exactly go smoothly 😅

#

I clicked resume a couple times in the video

#

I didn't think to start recording until midway through updating

velvet relic
#

Okay. I don't think it's working.

#

16.1 is broken.

velvet relic
# quaint minnow

Those red warnings, same as what one of our team members are showing.

#

After a bunch of restarts and stufft after the update I'm still stuck at 922 as before.

quaint minnow
#

Restarted Vortex, got a missing dependency warning for CBBE.
Told it to install, got the red error spam as above
Then prompted to install CBBE

#

Got prompted with the CBBE fomod

#

And being prompted that I'm missing CBBE again. It is installed

velvet relic
#

I just gave up and told people to downgrade.

quaint minnow
#

:(

velvet relic
#

I did what I could for tonight, fixed the confirmed issue and was able to reupload using latest version.

#

But didn't seem to fix the issue =/

quaint minnow
#

I do think the update needed a bit more time to cook.
I have a number of issues and threads in this channel that didn't get acknowledged

velvet relic
#

Tbh, pushing live before resolving these issue was a mistake I think.

quaint minnow
#

"Power user can't install collection on a clean Vortex install" should probably be a blocker

velvet relic
#

Even had a user report simmilar issues with a Skyrim collection.

quaint minnow
#

I assume they hit an update deadline

velvet relic
#

In that case whoever is in charge of that deadline...

quaint minnow
#

I wonder if some of these issues might be related to the update chain changes theyre doing on the site today

#

CBBE coincidentally has only orphaned files

velvet relic
#

Downgrading to 15.2 I was able to get past it now.

#

Btw, stuck at 922 is optional mods not installing I think.

#

So now I'm not sure if it was broken or not...

#

Everyone sharing issues means there is for sure some issues still lingering though.

quaint minnow
#

Removed the collection leaving mods, deleted CBBE entirely, reinstalled

velvet relic
#

Still doing a 2nd reinstall on 16.1 btw :p

quaint minnow
#

Does the collection delete these?

#

Poor Nagev is gonna have a fun morning Nox_Sad

velvet relic
#

Nope. We do modify some files though.
Ah this is a lovely mess.

#

And my test rig in everything now ran out of storage and Vortex refuse to start up so I can actually move downloads to a different folder so now I have to force delete stuff and start over :p

velvet relic
#

Will call it a night on this one. Sadly didn't work out as well as I hoped.

#

For context. I was able to finish on 15.2 once before retrying to check... running into this.

quaint minnow
#

Would be really handy to be able to filter and sort based on all the collection columns

#

I want to uninstall all mods using binary patching and replicate, then manually install them one by one from the collection to see if i hit any issues

#

i have to scroll through and hunt for them in the workshop, note the name, go to mods, search for it, then uninstall CatOhNo

velvet relic
#

Sadly Vortex doesn't really let me filter stuff in a way that lets me show what's been "modified".
Otherwise I'd share some screenshots. But atm since I can't filter really it'd just be showing a list of stuff that isn't what you're looking for.

quaint minnow
#

Doing another install with all Automation settings enabled

quaint minnow
#

seems like maybe a race condition

velvet relic
#

Retrying today I essentially got the same failures, but after restarting Vortex and doing the "Repair" option it was able to finaly finish for me.

#

The targeted plugin there is one that's being binary patched though. Totally forgot what I did there xD

quaint minnow
#

Should keep a patch separate with your changes so they can be easily reviewed, then merge into the master before publishing :P

#

Updating to 271, Got a failed to parse error on CBBE.esp. Assuming that can be ignored

#

Same issue as earlier, collection UI doesnt seem to reflect that its completed until I back out, and no completion prompt

#

also had to do the final deployment manually

velvet relic
#

Hmm. Seems like the same one that Mike also got. Might just reupload unflagging that.

quaint minnow
#

I suspect it'll happen randomly with anything you patch

#

they probably just need to account for the patching step somewhere

vale jungle
#

Given the amount of BE problems we're having today, I'm going to postpone further tests for StoryWealth for tomorrow (Sorry guys 😬) I've been trying to download rev 271 for the past hour with multiple 50x errors :/

#

We do have a 1.16.2 release built up, but going to release it tomorrow morning (in case we need to change additional items on our end to support the BE)

#

Not a great day

velvet relic
#

Yeah. Getting the same stuff atm.

edgy verge
#

Yay, happens to the best of us!

quaint minnow
#

actually even if it's not I'll play with it. I live life on the edge CoolDoge

quaint minnow
#

well, maybe I wont get to test it yet 😅

#

is graphql just too heavy to be used at this scale? or just needs optimizing

#

There doesn't seem to be much different with 1.16.2

#

CC @vale jungle @edgy verge @oak sparrow

#

This was using the build artifact from Package #358

edgy verge
#

We've had a day of backend issues, and the QUERY_TOO_COMPLEX is happening to protect the site until we can get 1.16.2 (a repackage) out in the morning.

quaint minnow
#

I assume there will be another 1.16.2 build with some tweaks tomorrow?

edgy verge
#

1.16.2 that you sneakily have got will have everything apart from the query_too_complex fix., which the backend have added this evening

quaint minnow
#

:P

edgy verge
#

We were basically DDOSing our own site, with some big old gql queries to do with the Collection Workshop

quaint minnow
#

The collection install issue will likely still be a thing if its just the query fix

edgy verge
#

We've a few fixes in the mix

quaint minnow
#

Don't mean to rush, just wanted to get a test run done asap

edgy verge
#

[1.16.2] - 2026-02-xx

  • Fixed race condition when attempting to generate file UIDs (#19602 and several others)
  • Added handling for transient EBUSY errors when starting loot (#19609)
  • User cancelled error suppression (#19619) (fixes #19619)
  • Fixed linking issues on mod extraction/install (#196101, #19626, #19700 and several others)
  • Suppress error report for user derived FOMOD-IPC timeout errors (#19641)
  • Fixed FOMOD native errors when installing XML FOMODs with BOM characters (#19718)
  • Fixed attempts to install corrupted/failed downloads (#19627)
  • Fixed broken icons on Browse Collections page
edgy verge
quaint minnow
#

Exciting times

vale jungle
#

Right, I'm back on StoryWealth now

velvet relic
#

I was able to finish it today on latest test without any hiccups. So that's good 😄

oak sparrow
#

Maybe the API restrictions added last night stopped it stalling out

quaint minnow
#

Deleted a few mods and then resumed, looks like it still stalls

quaint minnow
#

Removed and readded the collection
Behavior is the same as previous versions

#

Also worth noting that for around half the video the UI is frozen. Given my PC specs, I suspect the average user will have a much longer hang with the app completely unresponsive

velvet relic
#

Looks a lot like this issue I just had a user report.

#

He did click the "Play Button", just not in the screenshot here.

oak sparrow
# velvet relic

Have they actually checked the "Mods" tab? I did see it once where the collection tab was out of date but the mods were actually installed

velvet relic
#

They did say the mods seems to show up in Mods Tab. But either way, suggests that there is something that needs to be fixed as it's confusing at best, especially since it shows "pending".

oak sparrow
#

Have they tried uninstalling (but not deleting archive) the one in the mods tab?

#

I'm just wondering if a "fresh" install re-connects the missing metadata

velvet relic
#

Don't think they did, but asked them to try that to get rid of it.

oak sparrow
#

Remove the mod (and the archive?) then redownloading may fix it. I'm not entirely sure what's gone wrong, we could have them dump their Vortex state but that might not have the answer

#

Actually, I think I've replicated the issue

#

I keep getting the toast "mods removed"

velvet relic
#

Was going for not deleting archives. Mostly because our guide suggests that.

oak sparrow
#

Ok, so after a few more seconds, the collection finished properly

velvet relic
#

This feels like it's linked to the missing dependencies issues, where as for some users it doesn't finish up?
I think I had similar stuff where it did finish up on my testing.

oak sparrow
#

I did see in the mods table Vortex enable and disabled one of the "Missing" mods a few times

#

Hmm CBBE is still saying it's not installed

velvet relic
#

Yeah, binary patched mods seems to be more common to get hit. THe screenshot I shared, all the non-asw mods in the list there was binary patched mods.

#

Okay, the bridges wasn't. But the other was, which still makes it a very high ratio.

oak sparrow
#

I'm poking around in my Vortex state file to see if I can figure out what's going on with CBBE

#

CBBE is mentioned 72 times though 😅

velvet relic
#

Damn. My latest test on 272 with 16.2 though it didn't complain about CBBE for what it's worth, but for sure seems to be something going still.

oak sparrow
#

Ok, Nagev just confirmed it's a display bug with the collection mods table that's going to be fixed in 1.16.3

velvet relic
#

Okay, good to hear.

vale jungle
#

I'm 99% sure that the issues that affected StoryWealth were the same ones affecting @sharp rampart's SSE collection - I've installed/reinstalled both of your collections x amounts of times in 1.16.5 and have yet to run into any issues (important mention is that I never ran into any issues for ASW, which is the reason I'm saying 99% instead of 100%)

#

@velvet relic - please do let me know if you spot any issues in the latest Vortex release

velvet relic
#

That's nice to hear. Hopefully that does it.
Will let you know if I confirm further issues with that one on 16.5.

quaint minnow
#

Yall need to start having issues with smaller collections so I can test more easily 😅

#

Installing aSW now

#

Got a HTTP 500 error on a download, and now it seems to have stalled

#

Since the download controls are disabled during collection install I don't see a way to tell it to try again

vale jungle
#

Let it run - a 50x error just suggests there was a network/server hiccup - can resume later when asked

#

If you're positive it's not progressing - pause and resume

#

The correct way of dealing with this is through the collections screen. Downloads page will just confuse it.

#

So pause the collection download and resume it.

quaint minnow
#

I tried pausing and resuming, no change

vale jungle
#

What CDN are you connected to? do you have a default set?

quaint minnow
#

It's set to the default. "CDN"

#

I just removed the collection and am re-adding it

#

There wasn't any activity at all on downloads or the collection screen

vale jungle
#

Can you give me the exact error that the collection download failed error is specifying?

#

At this point I'm 100% sure it's not Vortex - it's the BE and I need to gather proof.

quaint minnow
#
2026-02-25T16:00:45.411Z [DEBG] stopping chunk worker {"paused":false,"id":6442,"offset":0,"size":20971520,"confirmedSize":20971520,"confirmedReceived":0}
2026-02-25T16:00:45.411Z [WARN] chunk exceeded max requeues, marking download as errored {"id":"KMUSNL7l2N","workerId":6442,"remaining":20971520,"requeues":6013}
2026-02-25T16:00:45.611Z [ERRO] DownloadWorker URL resolution failed {"workerId":6443,"chunkOffset":0,"chunkSize":20971520,"error":"HTTP (500) - Request Failed"}
2026-02-25T16:00:45.612Z [WARN] chunk error {"id":6443,"err":"HTTP (500) - Request Failed","ended":false,"networkRetries":0,"dataReceived":false}
2026-02-25T16:00:45.612Z [DEBG] not retrying chunk error {"id":6443,"errorMessage":"HTTP (500) - Request Failed","isNetworkError":false,"isTimeoutError":false,"shouldRetry":false,"ended":false,"dataHistory":0,"networkRetries":0,"maxRetries":3}
2026-02-25T16:00:45.612Z [DEBG] stopping chunk worker {"paused":false,"id":6443,"offset":0,"size":20971520,"confirmedSize":20971520,"confirmedReceived":0}
2026-02-25T16:00:45.612Z [WARN] chunk exceeded max requeues, marking download as errored {"id":"KMUSNL7l2N","workerId":6443,"remaining":20971520,"requeues":6014}
2026-02-25T16:00:45.812Z [ERRO] DownloadWorker URL resolution failed {"workerId":6444,"chunkOffset":0,"chunkSize":20971520,"error":"HTTP (500) - Request Failed"}
2026-02-25T16:00:45.812Z [WARN] chunk error {"id":6444,"err":"HTTP (500) - Request Failed","ended":false,"networkRetries":0,"dataReceived":false}
2026-02-25T16:00:45.812Z [DEBG] not retrying chunk error {"id":6444,"errorMessage":"HTTP (500) - Request Failed","isNetworkError":false,"isTimeoutError":false,"shouldRetry":false,"ended":false,"dataHistory":0,"networkRetries":0,"maxRetries":3}
2026-02-25T16:00:45.812Z [DEBG] stopping chunk worker {"paused":false,"id":6444,"offset":0,"size":20971520,"confirmedSize":20971520,"confirmedReceived":0}
2026-02-25T16:00:45.812Z [WARN] chunk exceeded max requeues, marking download as errored {"id":"KMUSNL7l2N","workerId":6444,"remaining":20971520,"requeues":6015}
#

it looks like it retried a lot

#

I need to tweak the max log size for testing so I just get one massive log.
the rotation confuses me

vale jungle
#

I've been meaning to change the size for a while too

#

Remove that download and try to resume again?

quaint minnow
#

When I cancelled the collection install it removed it, then I restarted vortex and added the collection again

#

it's downloaded that one successfully now

#

Next time I'll leave it up to play around to try getting it to resume

#

Is it possible the server just gave a bad link?

#

so retrying would never work without a new download request?

vale jungle
#

I'm not sure, but I'm probably going to switch CDNs upon 50x errors automatically in the future

#

@cosmic totem already suggested that and I should've listened.

quaint minnow
#

Maybe a couple retries, then jump ship

quaint minnow
#

Aside from that server error, no issues with StoryWealth so far, and it's into the optional mods

#

Time to get crackin on my Collectionathon stuff kittyexcite

#

Not sure when the checking dependencies notification appeared, but feels out of place

#

the missing masters is from the cancelled install earlier, so can ignore that

#

hmm, this is after the popup that it completed

#

after the finalizing - deploying and applying rules step

#

Probably unrelated, but spotted this ```js
2026-02-25T17:46:37.798Z [ERRO] [gamebryo-plugin-management] Unexpected non-whitespace character after JSON at position 238 (line 1 column 239)

#

UFO4P is the missing master, but it's present in staging and Data/
Clicked on the Vortex plugins tab and its been at the loading spinner for quite a while

#

Restarted Vortex then applied collection rules. For some reason the unofficial patch plugin is still disabled

#

I assume that's not just an accident in the collection? @velvet relic

#

Nope

#

Those are part of my own collection that's installed in another profile.

#

Maybe that's why they're disabled?

#

Resumed the collection and it completed and refinalized.
UFO4P's esp and those two mods are still disabled Thonk

#

I see nothing of note in the log

#

Were it not for the server error and my own collection being installed, aSW probably would have had no hitches

#

thats not right lol

#

Ahhhh I have different versions of these mods installed

#

That is not UFO4P v2.1.5

#

It's like it overwrote the metadata but kept the 2.2.0a install

#

My collection I had installed before this has 2.2.0a

#

I'll see if I can make a small repro for this

quaint minnow
quaint minnow
#

Updated that to tack some additional steps onto variant 2

edgy verge
#

Will investigate in the morning, thank you for your efforts!

velvet relic
velvet relic
#

Interesting. Somehow it wants to grab the latest version of UFO4P that we doesn't use.

quaint minnow
velvet relic
#

Which is the exact issue you were having it seems.

#

And quite sure I had it set to Exact Only. Lemme double-check.

quaint minnow
#

Mine was a result of a collection overwriting the metadata of an existing mod, but if theyre installing aSW thatd be overwriting with 2.1.5

#

Did they have UFO4P 2.2.0 downloaded before the collection install?

velvet relic
#

I dunno, most likely not, but could check.
But as you can see it shows up in the Mods Tab for the collection itself.

quaint minnow
#

I'll play around and see if I can recreate that

#

well shit lol

#
  1. installed/enabled/deployed UFO4P 2.2.0a
  2. Installed a collection with just UFO4P 2.1.5
  3. Chose replace existing mod
#

I'll probably add this to my other github issue. It feels like a result of the same bug

#

I'd have them pause the collection, remove all traces of UFO4P, then resume

#

On the main mods list it shows the intended version, but that file is actually 2.2.0a

#

Weird, I cancelled the collection install and it swapped from 2.2.0a back to 2.1.5 on the collection mods tab as it was uninstalling

velvet relic
#

Yeah, they also got it to swap after somehow. Not 100% sure what they did there. Possibly they removed the wrong file or something.

quaint minnow
#

I will isolate and create repro steps for every collection bug or die trying lasertodd

velvet relic
#

I feel it's somehow trying to go with the wrong file, which is causing issues here somehow. Like as if "got the mod!" but when it tries to install it's not the right "stuff" and stalls?
But yeah, clearing this hopefully will help clear out the whole 99% issue.

Key thing to figure out is if Vortex sometimes actually downloads the wrong file (I've had it happen in the past for some mods actually, but that was over a year ago now)

#

So sounds they had the 2.2.0a archive downloaded.

#

They confirmed they had downloaded latest on another profile.
So that means it's the exact thing as what you just tested.

velvet relic
#

In short. I just updated said mod. Collection should be downloading the older version though.

#

Yet now somehow they are getting the 99% error here?

#

So what this says is that it's happening on stuff that have been updated.

quaint minnow
#

I think that's this issue

#

This one seems kinda critical

#

Because it overwrites the metadata from the existing mod it's probably going to leave a ton of users with the wrong file installed

#

Vortex could maybe compare file version to the staging folder name to retroactively fix this

#

copy/pasting this in the author server since its being talked about in multiple places 😅

velvet relic
#

The thing is, there is no way they would have the wrong version as it was just released. Which suggests that there's more to it.

#

I'm quite confident it's related though.

quaint minnow
#

The test I made didnt hang though :/

#

1.16 Collection Issues (FO4; StoryWealth)

quaint minnow
#

Once you get a notification for incompatible mods in a collection, there doesnt seem to be a way to get it to dismiss itself

#

this also doesnt dismiss itself once corrected

#

far more minor than previous issues though

quaint minnow
#

Installed aSW

  • Download speeds seemed extremely bottlenecked, maybe the same issue users encounter with Domain to a lesser extent
  • I still dont understand why at 10:27 it does a deployment while still installing
#

Other than that, it appears to be successful

#

I still need to run through the repro steps for my recent GitHub issues

quaint minnow
# quaint minnow

In this video I never received the final collection install complete popup after installing optional mods

#

I assume its related to skipping one

#

In one of the runs I did, it seemed like the instructions popups for optional mods were fighting to be on top

#

I clicked install but installed the wrong one because it was switching between the two mods as I was clicking

#

(not in that video)

quaint minnow
#

Installed Immersive & Adult

  • Download speeds felt slow
  • A mod was hung at the end (~17:13)
#

Just the part with the issue

#

Also note the mod version. It shows 0.0.0, but it's actually "IA"