- #Working with skse and mod organizer install#
- #Working with skse and mod organizer mods#
- #Working with skse and mod organizer zip#
- #Working with skse and mod organizer download#
The Steam option isn’t necessarily recommended as you’ll have less control of SKSE than if you had installed it using a manager.
If you’ve downloaded it from Steam, SKSE will appear in your game library. MO will have a shortcut feature built in, or feel free to make a shortcut yourself.
#Working with skse and mod organizer mods#
You will be using this shortcut to open Skyrim, or else any mods depending on SKSE won’t work.
When installing manually, NNM, or MM after installing you’ll need to go to your skyrim folder (C:Program Files (x86)SteamsteamappscommonSkyrim) and find skse_loader and make a shortcut of it on your desktop.
#Working with skse and mod organizer download#
If you’d like to use a manager go ahead and download the zipped version and use the guide above. This one’s a bit tricky! There is a steam version, installer and a zipped folder available for download. SKSE or the Steam download (not recommended) If you’re not sure what I’m talking about, here’s another Gopher video for you! I’m going to list installation notes for the above mods in the order I recommend installing them in.
#Working with skse and mod organizer install#
#Working with skse and mod organizer zip#
You can drag and drop the logs directly on github to send them (tip: zip them if they are too big). 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. Once you have reproduced the problem, 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. To access the log files you can press the Open folder icon over the modlist and select "Open MO2 Logs folder".īefore 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. Thanks for testing it, could you submit your debug logs of the issue while using the new usvfs patch?