Engine Fixes consistently deactivates mods?

[nunyabidnez]

So Engine Fixes used to be pretty much a mandatory part of your mod order back in the day.  I've been out of the loop a while, and just this weekend started going through the nightmare of trying to make AE work, and low and behold now Engine Fixes seems to be the devil?  Every time I activate it, it will invariably cause an immediate CTD and as it takes the game down, it deactivates just about every mod in my mod list.  Is that an issue with anyone else, and if so is there a workaround?  My rig won't run much more than about 3000 animations without it, and it's ridiculously easy to blow past that with animation packs and other mods that introduce animations.  Thanks in advance for any advice.,

[Bastak21]

Try this https://www.nexusmods.com/skyrimspecialedition/mods/108069

[Just Don't]

Update Engine Fixes to the latest version. That optional config file linked above is not necessary nowadays.

[nunyabidnez]

You know what completely fixed the issue?  Me pulling my head out of my ass and using the right version,....   Yup, I'm an idiot who can't read version numbering conventions well.  Who would have thought that .11 would come after .6,.....  Sorry for the dumb question and thank you both, Just Don't and Bastak 21, I do appreciate the responses.

[traison]

19 minutes ago, nunyabidnez said:

I'm an idiot who can't read version numbering conventions

 

In your defence, I find humans in general are very bad at version numbers. For instance:

• Some are affraid of incrementing version numbers to the point where, when they make a revision to (as an example) 1.0.0 they append a letter to it: 1.0.0a; and when they make further adjustments to that, it turns into something even more silly and confusing: 1.0.0a-fixed, 1.0.0a-new, 1.0.0ab.
• Some think that version fields are limited to single digits. They seem to think they've ran out of numbers when they reach 9. When they make a revision of 1.0.9 it turns into 1.1.0 instead of 1.0.10. This causes a revision to incorrectly become a new minor version instead.
• The definition of what constitutes a major version is sort of non-existant, or at least it is rarely followed. You frequently see silly things like MyApplication v1.0 and MyApplication2 v1.0; this is like saying "MyApplication version 2 version 1.0".

Granted, there's many different standards for version numbers and no one is forced to follow any of them. For the most part the only thing that remains similar is the dot notation.

[nunyabidnez]

1 hour ago, traison said:

 

In your defence, I find humans in general are very bad at version numbers. For instance:

• Some are affraid of incrementing version numbers to the point where, when they make a revision to (as an example) 1.0.0 they append a letter to it: 1.0.0a; and when they make further adjustments to that, it turns into something even more silly and confusing: 1.0.0a-fixed, 1.0.0a-new, 1.0.0ab.
• Some think that version fields are limited to single digits. They seem to think they've ran out of numbers when they reach 9. When they make a revision of 1.0.9 it turns into 1.1.0 instead of 1.0.10. This causes a revision to incorrectly become a new minor version instead.
• The definition of what constitutes a major version is sort of non-existant, or at least it is rarely followed. You frequently see silly things like MyApplication v1.0 and MyApplication2 v1.0; this is like saying "MyApplication version 2 version 1.0".

Granted, there's many different standards for version numbers and no one is forced to follow any of them. For the most part the only thing that remains similar is the dot notation.

Full disclosure, I do have some comprehension issues, (dyslexia, ordering issues with numbers, etc), and I've always had problems with crap like that.  I'd love it if developers and modders would standardize their versioning systems, preferably using 0-9 with each version and perhaps a through d or so for interim versions.  So, like in this instance, it wouldn't have been (Part 1) SSE Engine Fixes for 1.6.1170 and newer, but rather (Part 1) SSE Engine Fixes for 1.6.2, as it would have rolled past the .9 into the next series.  I know there are some industry standards, but I don't know what they are personally, and I'm sure they make internal sense for the people with big brains who work with this stuff constantly, but as you said it can get so freakin confusing for knuckleheads like myself.