A side effect I've been notified of will no longer allow rabbits to spawn while using my fix. Adding the rabbit's record to any other "LCharAnimalxPrey" spawn list using "TES5Edit" will remedy this. Bethesda's hand-placed locations like Spriggan lairs and some shrines still spawn rabbits.
I have decided to lock the comments thread because of negativity. If you don't like this fix, then don't download it. But, I use it myself after playing many thousands of hours dealing with the CTD it fixes. If you have never encountered this particular CTD before then don't use my mod. But, if you are suffering from the "TESCombatStyle form" CTD, I can promise you, it works. I've tested it myself before uploading for a complete playthrough without using the fast-travel mechanic without suffering through any more crashes caused by the "TESCombatStyle form" bug.
Thank you and goodnight.
(Edit) Still no CTDs as of October 1st 2018. This "placebo" works. (Edit) Still no CTDs as of November 17th 2018. (Edit) Still no CTDs as of January 12th 2019. (Edit) Still no CTDs as of March 15th 2019. (Edit) I've since moved on to Skyrim SE, but it all ran fine with no more CTDs involving the "TESCombatStyle" error message.
All support/future updates for mods like USLEEP (USSEP on Skyrim SE Nexus) are Skyrim SE-exclusives. USLEEP support has been shut down & comments for USLEEP have been locked. Also, mods like Beyond Skyrim, Skywind, & Skyblivion will be Skyrim SE-exclusives as well. SkyRe (Skyrim Redone) has officially been ported to Skyrim SE as has Racemenu. Oldrim's days as a viable platform are numbered now that SKSE64 is out of Alpha. It'll only be a matter of time before other overhauls like Requiem/PerMa find their way over to Skyrim SE as well. ENB has come a long way with many of the features of Oldrim ENB (sans Parallax) now implemented. I'll take a 64 bit engine without all the bottlenecks/memory limitations over Oldrim any day of the week. Far less lag/freezes/CTDs thanks to the new engine. This mod is now available for Skyrim SE at the link I provided above too.
Your dreams are great and all, but way too many of my must have mods have authors that have no intention of porting their mods to SE, so yeah I don't care. SE isn't worth it and never will be.
Depends on your priorities. To me it's a lot like (being a Mac user) that I have the choice to play Morrowind with MWSE (the MW equivalent of SKSE and OBSE) in a Windows VM, the way I do with Oblivion and Skyrim, or the choice to play OpenMW natively, using both a different approach to graphics enhancement and memory management, and a different general mod build-out. I actually don't mind at all, since it gives me radically different gameplay experiences in roughly the same game world. Eventually doing Skyrim SE will give me that for Skyrim, too.
Anyway, I'm not going to cry about USLEEP abandoning "Oldrim". Frankly, they broke so damned many mods when they did USLEEP (instead of the separate patches for the DLCs) that it's been hard to recover from it. I would much rather deal with individuals intelligently patching bugs as they find them, and if I get near the mod limit do some script or manual merges. It's nice to have big "community project" patches take care of the bulk of the early-discovered problems, but years after the fact we can't much expect anything but people still actually playing the original game to continue to work on patches for it.
I bought SE. Played it for maybe a week. Went back to Oldrim. More ENB options. More physics options. I have virtually no trouble with crashes unless I've done something wrong. I have 253 esps enabled and countless other mods installed.It runs smooth af. It looks BEAUTIFUL. USLEEP works fine in its current state. I just don't see any logical reason to play SE, even though I paid full price for it. Oldrim is my home. Oldrim is beautiful.
Yea some people really get salty when when you talk s#*! on SE, guess it depends what kind of playthrough you wanna do. I dont know about them but im trying to play the best version of skyrim there is and thats Ultimate skyrim for oldrim baybee
I have no need to justify my love and preference for the Legendary Edition. Is it really so shocking to the SSE crowd that some LE players are simply content?
Not that this needs to be an SSE vs LE thread, but since you guys are talking about it the one thing I never see mentioned (probably because not that many people do it) are the lack of a desire to painstakingly re-edit esp's in SSE. I have an ESP that I have literally spent 2 years editing NPC's on. With SkyRe making it to SSE, hypothetically I have no reason to continue using LE. But im not about to do 2 years of work all over again so. In the words of Max Holloway, it is what it is.
As i said before, SSE is a waste of time, it's your typical remaster, Skyrim is an old, 2011 game, no one cares about it's new pretty looks (which you can easily match on oldrim with the right mods) and it's missing a lot of great mods that will never be seen again.
It's more or less and updated skyrim missing a lot of mods. Glad i never bothered with it. though i was curious that this mod may have pointed out what has been causing the random world CTDS. but it could have been any number of things. i guess i'll see in time. i mean that's another thing...If this mod is needed on SSE then that means they couldn't even bother to fix that o_O what was the point of it again?
SSE's "exclusive mods" aren't anywhere near enough to make up for the massive missing mods that were on oldrim. SSE will die out long before oldrim comes close to it. but skyrim as a whole is getting older and older. since they are the same game, they may die together, but if not, SE will certainly go first.
and yea, USLEEP is a dead mod now, if they actually did abandon oldrim. which is another example that if that mod is still needed for SSE they didn't fix much..
the one thing SE handles much better is having loads and loads of assets loaded at the same time, things like open cities have almost no performance hit on SE, while my framerate drops below 15 in oldrim. it's also generally more stable out of the box, while oldrim requires going through hours of tutorials and different programs. but oldrim also has a lot more mods. in the end, enb is what pushed me back to oldrim. SacredSage, please tell me how to get the SE godrays/global fog through enb.
Each version has their advantages. SE does however have ESPFEs which are insanely cool. Not having to merge esps to meet the plugin limit is really nice.
my game automatically crashes after the sound comes back. i rarely crash in the overworld, but it happens. i'm still concerned about the side effects of this mod though.
That sounds like a different crash. My sounds and music kept playing until I closed the Skyrim window. It was also accompanied by the Windows error chime.
It pops up in a message box on the desktop after a crash when you have "Crash Fixes" by "meh21" installed. But, it disappears as soon as you close Skyrim's window.
Those aren't formids. They're code addresses. https://en.wikipedia.org/wiki/Machine_code You've just mutilated some completely innocent records.
Although it would be amusing if it turns out rabbits were causing your crashes all along and by removing rabbits you fixed the crash... amusing but entirely unrelated to the crash fixes error code.
It is a fox that has a blank name when you click on it in the console. (I.E. Instead of saying "Fox", it says "".) It was a random occurrence that instead of spawning normal animals, it would spawn the non-moving CTD causing fox that would crash the game if anything attacks it or even if the player moves close to it. With my fix installed, the CTD causing foxes no longer spawn. It happened randomly and with my fix installed, it won't happen again. I repeat, it is a random occurrence that happens randomly while wandering Skyrim. It didn't always happen, most of the time was normal spawns. Other than the desktop message box that popped up after the crash, I found no other error message.
What I am wondering is from what you got the "TESCombatStyle" information? Did the error message you got from Crash Fixes look similar to this http://i.imgur.com/q22dCzG.png but actually mentioned TESCombatStyle? I simply have a hard time finding similar good reports.
Common sense dictates this error message from Crash Fixes would have shown up plenty times before if this is a vanilla problem. So this means something else might have to happen as well. Like a badly sorted load order or another plugin changing something.
The point is to actually understand the cause of problem and then provide a proper explanation and then a fix for it without breaking anything else. All we have so far is just noise because there is no documentation of the problem. Simple troubleshooting starts by making a test case that 100% triggers the problem by always spawning the same problematic critter for example.
Without the proper problem description nobody knows if they have the problem or if the "fix" actually does anything useful. Because as long as the CTD is "random" you don't actually know if it is fixed. Might be just lucky for a long time or something else changed in the meantime.
What i think people are trying to say is that you mistook a code adress given by the crash fixes log for a form id, (which i guess are pretty diferent things) and looked up for the wrong thing in Tesedit, which means that the form ID you searched as nothing to do with the crash fix report. So you are changing a totally unrelated thing to your crash error, which means that, unless you got extremely luck and actually by accident managed to find a form id that was givng you trouble in your load order, this wont actually help. I maybe wrong of course, i'm no expert just basing my thoughts on other peoples opinion here and at skyrimmods reddit.
The best proof I have of the error message would be a picture I took of the message on my TV screen using my phone to help me remember the codes. After making the fix, the very same fox that I encountered just west of Rorikstead that caused a CTD whenever I moved toward it, attacked it or even killed it with the console was finally able to be killed and looted as normal. Also, I did a full playthrough of all the vanilla storylines without using fast-travel without issue after creating the CTD fix. I will upload the picture from my phone a soon as I can.
Thanks. Do you happen to have the load order you had at that time?
Edit: Thanks for posting the load order. That is quite large... Just to clarify, in the vanilla game the CombatStyle is defined for all 2 Rabbits and 3 Foxes that are on the vanilla leveled lists 0xEC969 and 0xEC96B. Next time this happens check if all the NPC_s on the linked leveled list have the CombatStyle defined. AFAIK setting the style on the base will override it.
Those aren't formids. They're code addresses. https://en.wikipedia.org/wiki/Machine_code You've just mutilated some completely innocent records.
Those are Form IDs. If you don't trust the word of a random stranger on the internet, you can read the source code of Crash Fixes to verify this yourself.
TESCombatStyle form the reference ID 0x105A22 and the base ID 0xFF001529.
Base ID FF001529 doesn't exist in the vanilla game. It doesn't even exist in any mod out there. FF is the index for dynamically created records (essentially your save game). The Base ID of this reference is supposed to be 000EC968. Whatever caused your crashes, it was specific to your save game. Consequently this fix won't work for anyone else.
I don't use the "FF" ID for anything in my fix. I already knew that those are temporary IDs. I used the 0x105a22 ID ignoring the "0x" prefix and searched TES5Edit for "105a22" which pointed me to an NPC spawner which in-turn pointed me to "ec968" (LvlAmbientCreatures). This and its snowy alternative "ec96a"(LvlAmbientCreaturesSnow) is what I edited to stop the CTD events.
That's my point. FF001529 is crashing your game, not 000EC968. Somehow in your save game Ref 105A22, that's supposed to use Base 000EC968, has become a FF001529 (the fox that crashed your game). Editing 000EC968 isn't going to fix this crash because 000EC968 doesn't crash your game. You can spawn 100 instances of 000EC968 and won't experience a CTD.
I strongly suspect this fix is placebo and your crashes stopped because the FF001529's stopped appearing in your game.
In any case, ever since I've made this fix, I haven't had a CTD caused by this bug since and I play a lot of Skyrim rarely using the fast-travel mechanic. I'm currently going through my second full vanilla storylines play-through without issue. Where as before my fix, I could only play for minutes at a time before the CTD. In short, it works for me and apparently many others. Good day.
use this for a while, this make skyrim invaded by fox army. During my travel city to city, I notice the game only spawned fox, all ambient animal creature from other mod not spawned only hand placed animal.
I know, but it only mention rabbit. that's why I said other Mod adding more ambient creatures. well I try without this fix, all back to normal. it seems I have no problem with fox they still spawn without giving a crash & try spawning all kind of fox still no crash. thx btw.
No problem. Try using "Crash Fixes" by "meh21", if you get a CTD accompanied by the Windows error sound, before closing Skyrim roll the mouse cursor over the taskbar looking for another small window showing the error message. It took me a while to even notice it since my previous reaction was to close Skyrim after the crash, not knowing that "Crash Fixes" was trying to show me what caused it.
As an alternative solution to your rabbit problem, have you tried leaving the Template record as is (LCharAnimatedCreatures) and only adding the combat style (csWolf, or even better csHare) to the records?
This may fix your CTD problem without limiting the spawns to only foxes.
I don't have the expertise to know if this is correct - any opinions?
thurderan has pointed out a potential issue with the mod over on Skyrim SE Nexus. The issue lies with rabbits no longer spawning & can cause bandits/mods that add bandits which use the ambient creatures template (Bandit Encounters use this template evidently) to no longer function. Please investigate this further & if at all possible, fix it so I can update the SSE version with a fix to these issues as well. See thurderan's post over on the Skyrim SE Nexus version's mod page for further info.
Thanks, it was an unintended overlooked side-effect. I posted an optional way to remedy this in my sticky post and description for those who miss the rabbits.
I'm testing. Before, I had possible CTD in open sky. Your mod corrected. It worked 100%. But he started giving CTD indoors. I removed your MOD, and CTD in the internor has not yet happened. I will keep the post updated, if it comes again. Thanks
It may be conflicting with some mod. I do not know. I just wanted to let you know that it happened. I installed the mod, started indoor CTD. I removed the MOD, there was no indoor CTD. It's just a record.
I removed the MOD, no inner CTD occurred. Now, I'm going to reinstall your mod. I'll up the loading order. Maybe it's a conflict, maybe with "SkyTEST - Realistic Animals and Predators"?
Took me awhile to figure out that the having any of the Autosaves on in Oldrim and F4 will trigger CTD's. I'm still going to try this mod out on my next play through.
132 comments
Comments locked
The author has locked this comment topic for the time beingI have decided to lock the comments thread because of negativity. If you don't like this fix, then don't download it. But, I use it myself after playing many thousands of hours dealing with the CTD it fixes. If you have never encountered this particular CTD before then don't use my mod. But, if you are suffering from the "TESCombatStyle form" CTD, I can promise you, it works. I've tested it myself before uploading for a complete playthrough without using the fast-travel mechanic without suffering through any more crashes caused by the "TESCombatStyle form" bug.
Thank you and goodnight.
(Edit) Still no CTDs as of October 1st 2018. This "placebo" works.
(Edit) Still no CTDs as of November 17th 2018.
(Edit) Still no CTDs as of January 12th 2019.
(Edit) Still no CTDs as of March 15th 2019.
(Edit) I've since moved on to Skyrim SE, but it all ran fine with no more CTDs involving the "TESCombatStyle" error message.
Anyway, I'm not going to cry about USLEEP abandoning "Oldrim". Frankly, they broke so damned many mods when they did USLEEP (instead of the separate patches for the DLCs) that it's been hard to recover from it. I would much rather deal with individuals intelligently patching bugs as they find them, and if I get near the mod limit do some script or manual merges. It's nice to have big "community project" patches take care of the bulk of the early-discovered problems, but years after the fact we can't much expect anything but people still actually playing the original game to continue to work on patches for it.
It's more or less and updated skyrim missing a lot of mods. Glad i never bothered with it. though i was curious that this mod may have pointed out what has been causing the random world CTDS. but it could have been any number of things. i guess i'll see in time. i mean that's another thing...If this mod is needed on SSE then that means they couldn't even bother to fix that o_O what was the point of it again?
SSE's "exclusive mods" aren't anywhere near enough to make up for the massive missing mods that were on oldrim. SSE will die out long before oldrim comes close to it. but skyrim as a whole is getting older and older. since they are the same game, they may die together, but if not, SE will certainly go first.
and yea, USLEEP is a dead mod now, if they actually did abandon oldrim. which is another example that if that mod is still needed for SSE they didn't fix much..
SacredSage, please tell me how to get the SE godrays/global fog through enb.
i rarely crash in the overworld, but it happens. i'm still concerned about the side effects of this mod though.
Although it would be amusing if it turns out rabbits were causing your crashes all along and by removing rabbits you fixed the crash... amusing but entirely unrelated to the crash fixes error code.
========================
so maybe i shouldn't install this mod? gotta admit, i was kinda leery on what this was doing
Common sense dictates this error message from Crash Fixes would have shown up plenty times before if this is a vanilla problem. So this means something else might have to happen as well. Like a badly sorted load order or another plugin changing something.
The point is to actually understand the cause of problem and then provide a proper explanation and then a fix for it without breaking anything else. All we have so far is just noise because there is no documentation of the problem. Simple troubleshooting starts by making a test case that 100% triggers the problem by always spawning the same problematic critter for example.
Without the proper problem description nobody knows if they have the problem or if the "fix" actually does anything useful. Because as long as the CTD is "random" you don't actually know if it is fixed. Might be just lucky for a long time or something else changed in the meantime.
What i think people are trying to say is that you mistook a code adress given by the crash fixes log for a form id, (which i guess are pretty diferent things) and looked up for the wrong thing in Tesedit, which means that the form ID you searched as nothing to do with the crash fix report. So you are changing a totally unrelated thing to your crash error, which means that, unless you got extremely luck and actually by accident managed to find a form id that was givng you trouble in your load order, this wont actually help. I maybe wrong of course, i'm no expert just basing my thoughts on other peoples opinion here and at skyrimmods reddit.
Edit: Thanks for posting the load order. That is quite large...
Just to clarify, in the vanilla game the CombatStyle is defined for all 2 Rabbits and 3 Foxes that are on the vanilla leveled lists 0xEC969 and 0xEC96B. Next time this happens check if all the NPC_s on the linked leveled list have the CombatStyle defined. AFAIK setting the style on the base will override it.
Those are Form IDs. If you don't trust the word of a random stranger on the internet, you can read the source code of Crash Fixes to verify this yourself.
Base ID FF001529 doesn't exist in the vanilla game. It doesn't even exist in any mod out there. FF is the index for dynamically created records (essentially your save game). The Base ID of this reference is supposed to be 000EC968. Whatever caused your crashes, it was specific to your save game. Consequently this fix won't work for anyone else.
That's my point. FF001529 is crashing your game, not 000EC968. Somehow in your save game Ref 105A22, that's supposed to use Base 000EC968, has become a FF001529 (the fox that crashed your game). Editing 000EC968 isn't going to fix this crash because 000EC968 doesn't crash your game. You can spawn 100 instances of 000EC968 and won't experience a CTD.
I strongly suspect this fix is placebo and your crashes stopped because the FF001529's stopped appearing in your game.
As an alternative solution to your rabbit problem, have you tried leaving the Template record as is (LCharAnimatedCreatures) and only adding the combat style (csWolf, or even better csHare) to the records?
This may fix your CTD problem without limiting the spawns to only foxes.
I don't have the expertise to know if this is correct - any opinions?
Best, BD
Missing "TESCo" mbatStyle form
TESCO :D
=:::(
This one perhaps?
https://www.nexusmods.com/skyrim/mods/82951