Freyrgjurd

Hi, It's not a bug, but I think these situations have other motives besides HDD or SSD: In the first case (typically slower drives such as HDDs), the Dragonborn.esm is now no longer in the data directory. This happens if you backup copying the .esm and not cutting it. It will backup the .esm to the xEditBackup in the Overwrite directory of MO and put the modded .esm in the Overwrite root directory. In the second case (typically faster drives such as SSDs), a cleaned Dragonborn.esm is now in the data directory (compare the filesize to your backup of Dragonborn.esm to verify that it has been cleaned--it should be smaller).This happens if you backup cutting the .esm and not copying it. Since there isn't anything to overwrite, the modded .esm will be put inside the Data directory and the backup in the xEditBackup in the Overwrite directory of MO. Hope this helps.

I hate to bring up the VSync issue again, but if you "remove" the settings from both .ini it doesn't quite work. I had to enforce it in skyrim.ini for the game to work again. Used the recomended settings, started a new game and my character was STUCK in the dead body by the chopping block in the intro sequence. If you can test it... Maybe ENB looks for it in the .ini :/

With those results, I can only assume that iPresentInterval doesn't control the internal VSync switch of the game. Without any means of external VSync it is still enabled regardless of it's value. Is there any source from the devs that this parameters actualy controls VSync ? Maybe it just controls timing events, which will make more sense when taking the name of the parameter. I switch it on, like Boris said and no more glitches with npcs and events. Or it's a placebo effect.

I guess you guys can come with a middle term ? Like: NVIDIA Recommended: iPresentInterval=1, ENB VSync ON and App Controlled. In case of frame stutter, tearing or another problem related to VSync: NVIDIA Alternative: iPresentInterval=0, ENB Vsync OFF and Always On. I used the second for AGES (but with iPresentInterval=1) and never had a problem. The fact is not who is controling VSync (ENB, NVIDIA Driver), but the disadvantages of using the ini setting on 0, which is know all around. (e.g. Messing up Havok with items and bodies flying around when touched, bugging npcs navpaths, etc.) Z might have had problems because of poor optimization of the .dll from Boris, or not. But I'm with Tech on this one.

Just an addendum: It didn't work for me since I was using Chrome x64. Chrome won't interact with MO because of that. If not you case, then you need to edit the "Local State" file (it has no suffix. Open it with Wordpad or Notepad++) Follow this answer: https://forum.step-project.com/topic/4736-google-chrome-cant-download-from-skyrim-nexus-using-mo/

I guess it is now obsolete because of Sheson's memory patch. I tried to enable it, but didn't notice a single diference. Maybe with some exact testing might see something, but it is no longer a variable that affects the game in a noticeable way.

This guide is shaping to a better form every iteration. Use the forums anytime you have any doubts. If not me, a lot of people will try and help you. Just don't forget to play the game. With STEP:Core or STEP:Extended is a whole new experience \/o

Got extended installed and never noticed this. The floating npcs got solved after setting iPresentInterval=1. You got to remember that a lot of mods load at the start, maybe a loading delay of scripts ?

It will be only available if you have files in the Overwrite folder. After you create the mod, it will clean that folder, thus no need /no way to create a mod from there ^^

I recently got my I7 3770k fried by a lighting storm, now I have an I5-4690k version and I have the same performance in Skyrim and other games as before. What you need to understand is that all games get their juice mainly from the GPU. Your CPU is going to murder you if it BOTTLENECKS your GPU. I have a 670 and while I was getting the money to buy the new i5 and a new mobo, I used it on an old Core 2 Duo. It was horrible. I would recomend that you get and Devil's Canyon I5 (or I7 if you do video editing and stuff like that) for the overclock potential and use the money on a die hard PSU (1000w +), so you can buy another 980 for a SLI rig later on. For the motherboard, the Asus Rampage series is the most trustworthy board I ever had. The building quality of the PCB and the raw material invested in the components will allow you a higher overclock, lower temps and higher stability. I would not recomend the Hashwell-E platform, since it is mainly for editing (Photoshop and stuff). Up to 64Gb of ram, quad-channel and all that. No game will make wonders. It's up to you. If you have the money, go for overkill. I7 5xxxK, Hashwell-E, lots of mem and a good GPU rig. It'll be future proof for 3~5 years IMO. Just my 2 small cents ^^

The game's profile is taken care by the NVIDIA Driver itself. When you open the profile with NVIDIA Inspector, you are just browsing and editing it. Inspector will always load at BASE Profile, so if you want to confirm the changes, close the program, re-open it and browse to TES5 profile again. You changes should be there. It's like this: NVidia Graphics Driver is a library of profiles that NVIDIA itself creates and modify. Inspector gives us the tools to modify them :) The profile is loaded by the graphics driver everytime you load TESV.exe (through skse.exe too).

I think is a little overkill, since you'll not have, at anytime (IMO), that amount of cells and resources loaded simultaneously. Mainly, I go to a main city, interact a bit and walk a lot. FTravel to another main city and do the same. Windhelm -> Solitude -> Whiterun -> Markarth. It will stall or crash soon enough if the game is unstable, at least for me.

[ https://imgur.com/oTrBSJ0 ] In the same place you see the files in overwrite, just right click it and select Create Mod. "In Suma" it will do what you did. But through MO itself :) EDIT: To clarify a bit more: 1- This way is to CLEAN the overwrite of the backups and stuff. 2- You still have to go to Skyrim\Data to copy and create a new mod called "Cleaned Update.esm" and copy the cleaned file there. 3- You don't need to zip it. Just create a folder inside MO mods folder with the name you like, it will appear at the list if you refresh it. 4- You still have to restore the backup to Skyrim\Data to keep a clean install folder. :)

Let me see: 1. iPresent Interval=0, enblocal.ini Vsync False + VSync Always Off (on NVIDIA Control Panel or NVIDIA Inpector [samething, since Inspector just changes profiles instead of global values]) FPS: Up to 180. 2. iPresent Interval=0, enblocal.ini Vsync True + VSync Always Off [CP~] FPS: Up to 180. 3. iPresent Interval=1, enblocal.ini Vsync True + VSync Always Off [CP~] FPS: Up to 180. 4. iPresent Interval=0, enblocal.ini Vsync True + VSync App. Controlled [CP~] FPS: Up to 61. 5. iPresent Interval=1, enblocal.ini Vsync True + VSync App. Controlled [CP~] FPS: Up to 61. 6. iPresent Interval=1, enblocal.ini Vsync False + VSync App. Controlled [CP~] FPS: Up to 63. @Conclusion At NVIDIA Inspector / NVIDIA Control Panel if VSync is Forced Off, it will disbled it even if other settings enable it. I suggest you stick to APP. Controlled, since the panel won't activate it, but will allow for ENB or the game itself to enable it. Furthermore, iPresent Interval=0 was known to mess up physics in the game. I experienced it with items floating around like crazy after lockpicking a door or just by walking over it. IMO: iPresentInterval=1, enblocal.ini VSync True and App. Controlled.

Set Wait for Vertical Refresh to "Always off" (Recall that vsync should be running via ENBoost's enblocal.ini!) Just an observation: I know this is for AMD only, but if you force off VSync on NVIDIA Inspector or Control Panel, enb's vsync won't work. Discovered this after setting AMD setting on NVIDIA Inspector. (DUH me ! haha)

Well, maybe the comp.patch isn't needed anymore ? I installed STEP extended (EBT and Extended Patch) and got no errors or strange behavior. I played for a good 4~6h withou a single CTD.

Make sure you have the various versions of VC installed. There are: 2005 2008 2010 2012 2013 If I record correctly, the Skyrim is 2010. I install all of them in order of oldest to latest just to cover all ground. Another note, if you use a x64 system (as you are), install both x86 and x64 versions. I hope it helps ya.

The DLCs and the Addon are options in the FOMOD installation. You can select blood styles and stuff, at the end he asks which DLCs you're using and a checkbox for Blurry Screen Blood. A lot more practical, IMO.

[skyrrimpref.ini] [Display] bFloatPointRenderTarget=1 ?

You can hash-check mods that have the HASH available. It smells memory fault to me. Since, it gets stored in the memory while extracting before wrinting to the HD.

Ahh, that sliped my mind. Saw something about it yesterday. You can just run skse_loader.exe with an argument. Something like this: skse_loader.exe -forcesteaminstall Or something like that.

https://www.nexusmods.com/skyrim/mods/30947/? *Dead Body Collision Fix* Not pointed in the guide what version. NMM Download (with MO) gets the Fireball Desintegration version. I think it should be pointed out for the Original version.

So it's the ini file format. It can find it, but can't read it. Try mine: SKSE.ini

Isn't it the same of the Official Forums ?