Jump to content

Wrye Issue


jamsey117

Recommended Posts

Hi,

 

Skyrim Special Edition is running fine so far with Vortex (1.4.15) and the mods I've installed. I'm at the point where I'm trying to create a Bashed patch through Wrye. However, I'm having some issues with creating the patch itself. I'm not sure if this is a problem caused by Vortex, Wrye, or my SSE saves folder location. Here what I have done to replicate the issue:

 

Install:

- I installed Wrye Bash using the v309.1 installer.

- I chose SkyrimSE as my game and ensured the file path pointed to the correct location in my steam folder.

- I have checked that the Mopy folder is placed in the same location as SkyrimSE.exe.

- Mopy contains Wrye Bash.exe and other related folders and files.

 

 

Running:

- Running Wrye Bash.exe opens the application as normal. (I do get a "Mismatched BSA Versions" warning)

- It correctly detects and displays the mods I have installed in the mods tab.

- When I go to create a Bashed Patch, I get the following warning: "Update.esm: Bad Top GRUP type: 'VOLI'"

- After googling the issue I found a couple of posts saying that 'VOLI' is SSE specific

- I checked the general settings, and found the Managed Game option was set to 'Skyrim'.

- I believe Wrye "thinks" I'm running Skyrim instead of SSE.

 

(Note: I do not have any other version of Skyrim installed. Only Skyrim Special Edition. Despite this, Wrye seems hell bent on only running for Skyrim. In "C:\Users\user1\Documents\My Games" Wrye, actually CREATES a Skyrim folder with a new Skyrim.ini and Saves folder etc. My actual Skyrim.ini and save games are in a Skyrim Special Edition folder right next to this newly created folder.)

 

 

Attempted fixes:

- Changing Managed Game from Skyrim to Skyrim Special edition I get a warning about automatic reinstallation using the proper -o command line argument. The window then proceeds to close but the program hangs in the background.

- Maybe my install was wrong? I've reinstalled Wrye a few times now, making absolutely sure I'm selecting the correct options. If you have doubts I can run through the exact steps I take.

- I've looked at the bash_default.ini, and included the line "sOblivionPath=C:\Steam\steamapps\common\Skyrim Special Edition", and saved as bash.ini. I'm not sure about adding in any other lines since they don't seem to be related to what game Wrye is detecting or any path to the Skyrim.ini.

 

 

In conclusion, Wrye seems to only want to work for Skyrim and despite installing it in the correct location I'm unable to get it to work for SSE. I feel like I've tried the obvious solutions but I'm just not able to figure it out. Could this be an issue with how Vortex is managing my game? Sorry for the length of this post. If it is unclear, or you want more details, please ask. Apologies in advance if I've missed something obvious (as I'm sure I have...).

 

Love,

Jim

Link to comment
Share on other sites

Uninstall/reinstall Wrye, making sure that you are using the correct game setting. Also, make sure that you are using this version: https://www.nexusmods.com/skyrimspecialedition/mods/6837 Use the "installer" version.

Link to comment
Share on other sites

Uninstall/reinstall Wrye, making sure that you are using the correct game setting. Also, make sure that you are using this version: https://www.nexusmods.com/skyrimspecialedition/mods/6837 Use the "installer" version.

 

Thank you but I've already used both the standalone and the installer versions from that link and I get the same issue with each! I've probably reinstalled both 4 or 5 times now and am absolutely choosing Special Edition each time :(

 

 

If Wrye is saying you're running a different game, that sounds like the issue is with that application. I think there are some newer apps that can create bashed patches available now (such as Mator SMASH?).

I'm beginning to think it is the application's fault. I've heard of Mator but wasn't sure if it did the same thing. I'll give that a try :)

Link to comment
Share on other sites

It's not Wrye's fault not Vortex's. I currently use Wrye for SSE, FNV, and Oblivion all through Vortex. It's user error. Either you are installing it incorrectly or something is up with your machine. There is no need to alter any ini's to get WB to work on multiple games. Wrye is still being updated and is arguably more functional than MATOR at this point. Check the Wrye BASH Discord.

 

If you feel it is not definitely on your end , then I would report as a bug on their discord.

Link to comment
Share on other sites

I have Wryebash "installed" for Oblivion, Fallout New Vegas, Enderal, SSE, and Fallout 3, some in Steam, some in GOG.

I said "install", because all I ever do, is download the EXE Standalone Version, and Slap the MOPY directory in the root directory of the games I mentioned and go.
I DO NOT EDIT ANY OF THE WRYE INI FILES

I set up the "new tool" in the Vortex dashboard by putting in the following (your path will be different) in the START IN and TARGET fields

TARGET: D:\Games\Steam\steamapps\common\Skyrim Special Edition\Mopy\Wrye Bash.exe
START IN: D:\Games\Steam\steamapps\common\Skyrim Special Edition\Mopy

That's it.

AFAIK, Mator doesn't support large load orders (yet), whereas Wrye Does.

Link to comment
Share on other sites

I just redownloaded the standalone 7z, extracted, dragged Mopy into:

 

C:\Steam\steamapps\common\Skyrim Special Edition

 

Left the bash_default.ini as is.

 

Vortex target:

 

C:\Steam\steamapps\common\Skyrim Special Edition\Mopy\Wrye Bash.exe

 

Vortex startin:

C:\Steam\steamapps\common\Skyrim Special Edition\Mopy

 

Same issue... Using the installer or just dragging the Mopy folder into Skyrim Special Edition seems idiot proof. So maybe there is something weird going on with my machine, but I can't imagine what. It's relatively 'new' and every other modding tool I've used has worked just fine (xEdit, Nemesis, etc.). So now I feel more hesitant to call this a bug, especially if no one can reproduce this or has the same issue. Just as a sanity check, are you able to get this working with the 309.1 version?

 

Also, someone has apparently removed the plugin limit: Unofficial Mator Smash Updated

 

This let me generate a patch, but I haven't had time to check it out in detail.

Link to comment
Share on other sites

I just redownloaded the standalone 7z, extracted, dragged Mopy into:

 

C:\Steam\steamapps\common\Skyrim Special Edition

 

Left the bash_default.ini as is.

 

Vortex target:

 

C:\Steam\steamapps\common\Skyrim Special Edition\Mopy\Wrye Bash.exe

 

Vortex startin:

 

C:\Steam\steamapps\common\Skyrim Special Edition\Mopy

 

Same issue... Using the installer or just dragging the Mopy folder into Skyrim Special Edition seems idiot proof. So maybe there is something weird going on with my machine, but I can't imagine what. It's relatively 'new' and every other modding tool I've used has worked just fine (xEdit, Nemesis, etc.). So now I feel more hesitant to call this a bug, especially if no one can reproduce this or has the same issue. Just as a sanity check, are you able to get this working with the 309.1 version?

 

Also, someone has apparently removed the plugin limit: Unofficial Mator Smash Updated

 

This let me generate a patch, but I haven't had time to check it out in detail.

 

 

I had a LOT of problems with the newest wryebash, it would crash on start up, and I remember now that I moved EVERYTHING from my SSE my Documents\My Games\Skyrim Special Edition folder to another drive, and then I let WryeBash regenerate the BASH folders in the Documents\My Games\GAME folders and then Copied all the folders I moved EXCEPT THE BASH FOLDERS, back into the Documents\My Games\GAME folder and that got everything working correctly.

 

Try that

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
  • Recently Browsing   0 members

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