ReMeDy Posted October 22, 2017 Posted October 22, 2017 My Skyrim CTD's occur frequently when loading into different cells (areas) and even when loading save files, regardless of being indoors or outdoors. Sometimes the loading succeeds, and other times it doesn't. I've played Skyrim on weaker PC's and had less crashes, so I thought it was strange, until I read a quote from that Boris guy who authored ENBoost, saying more cores means more problems.Okay, so I have 12 cores. Should I just give up? Am I wasting my time with all these memory fixes, boosts, injectors, etc.? I don't mind if the game crashes occasionally, but yikes, it's bad when I can't even load freshly made 9000k size save files. Hell, one time I created a fresh new game and it crashed immediately even then.
germ Posted October 22, 2017 Posted October 22, 2017 Should have bought an Intel. AMD is notorious for being garbage, and even their new ryzen stuff sucks. I7-7700 beats all the new ryzens and it's only 300 bucks. A 12 core cpu is completely worthless to a gamer. I have over 200 mods installed on my Skyrim and my game doesn't CTD.
lewd123 Posted October 22, 2017 Posted October 22, 2017 Should have bought an Intel. AMD is notorious for being garbage, and even their new ryzen stuff sucks. I7-7700 beats all the new ryzens and it's only 300 bucks. A 12 core cpu is completely worthless to a gamer. I have over 200 mods installed on my Skyrim and my game doesn't CTD. Where did he say it was AMD? Also, Ryzen is not bad. It's actually really good value. A Ryzen 5 1600X costs about 250 bucks and has 50% more cores than your 7700 does. If you need cores, Ryzen and Threadripper dump all over the (now ironically named) Core series. Intel does have an edge when it comes to single-core speed though, which Skyrim does somewhat favor. In any case, I don't think his processor is the problem here. I think it's the shitty, buggy game. As for the OP, I recommend Crash Fixes and this: https://www.nexusmods.com/skyrim/mods/85443/? That second one doubly so if you use FNIS. FNIS can make a specific kind of crash (the dreaded footIK) more common, and that fixes it by forcing the game to only use one core when first loading in. See, footIK occurs because Bethesda forgot to add a mutex in their code that says "No, load that other thing with that other core first and come back to this," so loading everything with one core and enabling the others after loading fixes it.
godscat Posted October 22, 2017 Posted October 22, 2017 some graphic cards prefer Injcetors, some prefer Wrapper, besides - try both and check frequency of ctd, then try lower some settings or little less ultra versions of ENB presets from authors ( like Ultra High - Performance ). Another thing is start Your game every time before load save or anything with command ( coc test ; dont remember exactly, its load Your game in a small cell with bed and a small rikeling ??? yrggggh dont remember ) then after that every save should load correctly without CTD even if Your character is outside.I do that every time and i can play about 5 hours without any CTD, also i never use any crash fixes cause every time i change more of those extra settings i got more CTD,s Then fokus on proper skeleton, loot, fnis, tes5edit. You will get it
Pauduan Posted October 22, 2017 Posted October 22, 2017 To solve the load issue, you'll have to install Continue Game no Crash, which essentially limits the game to a single CPU core during the load process. I have only Intel CPUs ATM, and I still crash. And I used to crash on pretty much every kind of CPU I've played this game with, as long as I added at least 5-6 mods. Arriving at a stable load order and a clean install folder takes time, which is why there are so many forums, threads, and points of view on this. You may or may not be successful in ridding yourself of the crashes, so feel free to give up. It's just more fun when you do manage to sort things out, but I think everybody has their personal limit. However your CPU is not the issue, it is usually a mod of some kind, a conflict of some kind or a mistaken setting of some kind. Read up the STEP guide and follow it meticulously, and you should be able to reduce your problems. You will never be free of crashes else it would not be a Beth game. Go one step at a time and you should work it out. I agree with Crash fixes, removing it is the number one step to achieving a stable game. If you need the mod your game is very badly broken, you should have a stable game without it. But in general, the game engine bugs out more readily on better machines when heavily modded. The most stable install for me runs on an i3 and a RX460, where I have to be extremely careful about what it runs. On a more powerful machine the install tends to be more complex with more mods to push the machine harder, and that is where the problem begins. My present configuration is a 1080 and a 6600k with 32 gigs of memory, and it is still a work in progress. Remember mods are asking the game engine to do stuff it's not really supposed to do. You will face problems if it isn't done properly. This being LL a number of allegories come to mind, but this being a public forum I'll desist.
lewd123 Posted October 22, 2017 Posted October 22, 2017 To solve the load issue, you'll have to install Continue Game no Crash, which essentially limits the game to a single CPU core during the load process. I have only Intel CPUs ATM, and I still crash. And I used to crash on pretty much every kind of CPU I've played this game with, as long as I added at least 5-6 mods. Arriving at a stable load order and a clean install folder takes time, which is why there are so many forums, threads, and points of view on this. You may or may not be successful in ridding yourself of the crashes, so feel free to give up. It's just more fun when you do manage to sort things out, but I think everybody has their personal limit. However your CPU is not the issue, it is usually a mod of some kind, a conflict of some kind or a mistaken setting of some kind. Read up the STEP guide and follow it meticulously, and you should be able to reduce your problems. You will never be free of crashes else it would not be a Beth game. Go one step at a time and you should work it out. I agree with Crash fixes, removing it is the number one step to achieving a stable game. If you need the mod your game is very badly broken, you should have a stable game without it. But in general, the game engine bugs out more readily on better machines when heavily modded. The most stable install for me runs on an i3 and a RX460, where I have to be extremely careful about what it runs. On a more powerful machine the install tends to be more complex with more mods to push the machine harder, and that is where the problem begins. My present configuration is a 1080 and a 6600k with 32 gigs of memory, and it is still a work in progress. Remember mods are asking the game engine to do stuff it's not really supposed to do. You will face problems if it isn't done properly. This being LL a number of allegories come to mind, but this being a public forum I'll desist. No, Continue Game No Crash is the old version that that loads you into a small cell and then loads your save from there. He definitely wants Load Game CTD Fix, which I linked above. Crash Fixes can be configured, so you can disable the fixes that you think are suspect. You could even pare it down to just the string limit save file crash. All that does is reformat your save when it reaches the point where you wouldn't be able to load it, and tell the game how to read the new format. Using mods with a lot of strings will inevitably cause this, and you are on LL, so...
ReMeDy Posted October 22, 2017 Author Posted October 22, 2017 Yea, I do have an Intel, not an AMD. My Intel is an i7-5820K @ 3.30GHz.Okay, let me try everyone's ideas and post back.
Nagib Posted October 22, 2017 Posted October 22, 2017 1. Get Crash Fixes and use it with UseOSAllocators=1. Read on the mod's page on way to install it.Link: https://www.nexusmods.com/skyrim/mods/72725/? 2. This SKSE mod will prevent crashes on loading of save files. (Happens when you have many animation mods with FNIS).Link: https://www.nexusmods.com/skyrim/mods/85443/?3. In your SKSE folder (Not SKSE/Plugins, just SKSE), do you have SKSE.ini with following settings? _______________________________[Display]iTintTextureResolution=2048[General]ClearInvalidRegistrations=1EnableDiagnostics=1[Memory]DefaultHeapInitialAllocMB=768ScrapHeapSizeMB=256_______________________________Though, memory part is probably not necessary with Crash Fixes's UseOSAllocators=1.4. ENBoost. After you install ENB, all latest version have it preinstalled. You will have to configure enblocal.ini for the best effect.
27X Posted October 23, 2017 Posted October 23, 2017 Should have bought an Intel. AMD is notorious for being garbage, and even their new ryzen stuff sucks. I7-7700 beats all the new ryzens and it's only 300 bucks. A 12 core cpu is completely worthless to a gamer. I have over 200 mods installed on my Skyrim and my game doesn't CTD. Stop breathing my air.
Celedhring Posted October 23, 2017 Posted October 23, 2017 Oldrim is just poorly optimized, that's all there is to it.
Yuuen Posted October 23, 2017 Posted October 23, 2017 Coming into this as a person who also has 12 cores, (Cores really aren't a great indicator of overall power/stability or whatever btw, so people talking about AMD are talking out of their ass), it sounds more like you've broken things, made changes without knowing what they do and poorly configured your settings. So here's a few tips: - Crashes sometimes involve more to do with in-game conflicts than memory, so you should check for mods that double up in locations/mechanics and maybe even be an issue with a mod having a problem that is fixed in a later version. Basically, keep your load order "Tidy" even if you're like me with 240+ plugins. - Check to make sure your ENB and NVidia settings are optimized for your graphics card. - (As said above) SKSE memory patch enabled in the SKSE.ini and install crash fixes with OSAllocator enabled. [Display] iTintTextureResolution=4096 [General] ClearInvalidRegistrations=1 EnableDiagnostics=1 [Memory] DefaultHeapInitialAllocMB=1024 ScrapHeapSizeMB=512 This is what mine is set to, but I would suggest trying 768 for defaultHeap and 256 for the ScrapHeap first. - This has had mixed responses, but I personally haven't had issues after doing it, but you can try adding multi-core/multi-thread settings to your skyrim.ini. You should look into this more yourself, but here's some examples. [BackgroundLoad] bBackgroundLoadLipFiles=1 bLoadBackgroundFaceGen=1 bUseMultiThreadedFaceGen=1 bBackgroundCellLoads=1 bLoadHelmetsInBackground=1 bUseMultiThreadedTrees=1 bUseBackgroundFileLoader=1 [General] iNumHWThreads=6 iHWThread6=5 iHWThread5=4 iHWThread4=3 iHWThread3=2 iHWThread2=1 iHWThread1=0 iAIThread2HWThread=3 iAIThread1HWThread=2 iRenderingThread2HWThread=1 iRenderingThread1HWThread=0 bMultiThreadMovement=1 bUseThreadedTempEffects=1 bUseThreadedParticleSystem=1 bUseThreadedMorpher=1 HAVOK] iNumThreads=6 There are additional options for skyrimprefs.ini, but again, look into it yourself more. I will just add for the sake of it, do not use any of these "No crash" mods that put you in qasmoke on game start or whatever, they simply aren't necessary and cause more underlying problems. I've run this game on that same processor with an incredibly heavily load order, it's a great CPU and it should easily be able to deal with skyrim if you've got it optimized.
yatol Posted October 23, 2017 Posted October 23, 2017 I will just add for the sake of it, do not use any of these "No crash" mods that put you in qasmoke on game start or whatever, they simply aren't necessary and cause more underlying problems. I've run this game on that same processor with an incredibly heavily load order, it's a great CPU and it should easily be able to deal with skyrim if you've got it optimized. and what are those underlying problems you are talking about? i coc qasmoke since years, without that, i can't load saves because some mods quests priorities are highter than the skyrim.esm quests they need to be load it was the same with enderal, had to coc a farmhouse to load my enderal save after adding mods and fixing those quests priorities to be able to load the save without coc qasmoke... no idea what those quests need to be load, no idea what quests priorities have to be edited either, too complicated to do something about it
Gnafron Posted October 23, 2017 Posted October 23, 2017 1. Get Crash Fixes and use it with UseOSAllocators=1. Read on the mod's page on way to install it. Link: https://www.nexusmods.com/skyrim/mods/72725/? 2. This SKSE mod will prevent crashes on loading of save files. (Happens when you have many animation mods with FNIS). Link: https://www.nexusmods.com/skyrim/mods/85443/? 3. In your SKSE folder (Not SKSE/Plugins, just SKSE), do you have SKSE.ini with following settings? _______________________________ [Display] iTintTextureResolution=2048 [General] ClearInvalidRegistrations=1 EnableDiagnostics=1 [Memory] DefaultHeapInitialAllocMB=768 ScrapHeapSizeMB=256 _______________________________ Though, memory part is probably not necessary with Crash Fixes's UseOSAllocators=1. 4. ENBoost. After you install ENB, all latest version have it preinstalled. You will have to configure enblocal.ini for the best effect. This. If you use the UseOSAllocators function, don't forget to install https://www.nexusmods.com/skyrim/mods/75795/? (SKSE Plugin Preloader), it's essential. Also... You could have a 24-core or 4096-core CPU, it wouldn't prevent Skyrim from crashing. It only uses two cores at best anyway. It's like driving a Ferrari in a traffic jam.
Yuuen Posted October 24, 2017 Posted October 24, 2017 I will just add for the sake of it, do not use any of these "No crash" mods that put you in qasmoke on game start or whatever, they simply aren't necessary and cause more underlying problems. I've run this game on that same processor with an incredibly heavily load order, it's a great CPU and it should easily be able to deal with skyrim if you've got it optimized. and what are those underlying problems you are talking about? i coc qasmoke since years, without that, i can't load saves because some mods quests priorities are highter than the skyrim.esm quests they need to be load it was the same with enderal, had to coc a farmhouse to load my enderal save after adding mods and fixing those quests priorities to be able to load the save without coc qasmoke... no idea what those quests need to be load, no idea what quests priorities have to be edited either, too complicated to do something about it The fact you have to rely on that is a problem of your own doing, I've played skyrim on 3 different computers of varying power over the course of about 4 years and I've never needed to use it. I think you should focus on fixing your issues rather than trying to justify a bad and messy solution. This topic isn't what I made the post here to discuss, they needed help regarding optimization so that's what I've done. If you want to go on a rant about qasmoke, go make your own thread.
lewd123 Posted October 24, 2017 Posted October 24, 2017 The fact you have to rely on that is a problem of your own doing, I've played skyrim on 3 different computers of varying power over the course of about 4 years and I've never needed to use it. I think you should focus on fixing your issues rather than trying to justify a bad and messy solution. This topic isn't what I made the post here to discuss, they needed help regarding optimization so that's what I've done. If you want to go on a rant about qasmoke, go make your own thread. Actually, this guy determined that the cause was Bethesda forgetting a mutex in their code. https://www.nexusmods.com/skyrim/mods/85443/? "Essentially a programmer at Bethesda forgot to put a mutex somewhere to protect critical data which allowed one CPU core to access data which was not yet finished being loaded by another CPU core. In a vanilla game setup there was only a rare chance of this happening because there wasn't enough data to trigger the race condition, but in a heavily modded game more time is spent on loading data which made it likely for another CPU core to access it prematurely without a mutex there to protect it. The double load methods people used to get around the crash on load worked due to the fact less data was loaded between steps which reduced the chances of the race condition happening because processing happened a little quicker with base data being loaded first and then everything else the second load with the base data already cached in memory."
yatol Posted October 24, 2017 Posted October 24, 2017 I've played skyrim on 3 different computers of varying power over the course of about 4 years and I've never needed to use it so what, you want a cookie? i can run helgen start without problem, have no need for alternate start i don't crash with my 3 years old save and there's no need to fix all mods i try, can just coc qasmoke to load the save, finish the mod, and be done with it still waiting for those underlying problems you are talking about but since you just made that up, of course you can't say much about that
27X Posted October 24, 2017 Posted October 24, 2017 The fact you have to rely on that is a problem of your own doing, I've played skyrim on 3 different computers of varying power over the course of about 4 years and I've never needed to use it. I think you should focus on fixing your issues rather than trying to justify a bad and messy solution. This topic isn't what I made the post here to discuss, they needed help regarding optimization so that's what I've done. If you want to go on a rant about qasmoke, go make your own thread. Actually, this guy determined that the cause was Bethesda forgetting a mutex in their code. https://www.nexusmods.com/skyrim/mods/85443/? "Essentially a programmer at Bethesda forgot to put a mutex somewhere to protect critical data which allowed one CPU core to access data which was not yet finished being loaded by another CPU core. In a vanilla game setup there was only a rare chance of this happening because there wasn't enough data to trigger the race condition, but in a heavily modded game more time is spent on loading data which made it likely for another CPU core to access it prematurely without a mutex there to protect it. The double load methods people used to get around the crash on load worked due to the fact less data was loaded between steps which reduced the chances of the race condition happening because processing happened a little quicker with base data being loaded first and then everything else the second load with the base data already cached in memory." Was just about to post this. "Always works for me" is not any kind of factual evidence. The reason to load in to qasmoke is to avoid the race rethread issue which is a known issue for both versions of Skyrim. She has a history of posting crap like this without any factual evidence or aggregate metrics to back it up on a regular basis.
Yuuen Posted October 24, 2017 Posted October 24, 2017 I've played skyrim on 3 different computers of varying power over the course of about 4 years and I've never needed to use it so what, you want a cookie? i can run helgen start without problem, have no need for alternate start i don't crash with my 3 years old save and there's no need to fix all mods i try, can just coc qasmoke to load the save, finish the mod, and be done with it still waiting for those underlying problems you are talking about but since you just made that up, of course you can't say much about that I was just trying to avoid starting beef in someone else's thread because you seem like you're trying to be such an edgy shitposter. The fact you have to rely on that is a problem of your own doing, I've played skyrim on 3 different computers of varying power over the course of about 4 years and I've never needed to use it. I think you should focus on fixing your issues rather than trying to justify a bad and messy solution. This topic isn't what I made the post here to discuss, they needed help regarding optimization so that's what I've done. If you want to go on a rant about qasmoke, go make your own thread. Actually, this guy determined that the cause was Bethesda forgetting a mutex in their code. https://www.nexusmods.com/skyrim/mods/85443/? "Essentially a programmer at Bethesda forgot to put a mutex somewhere to protect critical data which allowed one CPU core to access data which was not yet finished being loaded by another CPU core. In a vanilla game setup there was only a rare chance of this happening because there wasn't enough data to trigger the race condition, but in a heavily modded game more time is spent on loading data which made it likely for another CPU core to access it prematurely without a mutex there to protect it. The double load methods people used to get around the crash on load worked due to the fact less data was loaded between steps which reduced the chances of the race condition happening because processing happened a little quicker with base data being loaded first and then everything else the second load with the base data already cached in memory." Was just about to post this. "Always works for me" is not any kind of factual evidence. The reason to load in to qasmoke is to avoid the race rethread issue which is a known issue for both versions of Skyrim. She has a history of posting crap like this without any factual evidence or aggregate metrics to back it up on a regular basis. Yet you just did the same thing? Making a claim without providing evidence. Sure, there is info out there about how badly skyrim is optimized, I wasn't saying there isn't. I just said, I have used the exact same processor he has under a heavy load order and I never needed to use QASmoke and made suggestions of things to check above that. The fact you have to rely on that is a problem of your own doing, I've played skyrim on 3 different computers of varying power over the course of about 4 years and I've never needed to use it. I think you should focus on fixing your issues rather than trying to justify a bad and messy solution. This topic isn't what I made the post here to discuss, they needed help regarding optimization so that's what I've done. If you want to go on a rant about qasmoke, go make your own thread. Actually, this guy determined that the cause was Bethesda forgetting a mutex in their code. https://www.nexusmods.com/skyrim/mods/85443/? "Essentially a programmer at Bethesda forgot to put a mutex somewhere to protect critical data which allowed one CPU core to access data which was not yet finished being loaded by another CPU core. In a vanilla game setup there was only a rare chance of this happening because there wasn't enough data to trigger the race condition, but in a heavily modded game more time is spent on loading data which made it likely for another CPU core to access it prematurely without a mutex there to protect it. The double load methods people used to get around the crash on load worked due to the fact less data was loaded between steps which reduced the chances of the race condition happening because processing happened a little quicker with base data being loaded first and then everything else the second load with the base data already cached in memory." To the OP I was suggesting that they should check for other causes because I have used that same processor and this wasn't a necessary procedure they had to go through. To the post yatol made, sure. I don't what kind of computer they have or what setup they have. I'm just giving my experience as someone who has tried to break this game for 4 years and haven't ever hit that "Oh I can't load this save anymore, time to use QASmoke", it's almost always something else breaking if that happens. I'll figure it out, fix it, move on and the game plays in its ideal state again.
yatol Posted October 24, 2017 Posted October 24, 2017 still waiting for those underlying problems you are talking aboutbut since you just made that up, of course you can't say much about that I was just trying to avoid starting beef in someone else's thread because you seem like you're trying to be such an edgy shitposter. it's you that start shit by saying i have to coc qasmoke because too stupid to fix mods, when i just ask details about your blabla about those underlying problems and and still waiting for those underlying problems you are talking about, it's you that wrote that above, yet you can't say anything about it?
Yuuen Posted October 24, 2017 Posted October 24, 2017 still waiting for those underlying problems you are talking aboutbut since you just made that up, of course you can't say much about that I was just trying to avoid starting beef in someone else's thread because you seem like you're trying to be such an edgy shitposter. it's you that start shit by saying i have to coc qasmoke because too stupid to fix mods, when i just ask details about your blabla about those underlying problems and and still waiting for those underlying problems you are talking about, it's you that wrote that above, yet you can't say anything about it? It's just how I've seen you operate before "Harass until they say I'm correct". Underlying problems depend on the load order, I can't go on about putting waste data into storageUtil if they don't use that or how loading from an unconfigured start with X, Y or Z mod at QASmoke to a configured save can sometimes cause anomalies. Do I have some source from some major voice in the community on some tweak site? No. If you want to call me all sorts of names, yell and scream in any help thread I post in or whatever because of that, feel free. I'm just saying what I've seen. There's a lot of problems that go unspoken because they're so specific and usually people just give up and go the nuclear option. I will never give information to someone if I feel like it could do more damage than good. All I said what that they don't need to use QASmoke as their firstline option and they should look into other causes.
yatol Posted October 24, 2017 Posted October 24, 2017 I'm just saying what I've seen. and what have you seen then? give some details about those underlying problems you are talking about, instead of just talking about them and while you are it, if you want them to look into other causes, tell them how to do that
Yuuen Posted October 24, 2017 Posted October 24, 2017 I'm just saying what I've seen. and what have you seen then? give some details about those underlying problems you are talking about, instead of just talking about them and while you are it, if you want them to look into other causes, tell them how to do that I did tell them how to do that. I gave a small checklist of things to check. Or did you only read the bottom line? I haven't touched QASmoke for at least a year and a half, so count this as a victory or whatever you want but I don't have an extensive and descriptive list of issues. It was usually things along the lines of MCM's breaking, High heels framework acting weird if you tried to load from that into a save with heels which would then make you have to take them off, save and then load that save, Overlays being wiped, Distance LOD issues, sometimes a mod would need to be reset because the configuration went wonky etc etc. The main point is, QASmoke doesn't fix anything, it's a band aid, a cover up for the larger issues. I understand that you've found it to work with whatever you've got running but surely you realize it has a limit?
lewd123 Posted October 24, 2017 Posted October 24, 2017 I did tell them how to do that. I gave a small checklist of things to check. Or did you only read the bottom line? I haven't touched QASmoke for at least a year and a half, so count this as a victory or whatever you want but I don't have an extensive and descriptive list of issues. It was usually things along the lines of MCM's breaking, High heels framework acting weird if you tried to load from that into a save with heels which would then make you have to take them off, save and then load that save, Overlays being wiped, Distance LOD issues, sometimes a mod would need to be reset because the configuration went wonky etc etc. The main point is, QASmoke doesn't fix anything, it's a band aid, a cover up for the larger issues. I understand that you've found it to work with whatever you've got running but surely you realize it has a limit? The FootIK crash eventually happens in a heavily-modded game even if you do everything perfectly. It happens especially early if you have a lot of FNIS animations. If you've never encountered it, then you should just count yourself lucky, and stop trying to cast doubt on a tried-and-true method of circumventing it. Hell, another version of the same method has you load your first save from the Alternate Start room, and then load your recent one, and there's no argument to say that that's broken or wrong. Loading in steps makes a lot of sense, and it's Bethesda's fault that the game sometimes can't load everything in the right order without it. And you still haven't defined these "larger issues" you keep insisting that step-loading is a bad workaround for.
Veladarius Posted October 25, 2017 Posted October 25, 2017 I have used most all of the ini settings that Yuuen posted earlier along with a every multithreaded command I could find and still had issues loading a regular save and had to resort to using a save made in the Alternate Start dungeon just after setting up my MCM menu's before loading the save game I wanted. This started before I installed any sort of SexLab based mod but had a good sized load order. Even after I spent 2 months tracking down mods causing papyrus issues and fixing or removing them it still persisted. I run a heavily modded game (SexLab and DD mods, enb and HDT physics) and am just under the esp limit (several of them are merged armor and/or weapon mods). Like Yuuen I have heavily modified the ini files including increasing the time allotted to papyrus. I have go through my papyrus logs from time to time looking for issues that need addressing. I use enboost along with my enb and still have some of the older fixes still sitting in my SKSE folder. I don't use a large number of SexLab animations, just one or two collections of animations (a good number of animations but no where near what is out there). But since the dx9 patch was released by Microsoft I have been able to load any save I want including outdoors. As Yatol stated earlier: i coc qasmoke since years, without that, i can't load saves because some mods quests priorities are highter than the skyrim.esm quests they need to be load it was the same with enderal, had to coc a farmhouse to load my enderal save after adding mods If quest priorities from mods were the issue then I would not be able to load any save I want at this point seeing as I have a number of quests in CD with priorities of 90+ (including one I just made with a priority of 99, dialogue at 100 and still have npc's that get past it) so this is not the issue. I had though the issue was with papyrus and having a large number of mods with scripts constantly checking things was the issue as at times I could load an auto save made when moving between places but that was only occasionally. Since the dx9 patch recently released and I can load anywhere I want including outdoors (I use a ugrids of 7 as well) and can go several hours without crashing, typically 3-4 depending on sexlab usage. My current character is level 22 and I just finished the Dawnguard DLC main quest (last part going through Falmer territories was especially taxing as I was using Estrus Chaurus and Estrus Spider). My recommendations are this: 1 - Resort your load order (LOOT is crap, BOSS was as well as far as I am concerned). I sort my load order starting with mods that affect major areas, overhauls or major texture replacers. From there I work down and each step affects smaller and smaller areas. Next is character beautification mods and mods affecting npc's (AI mods as well as mods affecting creatures such as Vampires or Werewolves). Next are the SexLab and DD mods then armor and weapon mods. Last are patches that allow different mods to work together and the bashed patch from Wrybash last. Of course make sure any mods with masters be loaded after their master is. I use WryeBash to manage my load order as it is easy to see what mods have masters and easily find them. 2 - Go through your load order and look for mods causing issues, particularly ones causing repeated errors throughout the game. Check the log after crashes for errors and such just remember there will be some errors from mods loading if they have the option to use other mods as an error will be generated if it isn't found, so long as it is not a required mod it isn't an issue. Watch for mods that constantly update in the background, there are a number of them that update every few seconds and can cause instabilities. Some can be changed in their MCM menu to update less often, Creature Framework is an example as it updates every 5 seconds and scans every actor it can in a 2 cell radius and caused my game to become unstable until I dialed it back by a lot. I just had to do this in FO4 as I recently updated to the latest version and updated FOSE and the mods using it. I suddenly found myself having crashes, turned out that one of the mods I had didn't like the new FO4 version and caused dump stack errors from the start of the game even on a entirely new game. The mod was tossed and it works fine now. 3 - Modify your ini file. If you have a lot of mods then papyrus may be choking at the default settings. This is my Skyrim ini file, take what you want from it: [General] sLanguage=ENGLISH uExterior Cell Buffer=64 sLocalSavePath=Saves\ bBorderRegionsEnabled=1 uGridsToLoad=7 bPreemptivelyUnloadCells=1 iPreloadSizeLimit= 4194304000 sIntroSequence= bUseThreadedTempEffects=1 bUseThreadedParticleSystem=1 bMultiThreadMovement=1 bUseThreadedMorpher=1 iNumHWThreads=4 iHWThread4=3 iHWThread3=2 iHWThread2=1 iHWThread1=0 bAnimateDoorPhysics=0 bPreCullActors=1 bUseHardDriveCache=1 bUseThreadedBlood=1 bUseThreadedTextures=1 bUseThreadedMeshes=1 bUseThreadedLOD=1 bUseThreadedAI=1 bBackgroundLoadVMData=1 iAiThread1HWThread=5 iAiThread2HWThread=3 iRenderingThread1HWThread=1 iRenderingThread2HWThread=0 [Papyrus] bEnableLogging=1 bEnableTrace=1 bLoadDebugInformation=1 fUpdateBudgetMS=1.2 fExtraTaskletBudgetMS=2.0 fPostLoadUpdateTimeMS=1000.0 iMinMemoryPageSize=128 iMaxMemoryPageSize=512 iMaxAllocatedMemoryBytes=76800 [Display] fShadowLODMaxStartFade=1000.0 fSpecularLODMaxStartFade=2000.0 fLightLODMaxStartFade=3500.0 iShadowMapResolutionPrimary=1024 iTintTextureResolution=2048 bAllowScreenshot=1 fDefaultWorldFOV=67 fDefault1stPersonFOV=67 fSunShadowUpdateTime=0.25 fSunUpdateThreshold=0.25 fNearDistance=25 bFloatPointRenderTarget=1 [Audio] fMusicDuckingSeconds=6.0 fMusicUnDuckingSeconds=8.0 fMenuModeFadeOutTime=3.0 fMenuModeFadeInTime=1.0 [Grass] bAllowLoadGrass=0 bAllowCreateGrass=1 bDrawShaderGrass=0 iMinGrassSize=50 iMaxGrassTypesPerTexure=10 [GeneralWarnings] SGeneralMasterMismatchWarning=One or more plugins could not find the correct versions of the master files they depend on. Errors may occur during load or game play. Check the "Warnings.txt" file for more information. [Archive] 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, Dragonborn.bsa, Dawnguard.bsa, Hearthfires.bsa, Update.bsa [Combat] fMagnetismStrafeHeadingMult=0.0 fMagnetismLookingMult=0.0 [Water] bReflectExplosions=0 bReflectLODLand=1 bReflectLODObjects=0 bReflectSky=1 bReflectLODTrees=0 [backgroundLoad] bBackgroundLoadLipFiles=1 bLoadBackgroundFaceGen=1 bUseMultiThreadedFaceGen=1 bBackgroundCellLoads=1 bLoadHelmetsInBackground=1 bUseMultiThreadedTrees=1 bUseBackgroundFileLoader=1 bSelectivePurgeUnusedonFastTravel=1 [Animation] bMultiThreadBoneUpdate=1 [Decals] bDecalMultithreaded=1 [VATS] bVATSDisable=1 4 - Use a safe load then load the one you want if you have to until you get things sorted out, there is nothing wrong with it if it lets you play the game. Some mods or mod combinations may just make it unavoidable. 5 - This should be common sense but people still do it: Don't update a major mod during an ongoing game, wait until you are starting a new game to update, especially mods like the Unofficial patch. While they can fix Aliases or Properties of quests these will not update in a current game and if they change scripts to make use of them they will still have whatever was in them (including NONE as they generally will not fill). In your case, I suggest starting with the logs as well as using a safe load (qasmoke or whatever you need to use) and see if you can get things going that way and continue working on it. As for my system I have an i5 2500k @ 3.6ghz, 16GB ram and an overclocked AMD 280x w/ 3gb. If you want help with the logs and such feel free to PM me.
Yuuen Posted October 25, 2017 Posted October 25, 2017 I did tell them how to do that. I gave a small checklist of things to check. Or did you only read the bottom line? I haven't touched QASmoke for at least a year and a half, so count this as a victory or whatever you want but I don't have an extensive and descriptive list of issues. It was usually things along the lines of MCM's breaking, High heels framework acting weird if you tried to load from that into a save with heels which would then make you have to take them off, save and then load that save, Overlays being wiped, Distance LOD issues, sometimes a mod would need to be reset because the configuration went wonky etc etc. The main point is, QASmoke doesn't fix anything, it's a band aid, a cover up for the larger issues. I understand that you've found it to work with whatever you've got running but surely you realize it has a limit? The FootIK crash eventually happens in a heavily-modded game even if you do everything perfectly. It happens especially early if you have a lot of FNIS animations. If you've never encountered it, then you should just count yourself lucky, and stop trying to cast doubt on a tried-and-true method of circumventing it. Hell, another version of the same method has you load your first save from the Alternate Start room, and then load your recent one, and there's no argument to say that that's broken or wrong. Loading in steps makes a lot of sense, and it's Bethesda's fault that the game sometimes can't load everything in the right order without it. And you still haven't defined these "larger issues" you keep insisting that step-loading is a bad workaround for. Why are you coming back to drag up an issue that's been dead for 2 days, are you that desperate for drama? I have not had that issue no, even with 11k animations and soon I'll be upgrading to FNIS 7.0 with the 20k limit. Doesn't mean that's the only issue to ever cause crashes on save load. You've twisted what I've said, I said loading from QASmoke can cause problems. Loading from that last configured save at the Alternate start room and then loading to your latest save is a much better solution than QASmoke, I've experienced very few issues with doing that. Like the other person, you're assuming that because I told the OP who had the same hardware as me at one point, that they don't need to use this solution that people with weaker computers or people who have yet to fix their bigger problems, doesn't mean there aren't people who don't need to use it as a temporary method to try and fix the issue that's breaking their saves. Asking what are these "larger issues" proves that you really don't know a damn thing about modding, coming in here stirring up all this and acting all high and mighty because you posted a quote, do I seriously have to explain to you every single reason the game can crash on a save load? Are you kidding me? There's damn near 10 posts a day with people who have this issue for all sorts of reasons, mod conflict, string limit, script errors, script load, corruption due to bad timing, a mod breaking, generally broken mods, ini settings, ENB settings (if they use it), your dreaded FootIK crash, hardware problems and many more. You can't sit there and tell me that QASmoke is going to fix every single one of these issues and while sometimes QASmoke may avoid the crash for a couple, it's still not fixing a thing. So again, it's a bandaid fix for people who can't or wont fix the problems with their game. The last person got all defensive and took it personal when I said this, but it's true. You only need that fix if there is something inherently broken in your game that you either don't understand how to fix because you're new to modding or you don't want to fix because it's just easier to avoid it and try to step save. I was ridiculed for stating that I've played this game heavily modded on 3 different computers of very differing power without having that issue and I'm seriously just starting to wonder if they were just salty because they have problems they can't deal with. Because how is that not conclusive to my point? You shouldn't need QASmoke if you have your game running properly, no matter what quote from whatever community bigwig. It just shouldn't be necessary. I'm not talking about direct hardware limits here. If you're trying to slap a 200+ plugin load order with 4 large quest mods, 10k animations, texture replacers out the ass and scripted mods for everything you can on a basic budget PC and crashing every second, then that's your own stupidity breaking the game and not even QASmoke can fix that. I don't sit in these help forums looking for my next big argument. I post my piece and then people like you that take it as a personal offense that some "no name" said something that differs from what someone who probably isn't even involved with skyrim anymore said 2 years ago. Sure, I'm a no name, I haven't published my mods but over these 4 years I've spent a lot of time fixing skyrim and working with every modding tool under the sun so while you may not like it, it's a fact that I know this game. Just because they made a fix that a lot of people liked, doesn't make them a god. People can disagree and state methods they found to be effective. Skyrim as a modding community is dying enough as it is, don't try and shut down different ways of thinking just because you don't agree with them due to your narrow experience and your reliance on this "hive mind" mentality.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.