Jump to content

Weird Wrye Bash Error


BinaryMessiah

Recommended Posts

I've been using Wrye Bash for 3 years now, and out of nowhere I'm getting the following error upon startup

 

Traceback (most recent call last):
File "bash\balt.pyo", line 1803, in _conversation_wrapper
File "bash\basher\__init__.pyo", line 4116, in RefreshData
File "bash\basher\__init__.pyo", line 4196, in _corruptedWarns
File "bash\balt.pyo", line 1215, in Display
File "bash\balt.pyo", line 2799, in __init__
File "bash\balt.pyo", line 481, in listBox
File "wx\_controls.pyo", line 1290, in __init__
TypeError: String or Unicode type required

 

 

I researched and can't find out what this means. I have reinstalled Wrye Bash twice and it won't go away. I'm noticing it was auto refresh anymore when clicking back into the window.

Link to comment
Share on other sites

  • 2 months later...

I'm new to using Wrye Bash and only installed it recently (Standalone version 306).

 

Every time I boot it up I get this error:

 

Traceback (most recent call last):
File "bash\balt.pyo", line 1796, in _conversation_wrapper
File "bash\basher\__init__.pyo", line 4101, in RefreshData
File "bash\basher\__init__.pyo", line 4181, in _corruptedWarns
File "bash\balt.pyo", line 1206, in Display
File "bash\balt.pyo", line 2792, in __init__
File "bash\balt.pyo", line 483, in listBox
File "wx\_controls.pyo", line 1290, in __init__
TypeError: String or Unicode type required

 

Also, I discovered that any changes made with the Tweak Settings when rebuilding the patch do not take effect in-game. So, naturally, now I don't trust the patch, even though I get no other errors when using the program.

 

I don't have any esp files with dirty edits, but obviously there is a file WB is scanning somewhere it doesn't like, even though it boots up quickly and seems to be running fine (on the surface) with no other errors. (sigh)

 

I'm assuming it's some particular mod that is the culprit and a commonly-used one, apparently, since I've seen this complaint from several people so far.

 

I've been working on this build for several weeks and I'm ready to get started (dammit). I thought it was squeaky-clean, but this one glitch is making me afraid to start playing and making saves. Hopefully someone will discover why this is occurring and post it.

Link to comment
Share on other sites

  • 3 months later...

Yeah, same here. I've used Wrye Bash for a while now and have not added a different load order. I get that exact same error and I can't find a solution. Every mod I use has been cleaned, I've reinstalled Wrye Bash with NMM the latest versions of both. I still get that error lately. Don't know why.
I've even gone to google and have found lots of recent posts about the same issue but with no solution to it or understanding of the reason behind it.

Link to comment
Share on other sites

Yeah, same here. I've used Wrye Bash for a while now and have not added a different load order. I get that exact same error and I can't find a solution. Every mod I use has been cleaned, I've reinstalled Wrye Bash with NMM the latest versions of both. I still get that error lately. Don't know why.

I've even gone to google and have found lots of recent posts about the same issue but with no solution to it or understanding of the reason behind it.

I'm having the same issue. I wonder if it has something to do with a Java update. It seems to have started after I updated Java.

Link to comment
Share on other sites

  • 1 month later...
  • 1 month later...

Just had this error exactly as quoted above. I had downloaded some new mods so I unchecked them all and rechecked them one by one. It was caused by the mod Frostmourne nexus id 6031. My suggestion to anyone with this error is to sort your mods by install date and disable the recent. Then re-enable them one by one and start Wrye Bash until you find the culprit.

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...