Jump to content

MO 1.2.18 and SKSE 1.7.2


afz53fu

Recommended Posts

Posted

Ok, so a couple of days ago I borked my skyrim install while trying to install realvision ENB (following Numerical instructions on Nexus page).  After trying to launch SKSE through MO and having it freeze I chose to uninstall it.  Uninstalled realvision using the nexus uninstall instructions.  Since then I deleted the data folder and verified game cache through Steam.  I started a new game through the Steam Launcher and saved after character creation, then tried to load up vanilla and official DLCs with SKSE through MO, SKSE loader stopped responding.  Deleted local game content through Steam and reinstalled through Steam.  Figured I might as well update to MO 1.2.18 from 1.2.17 due to the fresh install.  Launched Steam loader and saved at the end of Helgen.  Now with nothing other than the Official DLCs and SKSE installed I can launch Skyrim using the steam launcher, game and SKSE launcher from the Skyrim Folder and the Steam launcher and game from MO, but when I run the SKSE launcher from MO the game immediatelly becomes unresponsive (little black window labeled skyrim in top left corner of screen) once the SKSE loader finishes loading.  TES5edit reports no errors.  Does anyone have any ideas what I screwed up and possibly how to fix it?

Posted

Did you run MO with Admin rights?

if you use an AV: Did you whitelist MO and SKSE in its settings?

 

This problem sounds rather strange, so i'm only guessing here.

Posted

Did you install SKSE with the installer.exe, or did you choose the 7z archive and installed the scripts in MO?

You need to go a special way if you want to install SKSE within MO, here is an instruction for you.

Posted

I manually installed SKSE with the archive.  The only thing MO does with SKSE is the launcher.  Changing admin rights had no effect.  My AV has never interfered with Skyrim before, I have not changed any settings in it.  The problem persists when AV is turned off.

Posted

I manually installed SKSE with the archive.  The only thing MO does with SKSE is the launcher.  Changing admin rights had no effect.  My AV has never interfered with Skyrim before, I have not changed any settings in it.  The problem persists when AV is turned off.

 

So you've installed the scripts out of SKSEs /data folder as a mod within MO?

If yes: strange. I have both and it runs smoothly together, with AV turned on and no admin rights o.O

Posted

I have never done anything with SKSE in MO.  I run the SKSE launcher through MO by clicking it in the executables list and clicking run, never had a problem before installing real vision.  Is there a new step to make SKSE work with MO?

Posted

For shits and giggles I went back to my MO 1.2.14 installation, the SKSE launcher still works on it.  I guess I will be reverting back to 1.2.14.

Posted

Make sure all runtimes are up-2-date, as well as windows.
And if you use WinXP, then be aware that support for it is thin.

 

i can't remember which runtimes MO needs, but i guess MS-VC++.

Posted

I wasn't thrilled with the newest version of MO. I noticed that some things weren't working/showing up in game. I checked the metadata file and it had extra lines of code that the older version of MO didn't have and it was stating something along the lines of "no files copied." I removed those lines and the mods worked. No idea why it put that in there. So, instead of worrying that I would have to go through each mod and verify they all were ok, I just dug out an old DVD with my old MO image and continue to use that.

Posted

I currently run Win 7, I need to think about upgrading to Win 8 soon.  Or maybe skip a step and go right to WinX or whatever it will officially be called.  I reverted to MO 1.2.14, cleared out my downloads and started over since SKSE would actually launch and the game would actually continue to respond after the SKSE launcher finished.  I have no idea why 1.2.18 wouldn't work or why 1.2.17 broke but I have to guess that it was a result of the realvision enb mod download off of Nexus, it changed something either on it's own or one of its requirements that did not fix itself on uninstallation.

Posted

Very unlikely that the ENB was the reason, because as long as SKSE has not finished loading, TESV.EXE is not called and by this no (possible) left over of the previously used ENB.

 

As for Win8: it's a bad choice for gamers, especially for "old" games and/or games that still use DX9 (like Skyrim).

it's backwards compatibility is bad, due to the way Win8 now handles the system memory.

No need to blame Microsoft, as this change was overdue and sometimes backwards compatibility has to be broken to a degree. That Win8 is still this compatible is actually a miracle and i salute MS. Apple simply breaks every compatiblity with their bigger OS updates as they don't care, so developers have to update frequently. MS cares, so they can't be pure evil.

 

As for Win10: Just wait for it. it comes with DX12, which gives a significant performance boost, even tho it's very unlikely to have this big of an advantage for DX9 games ... if they still work on Win10 as it uses the same/an updated memory manager.

 

As for MO: MO uses quite a lot Windows APis, so those have to be up2date. Old runtimes or an out-of-date Windows installation can be a problem.

Another problem could be burried in the SxS config. So i'm pretty sure that when you reinstall Windows (fastest fix for SxS based errors, as all available suggestions and software to fix such errors are just patch work) MO will work flawless.

Posted

The SKSE loader had finished, the Skyrim window had appeared in the top left corner of the screen and TESV.exe was in the task manager under the  processes tab but  "Skyrim" was not listed under the applications tab.  TESV.exe was using 0% CPU and I forget how much memory.  I check for and install Windows updates when it is convenient for me, usually weekly sometimes every other week.  I do appreciate all the help CGi.

Posted

So i narrow down the source of your problem to:

  • ENB left-over (if a file called d3d9.dll is in the games main folder, remove it)
  • software DEP active (unlikely, but who knows who or what may have enabled it)
  • damaged SxS config (would actually have a bigger impact, but can be the source of many [even unnoticable] errors)

Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...