soulstealer

if the developer of mod organizer is a troll i can honestly spare his advice. if he would focus more on proper software development and grow some manners instead, thatd be great. it turned out the enb (272) had a problem of some kind, 262 seems to work again, though. thats what had caused the skyrim launcher to freeze, and maybe was related to building bad ini files or whatever. what truly caused mod organizer to not read the proper ini files anymore i dont know, i just deleted everything, that is reinstalled skyrim, every tool and mod and set it up anew with 1.2.18 and again it seems to work. i suppose it could have been a damaged steam installation or an issue with windows user rights control. looks solved for me at least. no, actually it works fine just switching oses and running one installation of everything. i did that for quite a while. then suddenly today something changes out of blue and i didnt cause it. maybe we will never know. but basically, this setup works very well. i blame some random bug somewhere.

i didnt reinstall my os. i have win 7 and win 8 installed on seperate hard drives. after i played on win 8 and booted back into win 7 and wanted to continue the problems occured i assume. then, i dont watch these series and you should stop trolling me, because i started messing around after the problem occured out of the blue, not before. if you have nothing else to contribute, move on.

so, i ran into a strange problem. first thing i noticed was, when starting tes5edit from my desktop it told me it was unable to find my skyrim installation - all out of a sudden. it also told me to start the launcher again to re-enter the registry values. i did so. strangely, when i started the launcher it continued to detect the graphic settings, but while doing so i would only see a pixelated 800x600 window, black background, steam overlay and the enb stuff in the top left, no buttons or anything. basically the skyrim.exe, the launcher and the autodetect are freezing. i dont remember to be it this way. so i thought ok, maybe its due to the enb (im using enboost). so when i started the launcher without the enb it would work properly, but i remember it had even worked with the enb before, too, and now suddenly stopped. on one occasion the launcher would create inis but then prompt again to create them on a second launch. so, next thing i was playing around in mo and noticed that it is not reading from its internal ini files in the profile folder. so i messed around and deleted the mygames\skyrim\ folder and the profile folder, setting things to write protection, etc, but all that i tried did not help to get the mo profile ini files to work. it seemed like mo would use ini files from somewhere else, but i could not track it down. the configurator plugin would also give me errors and not launch until i removed all ini files from the mo profile folder and the mygames\skyrim\ folder as well. but then even as i had it all deleted and let it be created by default, mo would still neither use its internal ini files nor the inis from mygames\skyrim\ and i was unable to determine why. somehow i believe that maybe something got messed up, since i switch playing the game and using mo between win 7 and win 8. so my idea was, maybe something got messed up with either the installation or user control / rights. all these problems just came out of the blue and i have no idea what has caused it, except switching between win 7 and win 8. before that i could tell mo is using its internal inis from the profile, because when i changed the resolution to an invalid value it would prompt me, but now, nothing.