MO launches SKSE but game doesn't launch

[blissfullyfemale]

Hello,

 

When I try to launch SKSE through MO it shows me the little black screen in the top left corner for a second and then it vanishes. Normally Skyrim would launch after that, but .. it doesn't. My task manager shows Skyrim running as a 'Windows Process' but not as an 'App' at the top. There is no screen for me to alt+tab into. It doesn't matter if I have no mods enabled, and I am running SKSE and MO as an administrator. What am I doing wrong?

 

The confusing part with all of this is that it did work, twice. I was going through the STEP core setup and tested it at the first two benchmark screens. And now it doesn't do anything even if I untick in the right pane, or uninstall all the mods in the left pane. 

 

Any ideas on what I am doing wrong?

 

And in case it matters, I am using (or trying to) Vividian ENB.

 

Thanks for the help!

 

~b

[EssArrBee]

The latest Nvidia driver came with a broken Nvidia Experience app. For some reason it can't start SKSE and a D3D plugin like ENB or SweetFX. You can try deleting the Nvidia app or installing an older version.

[blissfullyfemale]

Sorry .. I didn't specify but I'm running on an AMD Radeon R9 200. I will look into the AMD control center app though to see if that might be the issue.

[GSDFan]

Try running without the ENB installed. If it runs then the ENB is the problem, it has happened to me.

[hishutup]

I had a similar effect and it was a program that was up.

Kill the java and any other applications in the taskmanager that you might have run in MO, those can stick around

 

 

 MO as an administrator. What am I doing wrong?

Its been said to NEVER run MO as admin period.

I know right, its a thing, I always thought that admin was to fix applications that don't have permissions.

I guess its because of the whole virtual filesystem thing

 

As for enb do what GSDFan said and if it works try putting it back and disabling these line in EnbLocal.ini:

ExpandSystemMemoryX64=falseReduceSystemMemoryUsage=falseDisableDriverMemoryManager=falseDisablePreloadToVRAM=falseEnableUnsafeMemoryHacks=falseEnableCompression=falseAutodetectVideoMemorySize=false

Sometimes with different SSME values there can be an issue with enbs ExpandSystemMemoryX64 being enabled

 

 

I don't believe the type of ENB would matter unless the author messes up pretty bad but even then I think ENB puts default values

Edited October 2, 2014 by hishutup