TechAngel85

No. All the current STEP Guides are for Skyrim LE.

Is this the dump from Crash Fixes? Try googling a fix for "c0000005". There are several available. If you've replaced TESV.exe with an altered one, that could be the issue. Another option is to get rid of the ENBSeries memory management (turn it off) and use the one from Crash fixes. These are just things you can try.

You have quite a list there and I don't see any conflict resolution patch anywhere. That would be my first step of advice. Even though you have patches installed, that doesn't mean your list of mods is without conflicts. Second, have you tried Crash Fixes? It will fix several crashing issues and provide a dump file, when the game does crash, so you can investigate the cause of the crash.

Ah, my mistake. I remember that now, but for some reason was thinking, "they're already 'default' INIs".

What's the refresh rate of your monitor? What is your vsync set to in the nvidia settings?

Here's the link: https://mega.nz/#!VwdXjYAA!KROi99DyR_NLLREBlMmEy-AZQEAhKs2LQn16fn3xUYg This is the log from a new profile and fresh INIs from the created profile. My setup has all programs for modding installed an a separate SSD (D:). MO2 is using instances so all the MO2 data is install in AppData on my C: drive.

Next update, can you be sure you invest that issue with the archives not being put into the Skyrim.ini for Skyrim? This has happened on every profile I've made within MO2. If you have a check for MO, that might need to be altered due to MO2 changes, which returns the old BSA/Plugin relationship (users can no long allow MO2 to load BSAs without their associated plugins).

If you have MO2 and WB installed on a separate drive, other than your C: drive, then you'll need to change your user temporary files location to the same drive where MO2 and WB are located.

Right now, it's months. We were hoping for a later summer release (July - August), however it may be a fall release (September - October) due to the free time we have had to work on things. We may be opening up the Guide to a few beta testers since, currently, I'm the only staff member testing the completed Extended Guide. So can stay on the lookout for that announcement, which if it happens, will happen very soon.

The point I'm making is this isn't going to make the job of patching for STEP any easier until the all the ground work has been laid, which is exactly what you're saying too. I feel right now is not the time to be focusing on this. I can see how it would be very handy in the future, once the ground work is complete, and STEP will likely find a use for it. But getting to that point will take a lot of time and effort that could be put towards actually getting the v3.0 Guides completed. This is my main focus and concern right now. Smash will likely be incorporated at a later time when time can be spent putting together custom settings for the Guides.

I tried this on just the Core mod setup. As it is, the "one button" solution will not work for STEP. To be specific: It aggressively forwards all keywords from the UP, when some are purposefully not forwarded by authors. This is especially true for Weapon & Armor Fixes Remade around "material" keywords.It seems to be favoring the UP over a lot of records, which have purposefully been changed. I've found this true for keywords, alt materials, and portions of scripts.Just those two things alone would lead me into a few hours of verifying record forwards and fixing/removing what shouldn't have been forwarded. For this to be viable, I will have to play with the Bash Tags to see if I can get it to produce more of what I'm expecting. I would also need to verify the leveled lists are all being taken care of, probably comparing it to a Bashed Patch. I can see this being a valuable tool once and if you get your own custom settings worked out. This might not be the best time to try to work through this process, though, as it will take a considerable amount of testing to do so. In any case, I'm going to need a handmade patch to compare the Smash Patch to. If we can get Smash to mostly reproduce our handmade patch, then this tool could be very valuable when doing large edits to the Guide or when needing to pass the settings between staff and/or users.

Yep. It's a compete rework of the guide, but also includes a complete rework of our web presence, framework that the guides are built on, and new content. Pretty much everything is being built or rebuilt from scratch. I've handled all the guide work by myself. The Extended Guide is basically complete and in the testing phase. The Core Guide can be put together and finished with a few days of work since all the work for it was, more or less, competed within the reworking of the Extended Guide.

The helmet issue is a known issue because by certain mods. You can simply wait until after the cave exit and then go into race menu to design your character. ( open console and type: showracemenu ) I have this fixed on STEP v3 with the patch. The other two issues are going to be on your system alone. The fire is probably the mod ultimate fire effects. The CTD could be a multitude of things.

SMIM can simply be removed. Certain mods may need to have non-SMIM options installed. Vivid Clouds and Fogs will need to be removed from the current STEP Patch using xEdit.

STEP is not for SSE. What you're likely wanting is here: https://forum.step-project.com/topic/13092-lexys-legacy-of-the-dragonborn-special-edition/ Your third question is very subjective.

You only need to edit the weathers that you want to have the blue sky. I wouldn't edit the default from within the game. Edit the INIs to the colors you want for only the weathers that need it.

It would perform better and get you to where you want to be, but if you going spend money on an upgrade I would recommend at least a GTX 1060. It's only about $40 or $50 more, but it performs a lot better than the 1050.

Your ENB will be the most demanding. You can try Vividian ENB with the performance presets, but the honest truth here is that you probably shouldn't be running an ENB with that card. The most intensive mods to downgrade would be the overhauls, like SRO. You can use DDSopt to confine the size of that mod to 2048x2048, at most. Other things I would do is cap exterior textures to 1K and interior textures to 2K, at most. You shouldn't be using any 4K textures. It won't be a detailed, but you'll get better framerates.

Well, let me know if I need to file a bug report as a reminder for you to check on it when you have time.

Your CTD is likely unrelated to the Bashed Patch since you've been able to go longer and longer. I would install Crash Fixes and enable logging to check on it when the game crashes. Though it is possible for your crash to be performance related with only a 750 Ti. Though newer, the 750 Ti is not as powerful as our recommendation of at least a GTX 660. Edit: You should also run BethINI to clean up your INIs to ensure you have no bad edits. That's the reason it's a part of the STEP installation. It's clear you have not done this according to your posted INIs.

I set this to 6000 because that is what Mangaclub recommends for Vividian ENB and Vivid Clouds and Fogs. No performance loss on my GTX 1060.

Is this a reason BethINI isn't adding the... sResourceArchiveList=Skyrim - Misc.bsa, Skyrim - Shaders.bsa, Skyrim - Textures.bsa, Skyrim - Interface.bsa, Skyrim - Animations.bsa, Skyrim - Meshes.bsa, Skyrim - Sounds.bsa sResourceArchiveList2=Skyrim - Voices.bsa, Skyrim - VoicesExtra.bsa...lines to the Skryim.ini file? It's listed in on the wiki source that you created that these lines should be included.

There are other plugins which are causing the Bashed Patch to freeze at main menu then. The only other one I know that does it is SGR Enhanced Trees Activator.esp from Enhanced Vanilla Trees. It took me two hours of running and rerunning the Batched Patch while only enabling one mergable plugin at a time while building the patch, then running the game to see if it loaded properly. You may have to do the same to find the other plugins causing the issue and exclude them from your Bashed Patch.

When making your Bashed Patch, do not merge the DesyncBirdsOfPrey.esp. It causes that freeze at the main menu for some reason.

Try disabling your bashed patch and loading the game.