BAIN: Installer tab reports missing package assets after install

[BeermotorWB]

I've been experiencing an issue with BAIN in the recent nightlies, I'm guessing at least since a mid-April 21 build. I haven't reported it before now because I was trying unsuccessfully to build up some reliable reproduction steps, but in light of other reports this information might be useful.

The expected behavior is: BAIN remembers the state of assets after a package is installed.
Observed behavior: After a new package is installed, BAIN will sometimes report that assets of a package are not installed (red box with plus). This normally happens after another application reads or adds assets to the data folder, even if they're intentionally not tracked by BAIN.

Repro steps I have so far:

1. Install a package. In all of my cases it is a package with a BSA because I pack just about everything into a BSA.
2. Switch to the mods tab, tick the box.
3. Leave Bash open and open xEdit without bypassing reference building.
4. Review the file in xEdit. Check for errors or whatever but do not save changes.
5. Note this makes a .REFCACHE file in the Data folder under "SSEEdit Cache"
6. Close xEdit and return to Bash.
7. Switch to installers tab.
8. Note status of installed package.
9. If package is red, reinstall or anneal to correct.
10. Package will stay installed after the reinstall/anneal.

Other information:
Directories in Data not tracked by Bash/BAIN:
./Tools/FNIS/* (Running FNIS is expected to affect installed state of the FNIS parent package as it replaces assets)
./SSEEdit Cache from xEdit
./NetScriptFramework from the .NETscript debugging tool.

No bugcheck experienced yet but I'll keep running debugmode to try to get something.

[Infernio]

I've noticed this too, but I'm sure it's been around for much longer than recent nightlies. I could swear I hit this even back in the 307 betas era. In any case, it's not critical for now - Quick Refresh on the package has always fixed it for me (plus we're in the middle of 309/py3).

…

On 27. May 2021, at 01:17, BeermotorWB ***@***.***> wrote:  I've been experiencing an issue with BAIN in the recent nightlies, I'm guessing at least since a mid-April 21 build. I haven't reported it before now because I was trying unsuccessfully to build up some reliable reproduction steps, but in light of other reports this information might be useful. The expected behavior is: BAIN remembers the state of assets after a package is installed. Observed behavior: After a new package is installed, BAIN will sometimes report that assets of a package are not installed (red box with plus). This normally happens after another application reads or adds assets to the data folder, even if they're intentionally not tracked by BAIN. Repro steps I have so far: Install a package. In all of my cases it is a package with a BSA because I pack just about everything into a BSA. Switch to the mods tab, tick the box. Leave Bash open and open xEdit without bypassing reference building. Review the file in xEdit. Check for errors or whatever but do not save changes. Note this makes a .REFCACHE file in the Data folder under "SSEEdit Cache" Close xEdit and return to Bash. Switch to installers tab. Note status of installed package. If package is red, reinstall or anneal to correct. Package will stay installed after the reinstall/anneal. Other information: Directories in Data not tracked by Bash/BAIN: ./Tools/FNIS/* (Running FNIS is expected to affect installed state of the FNIS parent package as it replaces assets) ./SSEEdit Cache from xEdit ./NetScriptFramework from the .NETscript debugging tool. No bugcheck experienced yet but I'll keep running debugmode to try to get something. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe.