Switching from MO 1.3.11 to MO 2.1.3 because of the Nexus login changes I find that the script extender workaround doesn't work for me with Oblivion. When trying to launch the game, the Oblivion.exe process is started and maxes out one CPU core, but it only uses a few MB RAM, which never increases and the game never actually starts. I noticed that MO 2 doesn't place the hook.dll in the obse/plugins folder, and it also doesn't exist in the MO 2 installation folder. Providing the hook.dll from the old MO doesn't change anything, though.
It's not a big deal since I'm not playing Oblivion at the moment and also using MO with Oblivion is a real pain for numerous reasons, so I think I will be using Wrye Bash or maybe Vortex the next time I want to mod a new game. My old installation still works with MO 1.3.11, the only problem is downloading and updating mods (again, not a big deal since I don't play it at the moment), but maybe I can somehow use MO2 for that and still run it through MO 1.3.11. Should be possible with symlinks and such.
Anyway, I just thought I'd point that out, even though MO is not the best choice for modding Oblivion to begin with, in my opinion and experience.
Edited by Pherim, 10 May 2018 - 06:36 AM.