Kohlibri1997 Posted January 18, 2018 Share Posted January 18, 2018 (edited) I'm completely out of ideas what to do with my modlist. I don't know what's wrong after checking LOOT and TES5Edit. When I try to start Skyrim with SKSE i got to the main menu but the options and the music where missing. After activating and deactivating some mods to find out if something changes my Skyrim doesn't start at all. Loadorder: https://pastebin.com/uyEwVc6f (Hunterborn Patches, Bashed Patch, CACO SkyBirds Patch and ETaC Complete LOS Patch are disabled) SkyrimPrefs.ini: https://pastebin.com/qn5DdeNE Skyrim.ini: https://pastebin.com/ck1Uuiu9 SKSE.ini: https://pastebin.com/SKQzfU0C CrachFixPlugin.ini: https://pastebin.com/8HPv9h16 Papyrus: https://pastebin.com/Ldgd6YrT Edited January 18, 2018 by Kohlibri1997 Link to comment Share on other sites More sharing options...
Novem99 Posted January 18, 2018 Share Posted January 18, 2018 (edited) Ich würde an deiner Stelle alle mods, von denen DU keine Ahnung hast, was sie genau alles bewirken, deinstallieren. Und ich fürchte in diesem Falle sind das eine ganze Menge mods! 258 plugins...und da wunderst du dich, daß dein Spiel nicht funktioniert? Edited January 18, 2018 by Novem99 Link to comment Share on other sites More sharing options...
Kohlibri1997 Posted January 18, 2018 Author Share Posted January 18, 2018 Als ich zuletzt mit einer ähnlichen Anzahl an Mods gespielt habe, hat eine Zeit lang alles perfekt funktioniert. Irgendwann hab ich noch ein paar Mods hinzugefügt und einen Fehler bekommen, den ich zuvor durch neu installieren von MO lösen konnte. Dabei habe ich aber ausversehen die installierten Mods und die Downloads mitgelöscht. Dies habe ich abgebrochen und beim versuch die gelöschten Mods zu ersetzen hat SkyUI gestreikt und mein Game hat behauptet, ich hätte einen Mod installiert, den ich in meinem Leben noch nie runtergeladen habe. Daraufhin habe ich Skyrim und MO deinstalliert und nochmal ganz von vorne angefangen. Zu meinen aktuellen Mods habe ich einfach keine Ahnung, was genau der Fehler ist. Ich habe keine Fehler in LOOT, habe alle möglich Compability Patches installiert und ITMs und Deleted References mit TES5Edit behoben. Und im Papyrus Log finde ich auch keine richtigen Hinweis, woran der Fehler liegt, weil der Log immer so aussieht, egal ob mein Skyrim funktioniert oder nicht. Ich will aktuell erst mal herausfinder, was das Problem ist und versuchen das zu beheben. Ich bin es nämlich ehrlich gesagt satt alle Mods immer wieder von neu zu installieren, weil mir das in den letzten Jahren schon zu oft passiert ist. Link to comment Share on other sites More sharing options...
Grospolina Posted January 20, 2018 Share Posted January 20, 2018 A lot of people using Wrye Bash 307 beta2 are having this problem. Either delete the bashed patch and redo it using Wrye Bash 307 beta1 (bottom), or read up on the Wrye Bash Posts section. Link to comment Share on other sites More sharing options...
Kohlibri1997 Posted January 20, 2018 Author Share Posted January 20, 2018 With "disabled" I meant that they aren't activated because I don't need them and I can't even start Wrye Bash with MO. Link to comment Share on other sites More sharing options...
Grospolina Posted January 20, 2018 Share Posted January 20, 2018 Oops, I didn't notice that you said that it was disabled. Your Skyrim.ini is messed up. It's blank except for stuff added by MO. You can fix it like this:Delete (and back up) your Skyrim.ini and SkyrimPrefs.ini in Documents\My Games\Skyrim.Run the Skyrim Launcher outside of MO. This will generate new INI files.Back up your Skyrim.ini and SkyrimPrefs.ini in Mod Organizer\profiles\<profilename> OR make a copy of your profile and use that.Copy the new INI files from Documents\My Games\Skyrim to your profile.I also recommend using BethINI to optimize and manage your INIs. Link to comment Share on other sites More sharing options...
Kohlibri1997 Posted January 21, 2018 Author Share Posted January 21, 2018 Redoing my inis didn't help. Instead I encountered a new problem. When I delete my inis from the document folder Skyrim crashes when I start it normally with Steam while creating the new inis. Trying to find a solution, I reinstalled Skyrim, DirectX, VCRedist and tried compability modes, but nothing worked. With any compability mode setting on, the Skyrim Launcher crashes instantly. Link to comment Share on other sites More sharing options...
Grospolina Posted January 22, 2018 Share Posted January 22, 2018 If you're using ENB/ENBoost, then disable it before running the Skyrim Launcher. You can do this by renaming d3d9.dll to something like d3d9.OFF.dll. Just rename it back after you're done. Link to comment Share on other sites More sharing options...
Kohlibri1997 Posted January 22, 2018 Author Share Posted January 22, 2018 Disabling ENB helped, but as soon as I try to start Skyrim with MO with SKSE or the launcher, Skyrim won't start and after a few seconds MO unlocks itself. Skyrim starts normally with Steam. Link to comment Share on other sites More sharing options...
Grospolina Posted January 23, 2018 Share Posted January 23, 2018 Did you copy the newly-generated INIs to your MO profile? The game doesn't start for me if I use your old INIs, although it crashes after the Bethesda logo instead. You have close to the maximum number of plugins, but there are a bunch more that you can disable, if you haven't already. Since you're using MO, you can hide them so that they don't show up in your load order.Since you're using aMidianBorn Content Addon, you can disable AMB Glass Variants Lore.esp, Differently Ebony.esp and aMidianborn_Skyforge_Weapons.esp.Since you're using Natural Lighting Vivid Atmospherics TS.esp, you can disable Natural Lighting Vivid Atmospherics.esp.If you get "Bijin AIO for USLEEP users" from the Bijin Warmaidens page, you can disable the three separate Bijin ESPs.Use either Dark Fantasy Weather Systems or Heavenly Weather Systems.With MO, you can easily make a new profile and disable all mods to see if the base game works. Then you can start to enable more and more mods to see if they're causing the problem. Link to comment Share on other sites More sharing options...
Recommended Posts