Wrye Bash Issue (Solved)

[SilentAegis]

Hello there! To get to the point, my Wrye Bash seems to be unable to detect my Mod Organizer's mods for my Skyrim. For some reason, it's trying to read Fallout 4, but all my directories aim towards Skyrim, which is odd.

If your Wrye Bash works, perhaps we can compare directories or something? Any other ideas are appreciated. Thanks.

[Dexter]

You are running Wrye Bash via Mod Organizer right?

[cfs111]

From MO2 Discord...
Programs can't see the mods:
1) First thing is that programs like the game and LOOT that you want to be able to see the mods need to be launched from Mo2 to be hooked by the MO2 Virtual File System (USVFS) so you need to be doing that.
2) You should check whether USVFS is actually running and is not blocked for some reason, to do that you should check if the USVFS logs in the MO2 logs folder are empty (write !get logs on this channel for info on how to get the logs). Best way to check is to delete all the logs there, run MO2, run the program not seeing the mods, close both and check if the usvfs logs contain something.
If the logs result empty write !get blanklogs in this channel to see reasons and solutions for that case.
3) If the logs are not empty you should upload them on discord so we can see what is going on, best if you follow the instructions provided by !get debuglogs to set them to debug level information.
One possibility though is that the program that you are starting through MO2 is not looking at the same game installation that is being managed, thus not seeing the mods, please check that isn't the case.
4) If you have issues with SKSE not seeing SKSE plugins and you are using a Steamless game executable then you should add the -forcesteamloader argument to the SKSE executable.

[cfs111]

And in case you need it...
To access the log files you can press the Open folder icon over the modlist and select "Open MO2 Logs folder". Before sending any Logs make sure the Log Level is set to Debug in Settings\Diagnostics, then close MO2 and clean the logs folder, after that you can reopen MO2 and reproduce the problem once done close MO2, before sending or examining the logs as they are finished writing only after the program is closed; after you have finished testing setting the log level back to default is recommended.
You should always send the mo_interface.log file as that one contains the general information of your setup, for the usvfs log, you should upload the latest one if the issue is about programs started through Mo2.
You can drag and drop the logs directly on discord to send them (tip: zip them if they are too big). https://cdn.discordapp.com/attachments/458597400638914563/458728891620524032/unknown.png

[SilentAegis]

Originally posted by dexter411:

You are running Wrye Bash via Mod Organizer right?

Yup, it's all set up, but it doesn't work.

[SilentAegis]

Originally posted by cfs111:

From MO2 Discord...
Programs can't see the mods:
1) First thing is that programs like the game and LOOT that you want to be able to see the mods need to be launched from Mo2 to be hooked by the MO2 Virtual File System (USVFS) so you need to be doing that.
2) You should check whether USVFS is actually running and is not blocked for some reason, to do that you should check if the USVFS logs in the MO2 logs folder are empty (write !get logs on this channel for info on how to get the logs). Best way to check is to delete all the logs there, run MO2, run the program not seeing the mods, close both and check if the usvfs logs contain something.
If the logs result empty write !get blanklogs in this channel to see reasons and solutions for that case.
3) If the logs are not empty you should upload them on discord so we can see what is going on, best if you follow the instructions provided by !get debuglogs to set them to debug level information.
One possibility though is that the program that you are starting through MO2 is not looking at the same game installation that is being managed, thus not seeing the mods, please check that isn't the case.
4) If you have issues with SKSE not seeing SKSE plugins and you are using a Steamless game executable then you should add the -forcesteamloader argument to the SKSE executable.

Originally posted by cfs111:

And in case you need it...
To access the log files you can press the Open folder icon over the modlist and select "Open MO2 Logs folder". Before sending any Logs make sure the Log Level is set to Debug in Settings\Diagnostics, then close MO2 and clean the logs folder, after that you can reopen MO2 and reproduce the problem once done close MO2, before sending or examining the logs as they are finished writing only after the program is closed; after you have finished testing setting the log level back to default is recommended.
You should always send the mo_interface.log file as that one contains the general information of your setup, for the usvfs log, you should upload the latest one if the issue is about programs started through Mo2.
You can drag and drop the logs directly on discord to send them (tip: zip them if they are too big). https://cdn.discordapp.com/attachments/458597400638914563/458728891620524032/unknown.png

Alright, I'll try the stuff you mentioned, but you should know I'm using the original Mod Organizer, not the second one.

[cfs111]

Ah, well that may change things a bit. But, what version of WB? In MO in the Modify Executables edit WB by adding this line in the arguments block...

-o "C:\\Steam\\Steamapps\\common\\Skyrim\\"

with the path pointing to your skyrim install.

[SilentAegis]

Originally posted by cfs111:

Ah, well that may change things a bit. But, what version of WB? In MO in the Modify Executables edit WB by adding this line in the arguments block...

-o "C:\\Steam\\Steamapps\\common\\Skyrim\\"

with the path pointing to your skyrim install.

Thanks for the fast replies. And I'm using the one from the Nexus. Version 307 Beta3.

Using the argument you gave me (after changing it to fit my install location) gave me the following error:

Wrye Bash encountered an error.
Please post the information below to the official thread at:
https://afkmods.iguanadons.net/index.php?/topic/4966-wrye-bash-all-games/& or
https://bethesda.net/community/topic/38798/relz-wrye-bash-oblivion-skyrim-skyrim-se-fallout-4/

Traceback (most recent call last):
File "bash\bash.pyo", line 188, in main
File "bash\bash.pyo", line 263, in _main
File "bash\bash.pyo", line 381, in _detect_game
File "bash\initialization.pyo", line 161, in init_dirs
File "ConfigParser.pyo", line 242, in __init__
AttributeError: 'unicode' object has no attribute 'items'

[cfs111]

Try backing up to version 306. You may need to get in touch with the wrye bash team.

[smr1957]

What cfs said - I use v.306 for Oldrim as v.307 causes problem for it. You can get Wrye Bash version 306 here:
https://github.com/wrye-bash/wrye-bash/releases
You want the installer

[SilentAegis]

Reverting to a previous version worked. Thanks, you two. :D

EDIT: If I could, I'd choose both of your responses as the answer, but cfs111 beat smr1957 to it. :P