264 posts in this topic

For me, all of the supposedly mismatched files are ESPs. Nothing else shows up as out of sync.

A normal refresh on the package does nothing. It remains with an orange square. Only a full refresh corrects it, but it only stays corrected for as long as Bash is up for that session.

Share this post


Link to post
Share on other sites
24 minutes ago, Utumno said:

Edge case in the code - since the plugin has not changed size or mod date we don't rescan for mergeability - Run Scan Mergeable on it

Yep that works 

Mark Mergeable with the BSA still installed says "Not Mergeable" Has BSA installed

Mark Mergeable with the BSA manually deleted, and it is recognised as mergeable and turn green

Share this post


Link to post
Share on other sites

Thanks @alt3rn1ty - yes I haven't disabled but the pop up - you mean I should disable the ghosting menu altogether ?

@Arthmoor please run the latest utumno-wip : https://github.com/wrye-bash/wrye-bash/archive/utumno-wip.zip

 

I added some debug prints - do produce the bugdump (just run your Wrye Bash Debug.bat). I believe there's a mismatched cached crc in there.

Beermotor and alt3rn1ty like this

Share this post


Link to post
Share on other sites
13 minutes ago, Utumno said:

Thanks @alt3rn1ty - yes I haven't disabled but the pop up - you mean I should disable the ghosting menu altogether ?

Yeah if its easily done for individual games (leaving it enabled for Oblivion), its no use to Skyrim LE / SE or FO4, having it still in the context menu for those games is just going to be a stream of questions from confused users.

Share this post


Link to post
Share on other sites
1 hour ago, Utumno said:

Thanks @alt3rn1ty - yes I haven't disabled but the pop up - you mean I should disable the ghosting menu altogether ?

@Arthmoor please run the latest utumno-wip : https://github.com/wrye-bash/wrye-bash/archive/utumno-wip.zip

 

I added some debug prints - do produce the bugdump (just run your Wrye Bash Debug.bat). I believe there's a mismatched cached crc in there.

I'm home for the weekend now (I'm on-call so I'm rooted to my office chair) , so I'll snag that version and test as well. 

Share this post


Link to post
Share on other sites
21 hours ago, Utumno said:

Thanks @alt3rn1ty - yes I haven't disabled but the pop up - you mean I should disable the ghosting menu altogether ?

@Arthmoor please run the latest utumno-wip : https://github.com/wrye-bash/wrye-bash/archive/utumno-wip.zip

 

I added some debug prints - do produce the bugdump (just run your Wrye Bash Debug.bat). I believe there's a mismatched cached crc in there.

So the bleeding edge code isn't considered the latest anymore? Either way I'll grab that one and give it a shot.

Share this post


Link to post
Share on other sites

Update on my last post:

I'm either going nuts or I'm not able to reproduce the problem since installing the latest python build.

I have however run into a problem with the Bodyslide paths thing, but I'll update the issue on GitHub to keep the focus here on the refresh issue.

 

alt3rn1ty likes this

Share this post


Link to post
Share on other sites

This is all the bug dump gave me and it doesn't look very helpful to me:

	Wrye Bash starting
Using Wrye Bash Version 307
OS info: Windows-7-6.1.7601-SP1
Python version: 2.7.12
wxPython version: 2.8.12.1 (msw-unicode)
input encoding: UTF8; output encoding: None; locale: ('en_US', 'cp1252')
filesystem encoding: mbcs
bash.py  322 main: Searching for game to manage:
bush.py   89 __supportedGames: Detected the following supported games via Windows Registry:
bush.py   91 __supportedGames:  Oblivion: c:\games\bethesda softworks\oblivion
bush.py   91 __supportedGames:  Skyrim: C:\Steam\steamapps\common\Skyrim
bush.py   91 __supportedGames:  Skyrim Special Edition: C:\Steam\steamapps\common\Skyrim Special Edition
bush.py   91 __supportedGames:  Fallout4: C:\Steam\steamapps\common\Fallout 4
bush.py  149 _detectGames: Detecting games via the -o argument, bash.ini and relative path:
bush.py  159 _detectGames: No known game in parent directory of Mopy: C:\Wrye Bash 308
bush.py  170 __setGame:  Using Skyrim Special Edition game: C:\Steam\steamapps\common\Skyrim Special Edition
balt.py  818 <module>: Comtypes is missing, features utilizing HTML will be disabled
mods_metadata.py   39 <module>: Failed to import the loot_api module: (No module named loot_api)
testing UAC
MISMATCH: Whistling Mine.esp cached DEDF2F22 real 4FC632B2
MISMATCH: Unofficial Skyrim Special Edition Patch.esp cached 8D5B65D3 real 8D0F9513
MISMATCH: Helarchen Creek.esp cached A21F4897 real C159039E
MISMATCH: Castle Volkihar Rebuilt.esp cached 0530289A real 89CB6A13

alt3rn1ty and Beermotor like this

Share this post


Link to post
Share on other sites

It looks exactly as expected to me - note the "Castle Volkihar Rebuilt.esp cached 0530289A real 89CB6A13" - that's the esp that showed as mismatched right ?

The bleeding edge is always the tip of the utumno-wip branch, sometimes I pack a standalone from it and post it here as "bleeding edge".

I monkey patched full refresh to correct this - so have a go at https://github.com/wrye-bash/wrye-bash/archive/utumno-wip.zip (same zip but different content, that's always the contents of utumno-wip branch on github)

Full refresh should correct this (and take slightly longer)

alt3rn1ty and Beermotor like this

Share this post


Link to post
Share on other sites

Yep, the 4 files it listed as mismatched were all the ones that were doing so falsely.

The update fixed it though, so thanks :)

alt3rn1ty likes this

Share this post


Link to post
Share on other sites

Utumno, the latest WIP gives me the following traceback when launching WB for Fallout 4:

MISMATCH: Bashed Patch, 0.esp cached AB97BD63 real BACA7C64

Rebuilding the bashed patch doesn't help - I get the same error on the next WB launch.

Let me know what you need. :)

EDIT: Deleting the old bashed patch and generating a new one works fine (as expected). For some reason, WB doesn't recognize that the old one has been updated.

Share this post


Link to post
Share on other sites

@Utumno  Success, but the problem is my fault.

While enjoying a St. Bernardus Abt 12, perhaps the finest example of a Belgian abbey ale on Earth,  I finally figured out the BodySlide path issue.

In the Skyrim distribution of BodySlide there is no space between the words "CalienteTools". :/

I've updated issue #379 with what I found.

 

Share this post


Link to post
Share on other sites

Good catch @Supierce- monkey patched in latest utumno-wip ( added a crc scan on patch completion ). The whole crc business will be smoothed out in 308. Those python versions are slow to start due to scanning crcs for debugging - will maybe add a menu item

Changed to calientetools for both skyrims @Beermotor

With those fixed (especially the one by @Arthmoor) I think my bleeding edge is ready for stable

Beermotor likes this

Share this post


Link to post
Share on other sites
22 hours ago, Utumno said:

With those fixed (especially the one by @Arthmoor) I think my bleeding edge is ready for stable

Outstanding! Thank you @Utumno

Edit: First impressions: this is a dream come true. The BodySlide management is working perfectly in both Skyrims as well as Fallout. I'm going to work on a how-to for explaining how to install BodySlide to get the executables over to help folks get it up and running.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now