- #Skyrim se sseedit autopatch install
- #Skyrim se sseedit autopatch mod
- #Skyrim se sseedit autopatch Pc
- #Skyrim se sseedit autopatch series
Reinstalled everything with fresh downloads. Uninstalled both SkyrimSE, MO2 and xedit.
During this past week of banging my head against this wall I've attempted the following: That done I listened to the far more knowledgable than me and wanted to clean my Bethesda esms, unfortunately each time I get the above message. I checked the my games folder within my documents on my system drive and noted that both ini's were present.įired up MO2, configured it to access my Nexus account, opened up the modify executables tool and entered the following (my entry in italics):īinary: E:\MO2 SSE\SSEEdit 4.0.1\SSEEdit.exe I followed this up with launching the game from both the SkyrimLauncher and the Skyrim.exe based on previous experience of needing to generate ini's, set my display preferences and exited the game without playing it. (GP's videos said it doesn't matter where you drop xedit so assuming that's not a issue).
Then I extracted xedit 4.0.1 and dropped the extrracted folder into the same folder as MO2, meaning that xedit sits in it's own folder within the MO2 folder. From within xedit I told it to set the base directory to my Game drive "E:\MO2 SSE", and based on my understanding of the video, left the rest at %BASE_DIR%/Downloads, etc.
#Skyrim se sseedit autopatch series
I hunted for a solution found Gamer Poet's series and followed it's suggestions closely.
#Skyrim se sseedit autopatch Pc
Not too keen on it being on my system SSD, I like to keep my pc gaming all on a 2 TB HDD purposed for Steam and related utilities.
#Skyrim se sseedit autopatch install
Launched it and MO2 defaulted to install into my user/local/appdata drive.
#Skyrim se sseedit autopatch mod
In case the above isn't enough, below is my best recollection of this situation's evolution Īfter comparing mod organizers I decided on MO2, downloaded the installer version, created a MO2 folder on my Game drive (E) and dropped the executable there. Using ini: C:\Users\Fherrit Den\AppData\Local\Temp\My Games\Skyrim Special Edition\Skyrim.ini Using Cache Path: E:\steam\steamapps\common\Skyrim Special Edition\Data\SSEEdit Cache\ Using Scripts Path: E:\MO2 SSE\SSEEdit 4.0.1\Edit Scripts\
Using Backup Path: E:\steam\steamapps\common\Skyrim Special Edition\Data\SSEEdit Backups\ Using Skyrim Special Edition Data Path: E:\steam\steamapps\common\Skyrim Special Edition\Data\ Right off the bat, I'm running into issues because I can't clean the Beth esm's at all, in fact I can't clean anything with either TESV or SSEEdit for their respective games, I keep getting this error mesage. Recently I upgraded my rig and was more or less forced into Win10 from Win7 (long story, not worth going into) and I'm constantly encountering little gotchas from Win10 with many of my programs with this possibly being another example.Īnyway, here is the issue, after making the move from NMM to MO2 and deciding to give SkyrimSE a try I'm building a modded game following TUCO's guide. So basically I'm not completely ignorant and have some experience with how essential utilities such as Xedit, Wyre and mod organizers are. I've used TESV and TES4 a fair bit in the past with my most recent game of Oblivion seeing the most amount of use of the utility. I'm of what I would say "middling" experience with modding.
0 kommentar(er)
