Repository navigation
Outlander 3.0
Why 3.0?
Too many mods required updates and I had several errors pop up on older saves, I think most older saves will not work. Feel free to try it if you like.
What's changed other than mod updates?
- New shader chain, including a sick CRT shader by SafeBox. I personally love the CRT shader on Morrowind, it really enhances the vibes. Of course, if you aren't a fan of it, it can be disabled in MGE XE's Shader settings without any issue, either in game with the MGE XE MCM or by launching MGE XE in Mod Organizer and clicking the "Shaders" button, then "Modding". The new shader chain is focused on making dungeons and nights darker. Light sources (or magic lights) required!
- Better FPS thanks to a new mod, Dynamic FPS Optimization. This mod changes your view distance dynamically to improve FPS, but it isn't too noticeable thanks to Distant Land. You may notice some objects fade in and out, but the FPS saved in low performance areas like Vivec City is quite impressive. Of course, this is still the old engine running on modern hardware, so don't expect too much. If you prefer lower framerates to object pop in, you can disable this mod without issue.
- New soundtrack with MUSE Music Expansion. This replaces Morrowind's original soundtrack with something more ambient, dynamic, and atmospheric, with tracks specific to Redoran, Hlaalu, Telvanni, Sixth House, Ashlander, Dwemer, Imperial, Deadric, and Undead controlled areas. Combat music is still the original tracks, but now won't play for low threat enemies. You can disable the MUSE Music Expansion mods if you would like to play with the original soundtrack.
- Quest notification system similar to Skyrim's. Now you'll know whenever you start and end a quest with a sick Sixth House chime and a pop up.
- The Joy of Painting has now officially been added, no need to install ImageMagick!
Reminder: Do NOT report bugs to mod authors! If you find a bug while playing Outlander, report it to my Discord! I will find the source of the issue and report the fix to the mod author if needed. Most of the time, bugs arise between two mod incompatibilities, and not because of a single mod. It gets really annoying for mod authors to get reports from Wabbajack list users, as they tend not to know the intimate details of the mods they are using.
Known issues:
- Several errors regarding "aa_loot_DB" on start. Seems to be benign for now, and I haven't been able to identify the offending mod(s). Just hit "Yes to all" on start up.
- Poor performance in Ashfall camps with lots of activators.
- Occasional crash when arriving to a destination via Silt Strider. This only happened to me twice, each time with no error message in the log. I recommend saving before utilizing the silt strider service.