NewThalos

What's the most current version? I have v1.16 installed

What's the most current version? I'm rocking 1.16 Below is the changelog:

PerMa being as new as it is, and in active development, your best bet would be to post this on the PerMa page, if not done already. Since PerMa is an active WIP, it is very unlikely that you will get the same quality results here compared to asking directly at the source.

.. you do not need to reinstall windows. You screwed up your game, not your hardware or OS. Relax. Read some newbie guides, make sure you're using a proper mod management system such as Mod Organizer, take a deep breath, and try again. Also, in Verdant, if you dont set the appropriate ini files tweaks to compensate for the new grass, you will kill your FPS. That said, Verdant is not for people with hamster wheel and potato powered computers. It's resource intensive. It will bring even giant computers to its knees if you don't know what you're doing, and/or are using too many texture mods, don't thoroughly read directions for correct ini settings as per the mods you install. Good luck and happy modding

Bah, sounds like all sorts of shananigans going on here bud. You need a clean refresh of your game folder it sounds like to make sure you get rid of the trash, and keep only what is necessary. Might not be the answer you want, but its the answer that you need. Delete all of the loot crap from your skyrim root folder, let steam repopulate then, reinstall skse v1.7.2 (installer version, not the zip file loose version) and then place the correct enbhost and d3d9 into your skyrim root folder. Also make sure you're using the enb binary files that your ENB asks for. Then go back and cross reference whatever that ENB you installed tells you to adjust, and try again. Please note that by letting steam repopulate your game files, it will make you re-clean your dirty vanilla assets. If you want to go pro, use MO and setup profiles for the different ENB's you're using. It will save you some gray hairs. Good luck and happy modding.

The only thing that can break your computer, would be after market tweaks to your hardware, which is something you do yourself, not a mod. A mod is only an asset that the game utilizes, and if you overburden Skyrim with too many, or incorrectly loaded mods, the absolute worst thing that can happen is your game crashes, but nothing that I can possibly think of would effect your system files, drivers, or anything else of importance on your hard-drive and/or hardware just from installing/uninstalling/using mods.

It sounds like you installed this manually, and replaced existing vanilla assets, and when you removed the mod files, it took with it the vanilla assets along with it. You might need to start the game over as well, and if you're missing assets, just have Steam, re-verify the files. That mod is really a great mod, totally worth doing, you just need to make sure its high up in the load order via your mod manager, just after the unofficial patches.

omg thank you so much for the spoilers! makes it sooo easy to review, read, and comment on now! haha Could you be more specific? At which step do you get stuck at? At which step does your game go from 100% playable to less than 100% playable? Also, I noticed you're using a block log, which insinuates you're using SSME, is this correct? That mod has been antiquated for a long time now, strongly recommended that if you use that, to completely remove it, and use just SKSE v1.7.2 instead. Your papyrus log is pretty much the golden ticket for knowing what is spamming your game and likely crashing, but I can't read that txt file very easily. Some low hanging fruit that I see.. You have a lot of scripts running, that are firing and aborting quite a bit, specifically your schlong mods and whatever combat mod that is referencing a staggerControl functions. Have you run this papyrus through the Script Scalpel yet by chance? Or have you used SaveTool to remove old scripts from your save that are no longer installed?

Hmmm, would be easier with a screenshot, but it could be one of a couple things.. 1) Did you remember to set bFloatPointRenderTarget=1 in your Skyrimprefs.ini? 2) Skyrim is notoriously broken when it comes to Crossfire and SLI, and with a little research, you can find some solutions to using SLI with Skyrim. Also, any particular reason you chose injector? You sort of really want to use SKSE along with your ENB. Let us know what you find out.

With all due respect myztikrice, I disagree. SkyUI is notoriously problematic if you do not install manually and only up until semi recently, the SkuUI mod page explicitly instructed you to install manually. Currently, you can also install it through NMM (but not MO) but that method is not recommended for reasons that I'm going to get into shortly. Mod Managers handle assets on a secondary basis compared to skyrim-managed assets. Skyrim managed assets always get first priority, much like how loose gets priority over BSA. You don't want SkyUI assets to be overwritten, ever, and therefore you want them to be handled directly. Same for OneTweak and uStable, both mods that you don't want anything overwriting, ever, and are dependent on assets that you very much want to allow direct manement, rather than a mod manager, skipping all middle-men. As for SKSE, I fundamentally disagree. You 100% want to use the v1.7.2 installer, not the loose files. It would be terrible advice to do otherwise. There are only a very small number of items that you want to install manually, and they are ENB binaries, SkyUI, ustable, SKSE, onetweak, FNIS, and a small handful of skeleton/animation type mods that again.. you dont want a mod manager handling because you don't want any middle-men ever having priority over them. Again, with all due respect.

Well, you're using SkyRe, thats a potential cause assuming your dynamic patch did not create correctly, in additon to conflicts with combat overhauls. Ultimately the only thing that would touch stamina is an overhaul, you use several according to your list. Have you been uninstalling/installing a lot mid playthrough? Could be a byproduct of a corrupt save with bloated scripts that are no longer attached to anything. Cleaning your save would be the first thing I'd do, followed by examining SkyRe and anything related to it that is lacking a patch that should have been installed. Really, my advise is to ditch SkyRe and use Perkus Maximus instead. Its far superior.

It's cool, and as for the save, we can clean that up, not a problem. Plenty of ways to do that, your game isnt corrupt, its just not compatible with itself, and that will be fixed in due time. The main focus is just getting you to a point where the game runs, then we can worry about the bells and whistles later. As for the passive aggressiveness, you need to consider the point of view of people like me who just want to help you learn how to fix your game, but we get frustrated because people all too often don't want to hear the hard solution, they just want a fix, or a golden bullet ini tweak. We'll get it working for ya bud, and when you're done, you're going to be a pro. edit: fixed typo

Hmmmm, I'm afraid none of us are really equip to help you troubleshoot Steam Workshop installs. There is a reason why many of us don't use the Workshop, it's sort of a different animal that is harder to control. Either way, you need to uninstall everything from the Workshop, completely delete your skyrim game folder, have Steam re-populate the core game files entirely, etc etc etc. Pretty much what my original posted reply to you said from the beginning that you sort of ignored. If you're serious about solving your problem, then do what I just prescribed above, and following the directions on the following link below: Unofficial RealVision Troubleshooting Guide No longer supporting this thread, can't keep repeating myself over and over again about how to solve your problem. Cheers and good luck, friend.

Yeah you need a fresh install of the game, and need to create reliable restore points in order to troubleshoot the problem. Nobody here can help you until you, yourself, learn how to properly isolate the problem. You say you're following the directions, and yet your game folder still has manually installed trash in it that shouldn't be there. Back to the drawing board dude. Sorry. Start fresh, create a working game, then proceed from there in small measured steps until you're able to find out what breaks your game.

You are mistaken, much like so many others out there living in the information age where intellectual property rights are flagrantly thrown out the window due to the rampant spread of patently false information. Just because you own something, does NOT give you the right to RE-distribute copyrighted material. Please note how I wrote "RE-distribute" because that's what one is doing when they seed/leech a torrent file that they own. You are not a licensed reseller or distributor of Bethesda products. You are not granted the rights to re-distribute Skyrim, via torrent or any other venue out there. Support ends now. Please close this thread.

So a quick question that qwertyzeldar sort of touched base on-- did you run LOOT uses the latest version from the official LOOT archive? Or did you use the build in LOOT for MO? The built in one works, but what you really want for cutting edge sorting is to use the latest. Install the latest version of LOOT from the Official Loot Dropbox archive. Next, have you tried checking out what your load order looks like in Wrye Bash? If anything is orange or red, that means they need to be dealt with. Clicking on the mod and reviewing the right window pane in Wrye Bash tells you what the problem is being either missing master (red) or out of order plugins (orange). Often simply adhering to the suggestion of Wrye Bash (on top of what LOOT told you) is suffice, but you could also pull up Tes5Edit and load up everything in your load order (takes a few minutes) and then when its finished, highlight them all in the left pane of Tes5Edit, right click, and then select "sort masters" then when thats finished, close Tes5Edit, save whatever it tells you it changed, and then go back into Wrye Bash to check if you see any red or orange flags anymore. Tell us what you find out after following the instructions above. Cheers and good luck.

Alright first off, please edit your post to include "spoiler" tags for each individual section, because right now, people don't even bother reading your post all the way through because nobody wants to press the page down button 8 times just to get to the bottom, and/or go up and down to cross reference their reply with some line of text above. Make 1 spoiler for your load order, and 1 spoiler for each ini file you listed. Thanks Now to get to your question, you cant use ENBoost AND the ENB binaries, regardless if you're using an ENB preset or not, I wasn't entirely clear on whether or not you stated you're using both binary files (which already include ENBoost in the form of the enbhost file). Next, I see you got rid of Dual Sheath Redux, does this also mean you made sure to re-run any mods that had installers with patches for DSR? Gotta make sure you don't, they're hidden inside all sort of mods these days and we forget to re-run those installers to uncheck those patches. Next, you mentioned the coloration bugs that show up over time, right? Not just from the moment you boot up the game? This is very commonly seen in the case of GPU overheating which causes visual artifacts, but only after a few minutes/hours of gameplay after the GPU is thoroughly burning up. Do you track your CPU and GPU temperature at all? I suggest you start doing so unless you're confident that your tower is super chilled, and you have radiators keeping your CPU cool during those hot summer seasons. Next, I see you're not using some mods that I'd pretty much call absolutely essential, no argument, must have stability mods. Please MANUALLY install the following, (do not use a mod manager like MO or NMM!) Manually install Stable uGridsToLoad (do not use MO or NMM)Manually install OneTweak (do not use MO or NMM) Also, are you using the latest version of SKSE with the correct memory patch SKSE.ini file? If not, please do so asap. No excuses! Manually Install SKSE v1.7.2 (do not use MO or NMM)Make sure you have THIS file inside your SKSE folder.After you've responded to, and/or addressed the issues I've mentioned in this post, then we can address your ini files, but I didn't bother to read those yet until we take care of some blaring issues first.

@FeelNatesHate Yo man, lose the foul language. Not necessary. BUT-- as an alternative solution for those with the blue aura effect that is not caused by a spell, there is a well known blue outline effect that sometimes is a byproduct of ENB binaries, (not specifically them, but a matter of how they interact with certain other ini settings.. but thats a conversation for another time) try setting iBlurDeferredShadowMask=0 This is known to fix the blue aura problem (assuming your issue is the same) cheers

Addendum, Also, I know that picture you quoted says to always put the bashed patch at the bottom, but please know that they mean always at the bottom of every mod, EXCEPT dynamic patchers, which need to use the bashed patch as a master, and therefore dynamic patchers are always last.

Within MO, any dynamic patchers, bashed patches, newly merged plugins, etc etc-- all get sent to your overwrite folder, which can be found either by navigating your MO folder's file tree, or by simply double clicking on it at the bottom of your left load order window. You'll also notice the MO's warning flag going off on the very top right hand side of your screen warning you that you have files inside your overwrite folder that need to either be dragged into an existing mod, or placed into a new mod folder altogether. 1) Create a new mod folder within the folder that all of you installed MO mods go to, call it "bashed patch", then go back into MO, right click on the left load order menu, click refresh, then that mod should now be populated in your left load order menu (under "unchecked") but make sure you turn off your filters and clear your categories so you see everything. 2) Drag the newly created bashed patch folder to the appropriate place for bashed patches to go (at the end of your load order but before dunamic patchers like ASIS and PaMa, then double click on the overwrite folder and drag your new bashed patch files to their appropriate folder that you created for them. 3) Toggle the mod on now, and click refresh to make sure everything is populated and turned on via the right plugin menu now. DISCLAIMER: If you did not already know about the overwrite folder by now, chances are you have other trash items in there also, make sure you dont drag all of those trash items into your bashed patch folder. Worst case scenario, delete everything in the overwrite folder and re-run the wrye bash to make sure you have a clean bashed patch. Also, and you probably already know this, but always make sure you have enabled all in the right plugin window of MO prior to running the patch (duh, I know, but I had to make sure, since you seem new to MO) happy bash patching!

Bah, I remember this mod now. It's an outdated mod. One should be weary about using mods last updated over 3 years ago, with the only known patch created a year ago. This is what we call a "dead mod". It's unsupported, and has been replaced with more sophisticated versions, such as the "EBD - EveryBody's Different Redone by MongoMonk" but that requires you knowing how to use a dynamic patcher, and I don't think I want to have that conversation with you. But this all said, I can help you get this working. The original instructions are really bad-- again, written years ago before we came up with better ways of doing things, aka Mod Organizer et al.The problem is caused by either you not installing everything correctly, and/or an incorrect load order issue. I'm going to write you new and improved list of instructions as opposed to the original ones which I have provided here within the spoiler below for historical reference: Improved instructions - Install with Mod Organizer: 1) First install the three files from ApachiiSkyHair NPC Overhaul by Spewed, making sure that you are merging the next with the previous. Not replace. ApachiiHairStylesOnNPCs 2_20 (main file)Color Mismatch Fix for Elven races (first merge)Color Mismatch Fix for Humans and Bretons (second merge)This should leave you with a single folder in Mod Organizer with all three files combined. 2) Right click on the mod within MO, and click on "Open in Explorer" 3) Delete the "Skyrim.esm" folder located at: data/textures/actors/character/FaceGenData/FaceTint 4) Install ApachiiSkyHair NPC Overhaul Brown Forehead fix by Skycatcher and make sure when installing with MO, that you have it merge with the above combined mod folder that you just installed from the ApachiiSkyHair NPC Overhaul by Spewed mod page. Again, not replace. 5) Place this newly created patched npc overhaul mod of yours down towards the bottom after everything else, but before any bashed patches or dynamic patchers. Conclusion: In theory, this should work, but you should perhaps run LOOT and see what it says about the placement of these new plugins regardless. Worst case scenario, you might have to manually move them back down towards the bottom of your load order. As long as you make sure this newly combined mod is placed BELOW any mod that alters NPC's what so ever, it should be the dominant file that overwrites anything that comes before it in the priority list. If this does NOT help solve your problem, then my suggestion to you is to throw this mod away and never look back. After all, there are better alternatives out there.

Try using a savegame cleaner like SaveTool. This will allow you to remove any rogue scripts and/or assets from your save file. Always make a backup, as always.

Can you explain what exactly the problem is? Do you have a screenshot of the issue? You've mentioned that you have a problem but we don't yet know -what- that problem is?

Look's like either a profile issue, or a filter issue. Can you click the filter button on the bottom right LEFT, and open up your available filter types, then click anywhere on the bottom which should go back to default view, which is to reveal all mods, activated or otherwise. The answer is likely inside the filter section. Probably. Let us know what you find out. Edit, I mean bottom LEFT

The problems you're reporting are foreign to me, most likely a product related with Workshop in general. I don't use the Workshop for a reason. It sounds like what you're going to have to do as a byproduct of using the Workshop is to completely clean out your game folder by reinstalling it through Steam and starting from scratch. I also recommend avoiding the Workshop, and using programs like Mod Organizer, since using MO removes the need to alter files within the Skyrim game folder itself, because it segregates every mod each in its own individual packaged folder. Since you've admitted that you've done extensive alterations to your game folder via mod installations, etc, one cannot in good conscious try to advise keeping it after having the troubles you've described. Sorry bud, you're best bet is to start fresh with a clean install. :(