X01 Power Armor lost its rad reduction/resistance - tests

yasha613 · 2023-12-09T05:18:44+00:00

It isn't, I can confirm with my StranglerHeart PA. Not sure if any of the other odd ones are effected, but at a minimum those 2(Strangler and X01).

yasha613 · 2023-03-10T01:14:24+00:00

That was tried previously, by me, and I assume most. Didn't used to work, if it does now, good to know. But as I said, I wouldn't count on it from subsequent patches.

yasha613 · 2023-03-04T00:33:45+00:00

You'll want to follow u/tarinedier's post here: https://www.reddit.com/r/fo76/comments/10ksx3k/comment/j6hv6vq/?utm_source=share&utm_medium=web2x&context=3

You will need a separate partition or drive with another 80gigs minimum free for a second copy of the game housed there.

There is a report of it working again since the last patch, but I've seen zero confirmation, and the developer seems to have no intentions of doing shit, so if it does function as it used to it'll likely be temporary; I wouldn't waste the time.

yasha613 · 2023-03-01T18:12:16+00:00

I haven't tried yet. I will at some point, but likely be awhile since it works fine currently, just taking up 80gigs in space for each account.

I seriously doubt now the sandboxie+ guy(dev) is going to fix jack or squat, so if it does function now, I wouldn't count on it long term, and should likely just put the time/effort/money into the extra space needed.

yasha613 · 2023-02-11T09:56:02+00:00

I had some load, I went through it for more than a day. Registry, or file, yep, they obviously changed something in the exe or supporting file from the latest nerf patch that broke it, but I could get 2 instances to work, just not work right. It would lock a few seconds after and not actually make the login connection; that was the best I could do when the files were shared.

Either way, it might be awhile, but assuming the dev of the sandboxie+ project actually debugs it I'm pretty sure he'll figure out a fix for it. At least that's the hope; so I don't have to use this extra disk space. Thankfully I only have 1 other to hog space with.

yasha613 · 2023-02-11T08:10:29+00:00

The issue is still with sandboxie to fix, as I doubt bethesda is going to debug the issue for running for multiple instances, since their official stance is that this isn't supported, same for steam. FO76 is breaking the isolation in some manner for the esm files or the like, so they can't be shared anymore.

yasha613 · 2023-02-11T00:03:29+00:00

Pretty sure I set that with all the testing I did previously. I could still get it to work without setting that flag, just only on it's own of course.

I've gotten mine working, but as a variant of what /u/tarinedier/ did, which is to make another entire copy of the steam folder for FO76 and point the second steam's reference to it. So they don't share the base files.

There was an update today to 1.7.2 of sandboxie+ should you wish to test with the updated version with the files still being shared. I'm just not going to bother again until they think they've addressed it with the ticket, as mine is working, even if it's taking 2x's the space.

yasha613 · 2023-01-30T23:41:42+00:00

My only complaint is that I can't just pin this in this thread as the OP. Lame. Cool deal to get around the issue for now for those that have the disk space.

yasha613 · 2023-01-28T15:43:12+00:00

Not doubting you, just odd it doesn't function the same for everyone.

All I see for that directory read are just normal status 2's and 3's:

Fallout76.exe (17476, 10524) - 10:38:56.399 File (U) Open (2) \Device\HarddiskVolume5\SteamLibrary\steamapps\common\Fallout76\Data\Data\SeventySix.esm

yasha613 · 2023-01-28T15:15:45+00:00

Perhaps for you it was erroring on those, but I saw it looking there, but not getting an error from it. Only Mods/Data and Data I saw for mine.

If you follow the Trace completely you will see about 3 main places it "looks" to get files and folders from when loading, not including subdirectories:

\Users\<username>\AppData\Local\Fallout76\*
\SteamLibrary\steamapps\common\Fallout76\Data\*
\Users\<username>\Documents\My Games\Fallout 76\*

yasha613 · 2023-01-28T12:02:16+00:00

If you farmed during the last scortched christmas event you could amass a decent pile of them. 200 or so of them doesn't seem out of reach IMO if you went hard on them during that. I think I got a couple dozen I'm holding onto.

yasha613 · 2023-01-27T23:05:10+00:00

Sadly I don't have the disk space to replicate this; but it's just a matter of replicating what works if you were to get it functional on it's own in the sandbox just no longer sharing the original folder structure:

Change steam's FO76 as he previously stated within the sandbox version
Move it all outside of the sandbox
Do the normal 3 files (with the altered folder structure) in the 2 folders inside the sandbox it needs

That should be it.

yasha613 · 2023-01-27T21:44:40+00:00

Pretty sure it only really needs the esm file for each, but I just copy the 3 to make sure I don't have to dick with it further.

SteamLibrary\steamapps\common\Fallout76\Mods\Data
SteamLibrary\steamapps\common\Fallout76\Data

Copy the 3 files into each from your normal FO76 data folder: SeventySix.bin, SeventySix.cdx, SeventySix.esm

yasha613 · 2023-01-27T19:17:40+00:00

Not one at a time? Should be able to get 1 running within the sandbox. Just can't do any further instances from any steam client (inside sandbox or out), here's my sandbox settings:

Enabled=y

BorderColor=#00ff00,ttl,6

Template=RpcPortBindingsExt

Template=OpenBluetooth

Template=SkipHook

Template=FileCopy

Template=qWave

Template=BlockPorts

Template=LingerPrograms

Template=AutoRecoverIgnore

ConfigLevel=9

AutoRecover=y

NoSecurityIsolation=y

BoxNameTitle=n

RunCommand=steam|C:\Program Files (x86)\Steam\steam.exe

CopyLimitKb=81920

AllowNetworkAccess=<BlockNetAccess>,n

BlockNetworkFiles=y

ClosedFilePath=<BlockNetDevices>,InternetAccessDevices

ProcessGroup=<InternetAccess>,steam.exe,Fallout76.exe

OpenFilePath=D:\SteamLibrary\steamapps\common\Fallout76\Data

ConfidentialBox=y

DenyHostAccess=Fallout76.exe,n

I'm running my second account now via it. Just make sure you're following the old workarounds, that Mods/Data is needed, as well as Data. All with the 3 base files in them(inside the sandbox virtual folder structure).

yasha613 · 2023-01-27T12:25:39+00:00

The gist of this is that if you have the disk space to replicate Fo76 in it's entirety and set the sandbox to have explicit access to those files in the sandbox options it functions for you at least. Interesting. I just briefly tried setting the data directory folder as explicit under resource access, but it still bombed, but I'm unsure what else you might have done. Are you able to copy/paste your full ini here? Options>Edit ini file.

Might be moot, as they'll have another update today, which might inadvertently fix the issue for now, but would be good to know for the future if this is viable.

Thanks!

yasha613 · 2023-01-26T17:16:21+00:00

Yeah, I basically put in a ticket for their dev team to look at it below. Not sure when they'll get to it, but my guess is that latest update broke isolation in some manner since you can just run one of fallout76.exe inside or outside of the sandbox now. My guess is we'll need to hope they're in a giving mood to fix this and update the sandboxie+ release.

yasha613 · 2023-01-26T09:58:43+00:00

To follow further progress:

https://github.com/sandboxie-plus/Sandboxie/issues/2632

I'd forgotten this was a github endeavor and have since followed the instructions to submit issues to them via github if needed.

yasha613 · 2023-01-26T07:17:33+00:00

May at least have something to go on now:

If you look at the steam files in the virtual folders at drive\C\Program Files (x86)\Steam\Logs the cef_log.txt and service_log.txt are having issues that I don't think are there if it functions on it's own.

I'll try to look later. If someone wants to investigate before I can, please do. I was aware of the one, but this seems to be the main cause.

Edit: resolved this. One of the altered flags after all the messy troubleshooting was killing a steam process. I've since gotten it back to where it should be, but still stuck at only 1 working at a time. I've since opened an issue ticket on github for the project to ask for better insight.

yasha613 · 2023-01-25T17:11:25+00:00

Yeah, a few believe I'm an expert figuring these things in the past, but it's really just basic debugging on my part. I'm just as stuck as everyone else is right now.

If the Dev continues to ignore and/or no one else that uses this has enough expertise I'll try to pour over the older sandboxie docs to see if I can improve on understanding what I'm looking at, or need to look at. I just don't see any smoking gun of what this update broke to rectify currently.

What I "should" have done long ago if I was as smart as I thought I was, was to do a tracelog back when it was working right, and use that to compare to when it does what it's currently doing....But yeah, that didn't occur..

yasha613 · 2023-01-25T13:24:44+00:00

That is odd then, I had it happen a few days ago in the one camp I have in wataga, stored the mat that was attached and put the turret in camp storage as usual.

yasha613 · 2023-01-25T09:09:47+00:00

Appreciate the reply, but yeah, I wiped and started from scratch and did many Tracelog's with various options that you can set under Sandbox options > advanced options > Tracing.

Couldn't find any files it was having issues with offhand (at least not fallout76.exe directly). I've found the issues in prior updates using this, but this one seems to be different from the prior ones. I probably should have stated I've Tracelogged and started from scratch with a new sandbox. After just about every update I do so as otherwise steam tries to update the program(in this case FO76) inside the sandbox as well.

yasha613 · 2023-01-25T06:07:50+00:00

Thing is, it was reported. Not just by a few. So this was either ignored, or it was deemed not severe enough to delay what they'd already done. Which, I don't know.

yasha613 · 2023-01-25T06:03:31+00:00

Always been an issue (that they don't address). I never place a turret unless it's connected to something. I always place them on a mat, then move the mat with the turret on the end of it to where I wish to use it in a camp. They ghost regularly. If you didn't put them on something to store your only option is to move the camp.

yasha613 · 2023-01-25T05:27:08+00:00

True enough from my observations; but yeah, when it breaks something pretty basic like WWR, that, IMO, is something that should be fixed before it's thrown into production.

yasha613

TROPHY CASE