TechAngel85

I would make sure the drivers are up-to-date: https://www-ssl.intel.com/content/www/us/en/support/detect.html and https://www-ssl.intel.com/content/www/us/en/support/graphics-drivers/000005629.html Past that, I'm not too sure how much help I can be. I'm still running Windows 7 and I've never tried to run the game on Intel Graphics.

The d3d11 file is for DirectX 11 games, hence the "11". Skyrim runs DirectX 9. SSE is DirectX 11, though. A quick google search came up with igdusc32.dll being part of the Intel HD Graphics Drivers for Windows. Are you using Intel HD Graphics on your laptop or from the CPU, or do you have a dedicated graphics card?

From a computer technician viewpoint, all the big name antiviruses are the worse to use. When computers come to me for malware issues they always have Norton, McAfee, Kaspersky, etc. running on them. I personally only use MS Security Essentials combined with browser-side protection. Make sure the Skryim folder is in your exclusion list.

You have to have the d3d9.dll from ENBSeries to run it. So if you deleted it, you'll have to put it back and then make sure you add it and enbhost.exe to your antivirus exclusion list. You can probably just add the Skyrim folder to that list so that it'll ignore everything in the folder.

Did you add d3dx9_42.dll to the proxy list in enblocal.ini? I'm not sure this is required, but could be the issue. Also some overlays will interfere such as Steam's overlay.

Try running the injector outside of MO (not from the MO executable list). Then launch the game from MO using SKSE.

This likely could have been fixed with Crash Fixes or a proper ENBoost setup instead of Safety Load. Safety Load was tested to be in STEP but was rejected due to suspected CTDs caused by the mod, of which the author partially confirm was an outstanding issue but it got never fixed.

You need to add --single-process to LOOT inside MO. Modify the LOOT executable from the drop-down menu in MO and add that line in the arguments box.

Upon further testing, the following changes have been made: Transparency AA has been removed from the guide. Testing showed no difference whether this was set to Off or to 8x (max).AO has been changed to High Quality due to there being no performance loss on my system. Most modern systems shouldn't have any issue with this. My system stats are in my signature. The only mod in this guide is MEUITM. I refused to add anything else due to TexMod notoriously making the game unstable. I might look into MassEffectModder, though. Thanks for the heads up!

This has been my thoughts, exactly. The profile I use to play only has this installed due to an archery mod I used that requires it or Immersive First Person View. Else, it wouldn't be in my personal profile at all.

That's where hard testing has to step in, which I admit is a pain. Popping in and out of the game to test stuff is a real hassle, but that's how I found out about changing the AA settings in Inspector causes issues for ME1. Turns out a quick google search will turn up a ton of people posting this very issue, but I only found a single post (that got ignored) on an old forum thread that suggested it had something to do with AA. After testing and vetting it out myself, the guy was right. Overriding the games AA via Inspector causes the issue. SMAA works beautifully for these situations, though, since the game's native AA sucks. Sad that more people aren't competent enough to test things for themselves. I guess that I why we put together solid and well tested guides. :: Specifically, it's this blue "aura" issue: Imagine seeing that while tying to shoot the Geth... On a side note, I'm still not even sure if the transparency AA via Inspector is doing anything or not. I'm planning on tackling that one next.

Couple more updates: Changed settings for antialiasing in the video drivers because forcing AA caused lighting glitches that inferred with gameplayAdded SMAA to the guide as the preferred AA solution

With those big mods, the load order is not the only thing to worry about. Conflicts between them and other mods will be something that needs to be resolved using xEdit to create your own custom patch to resolve the various conflicts that will be present.

A few updates: Added in a video card section. It's not tested yet. I simply provided minimum settings based on my experience from other games.Changed the PoolSize to 1024 based on recommendations I've read.Changed Anisotropic Filtering in INI to 0 since we'll be forcing it through the video card now.Changed MinShadowResolution back to the default of 32 since I could not find my reference of why I originally changed it.Changed the DepthBias to .006 to match MEUITM's recommendation. As I mentioned above, the difference between .008 and .006 is so small that no will will notice any difference in-game.

Community members keep in mind that they can use this on top of STEP, if they desire. This mod is not integrated into the STEP Patches or anything like that so it being dropped will have no affect on its independent use. I'm only questioning if this mod is right for inclusion in "STEP" based upon our Mandate.

Going through this thread, there are a few things I'll add to the guide (like forcing AO). I will start playing the game again soon in some of my free time and will update it where I see it needs it. I'll add the graphic card tweaks tomorrow.

Just letting everyone know that I went back through the guide during the last couple days polishing and updating it where appropriate. Now if I can only manage to completely finish playing the game...

Personally, I would like to see this mod dropped and have said as much on every occasion I'm afforded. It has too many issues with other mods and miscellaneous issues as with the fNearDistance and Z-fighting. I see no reason this mod should even be touching those values, the animated "wobble" and "creature mode" movement is not realistic except for perhaps on horseback, and the player shadow is terrible and inconsistent with the rest of the game. The only thing I kind of like from the mod is the sitting animation, but that is not enough reason to save it from being dropped, imo. All-in-all, I simply don't think it's STEP material. I would like to call a vote on this from the staff and community. Drop or keep. Post your reasons, please.

'Behind" infers 'after' in this context. It can not mean anything else given the context as you have already deducted the meaning was inferring 'before' and 'after'. :: Don't you just love the English language...

It's a normal look for a spell cast on yourself, that much I can say.

You can try to disable or reset Burn Freeze Shocks Effects.

Looks like you have an effect that is stuck.

SRO used to be in the Conflicting Graphics section of the Guide. It would likely be placed there again. The mountain texture is the current Guide is provided by Improved Vanilla Mountains found in the Landscape section. SRO used to provide the majority of the Guides enhanced vanilla textures. Once it was removed we replaced the main landscape textures with Skyrim HD's landscapes as they were the closest to vanilla we could find. Many, many textures were never replaced that SRO covered. For the purposes of the Guide we also had a very customized, reduced SRO where textures were a mix of 4k, 2K, and 1K (mostly small clutter objects). The normals were mainly reduced to 2K and 1K. To be honest, I can rarely tell the difference between 4K and 2K textures when actually gaming and not just standing around looking at textures up close. This is how STEP goes about testing most of our textures. We're not producing the Guide for screen-archery, we're producing it for gameplay and 4K textures are typically overkill for such purposes.

I changed the wording up a bit. Thanks for the recommendation, all!

Okay, I've upload the hotfix to our Nexus page. Just merge it into the STEP Compilation when prompted during installation.