Jump to content

Wrye Bash - All Games


Utumno
 Share

Recommended Posts

4 hours ago, Utumno said:

307.201709152046

In a hurry - untested:

- Fixup for asking user confirmation on creating dirs

- Some changes in SSE saves - should be ok

 

The former is fixed.

Wrye Bash (Special Edition) now doesn't want to recognize save headers. It was working perfectly fine in the previous build.

Time for the details:

jLqVH0y.png

Here's a line from the bug dump (I have almost 500 saves and all of them have the same error, so one would probably be enough):

__init__.pyo 1427 refresh: Failed to load Save157_B7063C41_1_4B616964656E_Tamriel_002030_20170801030653_17_1.ess: Save game masters size (-244384) not as expected (1478).

@Utumno This should probably be fixed ASAP, but I'll leave that up to you.

Link to comment
Share on other sites

Wrye Bash starting
Using Wrye Bash Version 307.201709152046 (Standalone)
OS info: Windows-10-10.0.15063
Python version: 2.7.12
wxPython version: 2.8.12.1 (msw-unicode)
Using scandir 1.5
input encoding: None; output encoding: None; locale: ('en_GB', 'cp1252')
filesystem encoding: mbcs 
bash.pyo  324 main: Searching for game to manage:
bush.pyo   76 _supportedGames: Detected the following supported games via Windows Registry:
bush.pyo   78 _supportedGames:  Oblivion: e:\oblivion
bush.pyo   78 _supportedGames:  Skyrim Special Edition: D:\Steam\steamapps\common\Skyrim Special Edition
bush.pyo   78 _supportedGames:  Fallout4: D:\Steam\steamapps\common\Fallout 4
bush.pyo  136 _detectGames: Detecting games via the -o argument, bash.ini and relative path:
bush.pyo  142 _detectGames: Set game mode to Skyrim Special Edition found in parent directory of Mopy:  D:\Steam\steamapps\Common\Skyrim Special Edition
bush.pyo  156 __setGame:  Using Skyrim Special Edition game: D:\Steam\steamapps\Common\Skyrim Special Edition
testing UAC
mods_metadata.pyo  228 __init__: Using LOOT API version: 0.10.2
__init__.pyo 1427 refresh: Failed to load Save1_DE475442_1_507269736F6E6572_Tamriel_000004_20170915104824_1_1.ess: Save game masters size (-245451) not as expected (413).
__init__.pyo 1427 refresh: Failed to load Save14_7D0163D7_1_5068616964_Tamriel_000250_20170909185210_4_1.ess: Save game masters size (-245452) not as expected (413).
__init__.pyo 1427 refresh: Failed to load Save12_7D0163D7_1_5068616964_Tamriel_000233_20170830022509_4_1.ess: Save game masters size (-245452) not as expected (413).
__init__.pyo 1427 refresh: Failed to load Save7_7D0163D7_1_5068616964_Tamriel_000059_20170828181458_1_1.ess: Save game masters size (-245491) not as expected (374).
__init__.pyo 1427 refresh: Failed to load Save10_7D0163D7_1_5068616964_BleakFallsBarrow02_000127_20170829173731_3_1.ess: Save game masters size (-245490) not as expected (388).
__init__.pyo 1427 refresh: Failed to load Save3_0D5D22FC_1_5068616964_Tamriel_000044_20170915112822_2_1.ess: Save game masters size (-245452) not as expected (413).
__init__.pyo 1427 refresh: Failed to load Save8_7D0163D7_1_5068616964_BleakFallsBarrow01_000121_20170828183654_2_1.ess: Save game masters size (-245503) not as expected (374).
__init__.pyo 1427 refresh: Failed to load Autosave3_0D5D22FC_1_5068616964_Tamriel_000025_20170915110900_1_1.ess: Save game masters size (-245452) not as expected (413).
__init__.pyo 1427 refresh: Failed to load Autosave1_0D5D22FC_1_5068616964_RiverwoodRiverwoodTrader_000034_20170915111752_1_1.ess: Save game masters size (-245462) not as expected (413).
__init__.pyo 1427 refresh: Failed to load Save5_7D0163D7_1_5068616964_Tamriel_000053_20170828180923_1_1.ess: Save game masters size (-245491) not as expected (374).
__init__.pyo 1427 refresh: Failed to load Autosave2_7D0163D7_1_5068616964_Tamriel_000240_20170909184237_4_1.ess: Save game masters size (-245452) not as expected (413).
__init__.pyo 1427 refresh: Failed to load Save6_7D0163D7_1_5068616964_Tamriel_000057_20170828181254_1_1.ess: Save game masters size (-245491) not as expected (374).
__init__.pyo 1427 refresh: Failed to load Save13_7D0163D7_1_5068616964_WhiterunDragonsreach_000235_20170830202327_4_1.ess: Save game masters size (-245458) not as expected (413).
__init__.pyo 1427 refresh: Failed to load Autosave3_7D0163D7_1_5068616964_Tamriel_000247_20170909184935_4_1.ess: Save game masters size (-245452) not as expected (413).
__init__.pyo 1427 refresh: Failed to load Save11_7D0163D7_1_5068616964_WhiterunWorld_000154_20170829180842_4_1.ess: Save game masters size (-245479) not as expected (388).
__init__.pyo 1427 refresh: Failed to load Save1_0D5D22FC_1_5068616964_HelgenKeep01_000014_20170915105828_1_1.ess: Save game masters size (-245457) not as expected (413).
__init__.pyo 1427 refresh: Failed to load Autosave1_7D0163D7_1_5068616964_WhiterunWorld_000239_20170909184141_4_1.ess: Save game masters size (-245454) not as expected (413).
__init__.pyo 1427 refresh: Failed to load Autosave2_0D5D22FC_1_5068616964_Tamriel_000034_20170915111810_1_1.ess: Save game masters size (-245452) not as expected (413).
__init__.pyo 1427 refresh: Failed to load Save9_7D0163D7_1_5068616964_BleakFallsBarrow02_000123_20170828183906_3_1.ess: Save game masters size (-245504) not as expected (374).
__init__.pyo 1427 refresh: Failed to load Save2_0D5D22FC_1_5068616964_HelgenKeep01_000020_20170915110359_1_1.ess: Save game masters size (-245457) not as expected (413).
Wrye Bash starting
Using Wrye Bash Version 307.201709152046 (Standalone)
OS info: Windows-10-10.0.15063
Python version: 2.7.12
wxPython version: 2.8.12.1 (msw-unicode)
Using scandir 1.5
input encoding: None; output encoding: None; locale: ('en_GB', 'cp1252')
filesystem encoding: mbcs 
bash.pyo  324 main: Searching for game to manage:
bush.pyo   76 _supportedGames: Detected the following supported games via Windows Registry:
bush.pyo   78 _supportedGames:  Oblivion: e:\oblivion
bush.pyo   78 _supportedGames:  Skyrim Special Edition: D:\Steam\steamapps\common\Skyrim Special Edition
bush.pyo   78 _supportedGames:  Fallout4: D:\Steam\steamapps\common\Fallout 4
bush.pyo  136 _detectGames: Detecting games via the -o argument, bash.ini and relative path:
bush.pyo  142 _detectGames: Set game mode to Oblivion found in parent directory of Mopy:  E:\Oblivion
bush.pyo  156 __setGame:  Using Oblivion game: E:\Oblivion
testing UAC
mods_metadata.pyo  228 __init__: Using LOOT API version: 0.10.2
Wrye Bash starting
Using Wrye Bash Version 307.201709152046 (Standalone)
OS info: Windows-10-10.0.15063
Python version: 2.7.12
wxPython version: 2.8.12.1 (msw-unicode)
Using scandir 1.5
input encoding: None; output encoding: None; locale: ('en_GB', 'cp1252')
filesystem encoding: mbcs 
bash.pyo  324 main: Searching for game to manage:
bush.pyo   76 _supportedGames: Detected the following supported games via Windows Registry:
bush.pyo   78 _supportedGames:  Oblivion: e:\oblivion
bush.pyo   78 _supportedGames:  Skyrim Special Edition: D:\Steam\steamapps\common\Skyrim Special Edition
bush.pyo   78 _supportedGames:  Fallout4: D:\Steam\steamapps\common\Fallout 4
bush.pyo  136 _detectGames: Detecting games via the -o argument, bash.ini and relative path:
bush.pyo  142 _detectGames: Set game mode to Fallout4 found in parent directory of Mopy:  D:\Steam\steamapps\Common\Fallout 4
bush.pyo  156 __setGame:  Using Fallout4 game: D:\Steam\steamapps\Common\Fallout 4
testing UAC
mods_metadata.pyo  228 __init__: Using LOOT API version: 0.10.2

 

Link to comment
Share on other sites

2 hours ago, Utumno said:

Thanks @Pabulum - fixed:


307.201709160706

Btw post me the whole bugdump (if there are 500 similar errors do edit those out but I need the first part with the info on your environment)

Utumno if you uploaded that around the same time as the post ( 2 hours ago ) I think the upload was not successful, I just tried dropbox moments before posting the bugdump above and got the previous version ( hence I thought I may aswell make myself useful and post the whole bugdump while I have the appropriate related version :)

Link to comment
Share on other sites

Well now I am confused .. @Sharlikran where did you get that version from ?

Usually when Utumno posts a new long version number like 307.201709160706 thats an indicator that the nightly build files are updated, but they aren't, which suggests this update is python source only ???

Link to comment
Share on other sites

1 hour ago, alt3rn1ty said:

Well now I am confused .. @Sharlikran where did you get that version from ?

Usually when Utumno posts a new long version number like 307.201709160706 thats an indicator that the nightly build files are updated, but they aren't, which suggests this update is python source only ???

I'm running the Python WIP (not from Dropbox) from 6:45ishPM on 16 Sept and it is showing the version as  307.201709160706.

I nuked all of my saves because I'd polluted them with foolishness, so I'm about to reroll a new character to test several things.

Link to comment
Share on other sites

3 hours ago, alt3rn1ty said:

Well now I am confused .. @Sharlikran where did you get that version from ?

Usually when Utumno posts a new long version number like 307.201709160706 thats an indicator that the nightly build files are updated, but they aren't, which suggests this update is python source only ???

Yep that's what I always do - I apparently shut down before upload completed (dropbox did have a green tick on the files but ...). They're up now.

Thanks everybody for testing.

Link to comment
Share on other sites

So I have an issue with WB and MO2 with the latest build 307.201709160706 , I know as a matter of course that this can gets kicked down the road as you don't support WB being use within MO/MO2. That being said with the up coming changes to Win 10 in the Fall release several changes have been made to Win 10's kernel to correct the 4GB dx9 bug along with a few other issues and OS build 16288 is currently being run on both the slow and fast ring concurrently. The stand alone version when run comes up with a pop up in MO2 as shown here it also appears when run just as a stand alone without MO2 involved. The difference is with MO2 the program fails to launch but as just a stand alone without MO2 once the screen is bypassed (answered) the program will launch. From what I have gathered this effects just the stand alone version the python version seems to work although I have yet to confirm this for myself (reported from other users). I've included my logs from WB and MO2  to assist.

Spoiler

Wrye Bash starting
Using Wrye Bash Version 307.201709160706 (Standalone)
OS info: Windows-10-10.0.16288
Python version: 2.7.12
wxPython version: 2.8.12.1 (msw-unicode)
Using scandir 1.5
input encoding: None; output encoding: None; locale: ('en_US', 'cp1252')
filesystem encoding: mbcs
bash.pyo  324 main: Searching for game to manage:
bush.pyo   76 _supportedGames: Detected the following supported games via Windows Registry:
bush.pyo   78 _supportedGames:  Skyrim Special Edition: D:\Steam\steamapps\common\Skyrim Special Edition
bush.pyo   78 _supportedGames:  Skyrim: D:\Steam\steamapps\common\Skyrim
bush.pyo  136 _detectGames: Detecting games via the -o argument, bash.ini and relative path:
bush.pyo  146 _detectGames: No known game in parent directory of Mopy: D:\Steam\steamapps\common\StepDumpSE
bush.pyo  156 __setGame:  Using Skyrim Special Edition game: D:\Steam\steamapps\common\Skyrim Special Edition
testing UAC
Traceback (most recent call last):
  File "Wrye Bash Launcher.pyw", line 89, in <module>
  File "bash\bash.pyo", line 360, in main
  File "bash\env.pyo", line 649, in testUAC
  File "bash\bolt.pyo", line 928, in rmtree
  File "shutil.pyo", line 256, in rmtree
  File "shutil.pyo", line 254, in rmtree
WindowsError: [Error 32] The process cannot access the file because it is being used by another process: u'c:\\users\\helidoc\\appdata\\local\\temp\\WryeBash_rd9oc3'
 

 

 usvfs-2017-09-16_18-26-32.log

Link to comment
Share on other sites

Ah understood about the upload, will grab tomorrow when back off shift in the morning

@Helidoc65 - I dont think anything can be done with that one on the Wrye Bash development side, process being blocked from accessing a file locked by another process causing a windows error doesn't seem to me like anything Wrye Bash could anticipate or prevent. If you are launching Wrye Bash via MO then MO should be handling all launched apps calls for files, so I reckon only MO developers would be able to address the issue. Wrye Bash knows nothing about the virtual environment it is being run in.

Link to comment
Share on other sites

@alt3rn1ty - didn't think there was anything to be done, MO has no issues with WB though MO2 does, what got me was that there seems to be a difference between the stand alone and the python versions as the python appears to be working go figure. That and the fact that running the stand alone I was getting the same popup but was able to just select to overwrite was why I was reporting it here with the latest 307.201709160706 build without MO2 in the picture at all.

Link to comment
Share on other sites

@Helidoc65 please confirm python version runs alright, interested to know. Re: this particular error should be caught anyway just fails to remove a tmp dir - will address in next nightly

 

EDIT:

Ok what happens is that Bash fails to delete _tmpfile when run through MO2 and then you run the standalone and it finds the file and it asks to overwrite (shouldn't ask). If running through MO2 it also fails to delete a tmp dir it creates and crashes (shouldn't) - it's the way that MO runs exes as opposed to python code (via python.exe I guess) ? Who knows

- Can you verify that a clean install of Bash (no need to delete the BP) and then running the "standalone - no MO2" the DATA/_tmpfile is cleared ok ?  post me the logs from this clean run please

That may mean that tmp dirs/files will be left behind (if above is correct only when run through MO2), not a huge deal, and nothing we can do about it on our end

Edited by Utumno
Link to comment
Share on other sites

@Utumno - Below are the logs from both the standalone - no MO2 and from the python version - no MO2.  Don't know how anyone got the python to run inside of MO2 can't get it to run on my system and at this point I most likely won't try... I hate vapor-ware seems MO2 is half baked from the original and never finished. I do have a question about the loot api seem WB was complaining about it... forgive if it has been discussed earlier, installed the latest per the readme and it did not like that at all. Appreciate all you do.

Standalone log

Spoiler

Wrye Bash starting
Using Wrye Bash Version 307.201709160706 (Standalone)
OS info: Windows-10-10.0.16288
Python version: 2.7.12
wxPython version: 2.8.12.1 (msw-unicode)
Using scandir 1.5
input encoding: None; output encoding: None; locale: ('en_US', 'cp1252')
filesystem encoding: mbcs
bash.pyo  324 main: Searching for game to manage:
bush.pyo   76 _supportedGames: Detected the following supported games via Windows Registry:
bush.pyo   78 _supportedGames:  Skyrim Special Edition: D:\Steam\steamapps\common\Skyrim Special Edition
bush.pyo   78 _supportedGames:  Skyrim: D:\Steam\steamapps\common\Skyrim
bush.pyo  136 _detectGames: Detecting games via the -o argument, bash.ini and relative path:
bush.pyo  146 _detectGames: No known game in parent directory of Mopy: D:\Steam\steamapps\common\StepDumpSE
bush.pyo  156 __setGame:  Using Skyrim Special Edition game: D:\Steam\steamapps\common\Skyrim Special Edition
testing UAC
mods_metadata.pyo  228 __init__: Using LOOT API version: 0.10.2

python logs

Spoiler

Startuplog-

Found Python at 'C:\Python27\pythonw.exe'
Launching Wrye Bash 307 in debug mode

Dumplog-

Wrye Bash starting
Using Wrye Bash Version 307
OS info: Windows-10-10.0.16288
Python version: 2.7.13
wxPython version: 2.8.12.1 (msw-unicode)
input encoding: UTF8; output encoding: None; locale: ('en_US', 'cp1252')
filesystem encoding: mbcs
bash.py  323 main: Searching for game to manage:
bush.py   76 _supportedGames: Detected the following supported games via Windows Registry:
bush.py   78 _supportedGames:  Skyrim Special Edition: D:\Steam\steamapps\common\Skyrim Special Edition
bush.py   78 _supportedGames:  Skyrim: D:\Steam\steamapps\common\Skyrim
bush.py  136 _detectGames: Detecting games via the -o argument, bash.ini and relative path:
bush.py  146 _detectGames: No known game in parent directory of Mopy: D:\Steam\steamapps\common\StepDumpSE
bush.py  156 __setGame:  Using Skyrim Special Edition game: D:\Steam\steamapps\common\Skyrim Special Edition
mods_metadata.py   41 <module>: Failed to import the loot_api module: (No module named loot_api)
testing UAC
 

 

 

Standalone was version 307.201709160706 and python was latest dev.zip download as of 2 hours prior to this post. And after I cleaned the trash from MO2 WB never asked for an overwrite for either version

Link to comment
Share on other sites

10 hours ago, Helidoc65 said:

So I have an issue with WB and MO2 with the latest build 307.201709160706 , I know as a matter of course that this can gets kicked down the road as you don't support WB being use within MO/MO2. That being said with the up coming changes to Win 10 in the Fall release several changes have been made to Win 10's kernel to correct the 4GB dx9 bug along with a few other issues and OS build 16288 is currently being run on both the slow and fast ring concurrently. The stand alone version when run comes up with a pop up in MO2 as shown here it also appears when run just as a stand alone without MO2 involved. The difference is with MO2 the program fails to launch but as just a stand alone without MO2 once the screen is bypassed (answered) the program will launch. From what I have gathered this effects just the stand alone version the python version seems to work although I have yet to confirm this for myself (reported from other users). I've included my logs from WB and MO2  to assist.

 

 

I can't discuss MO or MO2 in any detail.  I read comments that other people were saying, and someone pointed out to Tannin that I said something negative toward MO or MO2, when I was just responding to what I read from other people and he snapped at me about it as if I was to blame.  People just don't go out of their way to read every forum post in the world so...  Because of what MO/MO2 do even WrinklyNinja doesn't support it, and I don't use the program so I don't support it with xEdit either.  There simply isn't a check box in the Delphi compiler to add MO2 support.  I'm not trying to be sarcastic, there just isn't such a thing. Delphi just uses the standard system libraries.  However, MO and MO2 are not kicked down the road. The step community has assured me that to provide assistance to anyone.

Quote

mods_metadata.py   41 <module>: Failed to import the loot_api module: (No module named loot_api)

That by the way is not a bug it just means you don't have the DLL files and the correct version of LOOT installed.  Ignore that.  Aside from the DLL files you need for WB you need LOOT 10.1 or higher, although I have not tested things with anything higher then 10.1.

Link to comment
Share on other sites

1 hour ago, Sharlikran said:

I can't discuss MO or MO2 any longer. I read comments that other people were saying, and someone pointed out to Tannin that I said something negative toward MO or MO2, when I was just responding to what I read from other people and he snapped at me about it as if I was to blame.  People just don't go out of their way to read every forum post in the world so...  Because of what MO/MO2 do even WrinklyNinja doesn't support it, and I don't use the program so I don't support it with xEdit either.  There simply isn't a check box in the Delphi compiler to add MO2 support.  I'm not trying to be sarcastic, there just isn't such a thing. Delphi just uses the standard system libraries.  However, MO and MO2 are not kicked down the road. The step community has assured me that to provide assistance to anyone.

That by the way is not a bug it just means you don't have the DLL files and the correct version of LOOT installed.  Ignore that.  Aside from the DLL files you need for WB you need LOOT 10.1 or higher, although I have not tested things with anything higher then 10.1.

As far as Loot goes I have the latest version installed. 11.0 The API python module is Version 2.0.0 and if I read that correct, it's based off of 10.2, perhaps I need to do a bit of balancing there to get the two to play nice as when I installed the api into python it was a no go. That being said don't take my comments to heart about MO/MO2 my terminology was mainly meant that MO/MO2 is no longer being actively developed. While there are end-user support forums around for it there has only been one person who really made an attempt at taking it up and that has been hit and miss. Tannin has popped in from time to time to offer insight to some of the code work but due to his moving on to NMM .. well I'm sure you know all the rest. Last time I did any code work was 40 years ago and that was with punch cards, things were a bit different back then, so when I have an issue with something I ask around, don't mean to ruffle any feathers with my terminology and for that I apologize.

Link to comment
Share on other sites

@Helidoc65 I must admit I skimmed a bit, I read ..

Quote

So I have an issue with WB and MO2 with the latest build 307.201709160706 , I know as a matter of course that this can gets kicked down the road as you don't support WB being use within MO/MO2.

Then opened your spoiler with the bashbugdump and assumed it was related to MO/MO2 :facepalm:

---------------------------------------

@Utumno None of my previous problems with any wizard installers in the latest upload of standalone, and the more recent saves issue is also a confirmed fix as far as I can tell.

 

Wrye Bash starting
Using Wrye Bash Version 307.201709160706 (Standalone)
OS info: Windows-10-10.0.15063
Python version: 2.7.12
wxPython version: 2.8.12.1 (msw-unicode)
Using scandir 1.5
input encoding: None; output encoding: None; locale: ('en_GB', 'cp1252')
filesystem encoding: mbcs 
bash.pyo  324 main: Searching for game to manage:
bush.pyo   76 _supportedGames: Detected the following supported games via Windows Registry:
bush.pyo   78 _supportedGames:  Oblivion: e:\oblivion
bush.pyo   78 _supportedGames:  Skyrim Special Edition: D:\Steam\steamapps\common\Skyrim Special Edition
bush.pyo   78 _supportedGames:  Fallout4: D:\Steam\steamapps\common\Fallout 4
bush.pyo  136 _detectGames: Detecting games via the -o argument, bash.ini and relative path:
bush.pyo  142 _detectGames: Set game mode to Skyrim Special Edition found in parent directory of Mopy:  d:\Steam\steamapps\Common\Skyrim Special Edition
bush.pyo  156 __setGame:  Using Skyrim Special Edition game: d:\Steam\steamapps\Common\Skyrim Special Edition
testing UAC
mods_metadata.pyo  228 __init__: Using LOOT API version: 0.10.2
Link to comment
Share on other sites

@Sharlikran - Good didn't mean it that way. Me myself I just want a tool that works. On that note here is what I get from the latest dev version of WB Running the latest version of Loot and the latest api installed.

Startup

Spoiler

Found Python at 'C:\Python27\pythonw.exe'
Launching Wrye Bash 307 in debug mode
[2017-09-17 00:30:06.443380] [0x000030e0] [info]    Initialising load order data for game of type 5 at: "D:\Steam\steamapps\common\Skyrim Special Edition"
[2017-09-17 00:30:06.444381] [0x000030e0] [debug]   Loading file: "C:\Users\Helidoc\AppData\Local\LOOT\Skyrim Special Edition\masterlist.yaml"
[2017-09-17 00:30:06.451388] [0x000030e0] [trace]   Testing condition syntax:
[2017-09-17 00:30:06.453389] [0x000030e0] [debug]   Loading file: "D:\Steam\steamapps\common\StepDumpSE\Mopy\Bash Patches\Skyrim Special Edition\taglist.yaml"
[2017-09-17 00:30:06.454390] [0x000030e0] [trace]   Testing condition syntax:

 

BashBugDump

Spoiler

Wrye Bash starting
Using Wrye Bash Version 307
OS info: Windows-10-10.0.16288
Python version: 2.7.13
wxPython version: 2.8.12.1 (msw-unicode)
input encoding: UTF8; output encoding: None; locale: ('en_US', 'cp1252')
filesystem encoding: mbcs
bash.py  323 main: Searching for game to manage:
bush.py   76 _supportedGames: Detected the following supported games via Windows Registry:
bush.py   78 _supportedGames:  Skyrim Special Edition: D:\Steam\steamapps\common\Skyrim Special Edition
bush.py   78 _supportedGames:  Skyrim: D:\Steam\steamapps\common\Skyrim
bush.py  136 _detectGames: Detecting games via the -o argument, bash.ini and relative path:
bush.py  146 _detectGames: No known game in parent directory of Mopy: D:\Steam\steamapps\common\StepDumpSE
bush.py  156 __setGame:  Using Skyrim Special Edition game: D:\Steam\steamapps\common\Skyrim Special Edition
testing UAC
mods_metadata.py  225 __init__: Using LOOT API version: 0.11.0
mods_metadata.py  281 refreshBashTags: An error occurred while parsing file C:\Users\Helidoc\AppData\Local\LOOT\Skyrim Special Edition\masterlist.yaml:
Traceback (most recent call last):
  File "bash\bosh\mods_metadata.py", line 274, in refreshBashTags
    lootDb.load_lists(path.s)
RuntimeError: bad cast

mods_metadata.py  296 refreshBashTags: An error occurred while parsing taglist.yaml:
Traceback (most recent call last):
  File "bash\bosh\mods_metadata.py", line 292, in refreshBashTags
    lootDb.load_lists(self.tagList.s)
RuntimeError: bad cast

Traceback (most recent call last):
  File "Wrye Bash Launcher.pyw", line 89, in <module>
    bash.main(opts)
  File "bash\bash.py", line 429, in main
    app.Init() # Link.Frame is set here !
  File "bash\basher\__init__.py", line 4005, in Init
    self.InitData(progress)
  File "bash\basher\__init__.py", line 4044, in InitData
    bosh.modInfos.refresh()
  File "bash\bosh\__init__.py", line 1967, in refresh
    self.reloadBashTags()
  File "bash\bosh\__init__.py", line 2147, in reloadBashTags
    mod.reloadBashTags()
  File "bash\bosh\__init__.py", line 730, in reloadBashTags
    tags, removed, _userlist = configHelpers.getTagsInfoCache(self.name)
  File "bash\bosh\mods_metadata.py", line 305, in getTagsInfoCache
    tags = lootDb.get_plugin_tags(modName.s)
RuntimeError: bad cast

WB CTD's right after I select the game and initial splash screen.

Link to comment
Share on other sites

Okay the settings for 11 are the same as for 10.1. So the masterlist syntax hasn't changed.  So what happens is you need to go to the mopy folder for the game you are using Wrye with. For example Skyrim should be the Skyrim\Mopy folder. You need two dll files, one named loot_api.dll and the other loot_api.pyd. They go in the Mopy folder as far as I know, or at least that's where I have them.  Then go to the C:\Users\[username]\AppData\Local\LOOT or you local AppData folder, and delete the settings.yaml and the folder for the game, again for example skyrim. Then run LOOT without MO2 and download a new masterlist for Skyrim. Then go into MO2 and see what happens when you start Wrye bash.

Link to comment
Share on other sites

Not using MO2, stopped earlier today after it just would not work. That being said, I deleted the settings.yaml file and the directory for the effected game in this case Skyrim SE. Ran Loot, again not using MO2 then ran WB and it still CTD.

Logs from this crash. The version of loot_api.dll and loot_api.pyd are from here https://github.com/loot/loot-api-python/releases/tag/2.0.0:)

 

Spoiler

Found Python at 'C:\Python27\pythonw.exe'
Launching Wrye Bash 307 in debug mode
[2017-09-17 02:43:37.955005] [0x00001678] [info]    Initialising load order data for game of type 5 at: "D:\Steam\steamapps\common\Skyrim Special Edition"
[2017-09-17 02:43:37.956006] [0x00001678] [debug]   Loading file: "C:\Users\Helidoc\AppData\Local\LOOT\Skyrim Special Edition\masterlist.yaml"
[2017-09-17 02:43:37.962012] [0x00001678] [trace]   Testing condition syntax:
[2017-09-17 02:43:37.965015] [0x00001678] [debug]   Loading file: "D:\Steam\steamapps\common\StepDumpSE\Mopy\Bash Patches\Skyrim Special Edition\taglist.yaml"
[2017-09-17 02:43:37.965015] [0x00001678] [trace]   Testing condition syntax:

Wrye Bash starting
Using Wrye Bash Version 307
OS info: Windows-10-10.0.16288
Python version: 2.7.13
wxPython version: 2.8.12.1 (msw-unicode)
input encoding: UTF8; output encoding: None; locale: ('en_US', 'cp1252')
filesystem encoding: mbcs
bash.py  323 main: Searching for game to manage:
bush.py   76 _supportedGames: Detected the following supported games via Windows Registry:
bush.py   78 _supportedGames:  Skyrim Special Edition: D:\Steam\steamapps\common\Skyrim Special Edition
bush.py   78 _supportedGames:  Skyrim: D:\Steam\steamapps\common\Skyrim
bush.py  136 _detectGames: Detecting games via the -o argument, bash.ini and relative path:
bush.py  146 _detectGames: No known game in parent directory of Mopy: D:\Steam\steamapps\common\StepDumpSE
bush.py  156 __setGame:  Using Skyrim Special Edition game: D:\Steam\steamapps\common\Skyrim Special Edition
testing UAC
mods_metadata.py  225 __init__: Using LOOT API version: 0.11.0
mods_metadata.py  281 refreshBashTags: An error occurred while parsing file C:\Users\Helidoc\AppData\Local\LOOT\Skyrim Special Edition\masterlist.yaml:
Traceback (most recent call last):
  File "bash\bosh\mods_metadata.py", line 274, in refreshBashTags
    lootDb.load_lists(path.s)
RuntimeError: bad cast

mods_metadata.py  296 refreshBashTags: An error occurred while parsing taglist.yaml:
Traceback (most recent call last):
  File "bash\bosh\mods_metadata.py", line 292, in refreshBashTags
    lootDb.load_lists(self.tagList.s)
RuntimeError: bad cast

Traceback (most recent call last):
  File "Wrye Bash Launcher.pyw", line 89, in <module>
    bash.main(opts)
  File "bash\bash.py", line 429, in main
    app.Init() # Link.Frame is set here !
  File "bash\basher\__init__.py", line 4005, in Init
    self.InitData(progress)
  File "bash\basher\__init__.py", line 4044, in InitData
    bosh.modInfos.refresh()
  File "bash\bosh\__init__.py", line 1967, in refresh
    self.reloadBashTags()
  File "bash\bosh\__init__.py", line 2147, in reloadBashTags
    mod.reloadBashTags()
  File "bash\bosh\__init__.py", line 730, in reloadBashTags
    tags, removed, _userlist = configHelpers.getTagsInfoCache(self.name)
  File "bash\bosh\mods_metadata.py", line 305, in getTagsInfoCache
    tags = lootDb.get_plugin_tags(modName.s)
RuntimeError: bad cast

 

 

Link to comment
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
 Share

×
×
  • Create New...