Providing the hook.dll from the old MO doesn't change anything, though. 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. 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. 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.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |