Melamkish

Credit for the answer goes to both hishutup and GrantSP Summary to clarify the actual fix: From GrantSp: Ensure OBSE is installed (obviously) Manually install the CSE by copying all the files inside the archive to the Oblivion directory Open the 'Launch CSE.bat' and copy the arguments: -editor -notimeout In MO create a new, or modify the existing Construction Kit exe link, and in the 'Binary' field point it to your 'obse_loader.exe' In the 'Arguments' field, paste the arguments you previously copied Ensure the exe link is either modified or created anew and close the 'Modify executables' dialogFrom hishutup: Open the Configuration and settings window using the tool icon Select the Workaround tab. Click on the load mechanism bar and select Script Extender Close the Configuration and settings window My suggestion: After running the CSE through MO in the above manor, don't forget to remove administrative rights on the obse loader executable or you will get UAC warnings about elevated privledges. (a minor issue to change permissions back and forth). If the game doesn't launch you may need to change the load mechanism back to Mod Organizer (I am using the non-Steam, retail version of the game).

Now it works!! Big thanks to both of you. Hishutpu, at first I was't sure what you meant by obse workaround, until I was trying out GrantSP's suggestion. Then it suddenly dawned on me. Earlier, someone on another forum was trying to get Oblivion/Steam to launch from MO and mentioned he had tried with the script extender workaround. When I just looked at that tab, I didn't see one. But, I remember that with Skyrim, the load mechanism bar said "Steam", and with Oblivion it said "Mod Organizer". Clicked on the load mechanism bar and then saw the "Script Extender". Selected that, added GrantSP's suggestion to the argument section of the tool and Just goes to show that even after using something for so long, one can overlook the simplest things

So far, MO/Oblivion/OBSE seem to be working for me. It is only the current CSE I'm having issues with. If there is some sort of potential fix or work around, I'm willing to give it a try. I would prefer NOT to go back to a different way of managing mods, as I like the philosophy of the way MO works. I may try to run the older CSE 5.1 on the other platform and see what happens. The CSE log is not as fullly detailed but does do some of it's own hooks. Didn't look real close last night. I did move all of the plugins out of the OBSE plugin folder except, OBSE and the CSE, still no luck.

Well, since I have noticed in various forums that more people are using MO with Oblivion, hoped someone may have gotten the latest CSE and MO working together, or at least had some insight into this problem . After researching the exception code, Stack Heap Error/Overflow, on the MSDN, and going thru every single log in the Administrative Tools Event Viewer, I can't find anything that seems to indicate a system setting problem, so after I check a few more things, I will head over and post a bug report.

I am trying to determine whether this is a system issue, a conflict between the two, or, a bug that should be reported. Trying to get CSExtender v6.2 to work with MO. Using MO version 1.2.14 with Windows 7 x64. I have done several tests of launching the CSE through MO, both with and without setting "Run as admin" on the two recommended files in the CSE documentation. The docs require the obse loader executable as well as the CS editor to be "Run as admin". When I set the compatibility to do so, and launch the CS Extender thru MO this is what happens: The CS opens, with all the Extended features, however, MO fails to hook the CSE with the MO virtual mod directory. In other words, all I can see is the default game directory. This happens on a different machine, as well. Besides this issue, MO is performing very well. Reviewing the MO log reveals that everything above the following entries are loading properly. Same error each time. At the end of the logs is this error: DEBUG (18:44:34.0506): findfirstfileex C:\Games\Bethesda Softworks\Oblivion\*.*: . (10) DEBUG (18:44:34.0569): process failed to start (740) INFO (18:44:34.0569): Windows Exception (c00000fd). Origin: "C:\Windows\syswow64\ole32.dll" (7573a1f0). Last hooked call: struct HINSTANCE__ *__stdcall LoadLibraryExW_rep(const unsigned short *,void *,unsigned long) I have been using MO since before version 1 with Skyrim, so fairly familiar with it. All other tools launch properly. Thanks for any insight into this.