unnownrelic

Oh jeez, that fixed it right up. Thank goodness for the clever people. Consider this fixed, I guess.

Hello! This problem is painfully similar to https://forum.step-project.com/showthread.php?tid=3856, and is almost identical except for the part where I try to launch Wrye Bash at all through MO. WB launches independently on its own with both the python and standalone version, but trying to use either through MO results in the error I put in the code box below. This occurs after getting through step 2.D of STEP 2.2.8 core, with WB versions 303 through 304.3, both standalone and python. The error message I'm using below is for 303, but the others are all very similar except for +/- a few on some of the line numbers. This does NOT occur when trying to run WB on my profile that has STEP 2.2.7 extended fully loaded up, nor does it happen with a completely vanilla profile up to step 2.c. I'll keep trucking through to the end of 2.E to see if anything changes and come back to update my findings. Also this is using MO 1.1.1. I haven't gone back to an earlier version of MO yet to see if that makes a difference. Error! Unable to start Wrye Bash. Please ensure Wrye Bash is correctly installed. Traceback (most recent call last):  File "bash\bash.py", line 427, in main  File "bash\bosh.py", line 30342, in initBosh  File "bash\bosh.py", line 30088, in initDirs  File "bash\bosh.py", line 3642, in __init__  File "bash\bosh.py", line 3121, in getSetting  File "bash\bosh.py", line 3129, in getSettings  File "bash\bosh.py", line 3157, in getTweakFileSettings  File "encodings\cp1252.pyo", line 15, in decode UnicodeDecodeError: 'charmap' codec can't decode byte 0x9d in position 110: character maps to <undefined>

Alright, finally got home to test it out and it worked 100%. Thanks DoubleYou!

D'oh, I missed that somehow, I knew it would be something simple. Thanks for pointing me there.

I'm sure I'm making a silly mistake, but I think I'm following the directions properly so far. Presently I'm on step 1.E. for the STEP guide, and using the Mod Organizer program to run patchers, wrye bash, and whatever else mod-related needs to be run as necessary. When trying to run the SkyProc patcher for DSR, it appears to complete and then at the end says that I need to have Dual Sheath Redux.esp in my load order. It is, in fact, in there, according to Mod Organizer's load order. At any rate, the Dual Sheath Redux Patch.esp file is created at the end of the process and it shows up at the bottom of my load order after restarting MO to let it detect. This is where the notable problems start. Running Wrye Bash tells me that the DSR patch ESP file has corrupted headers and ignores it in its load order. If I ignore this and run the game anyway, it says that the DSR patch ESP file is not present even though it's been checked and added to the load order, and it proceeds to disable DSR completely. For reference, I'm running Dual Sheath Redux Patch.jar through a bat file, which is then activated via MO. javaw.exe is set to run as administrator per settings directly applied to its executable, though I can't seem to force that option to be on for the .jar or the .bat, probably because they're not standard executables. Any ideas? And if you need any extra information about my set-up feel free to ask, I've been benching as I go and making sure to keep notes.