Do pre-1.8 files need to be re-saved?

Before I was having issues with my followers coming out two-toned with no blush or makeup. Since the CK patch and me deleting the ""tintmasks" folder entirely all I do is now the CTRL-F4 and Presto all my changes are there as intended.

No. They will continue to work just fine. If that wasn't the case, Patch 1.8 would have invalidated every mod that exists during the beta.

Going forward though, any mod saved in CK 1.8.151 will not necessarily work on an older version of the game, but folks who refuse to update are generally doing themselves more harm than good anyway.

I got this sometimes and way before the 1.8 patch. Like 1.5. Didn't bother to mention it though since I thought it was just an isolated issue. Make sure initially disabled isn't checked, even though it should be off by default.

I've never understood this principle that some players have. They are sticking to something like Skyrim 1.3 with a superstitious paranoia and wonder why the mods won't work for them anymore.

Arthmoor postulates that they scapegoat the patches. I compound this with a pseudo-psycho-sociological assessment that, the perception that Bethesda's patches break things began in 1.2. Now, in order to justify their ire, many convince themselves that their gameplay was halcyon prior to patching (it helps the PC-playing community's stance that Bethesda "doesn't care" about them).

By placing the patches (and by extension Bethesda) as the root of all their ills, they justify their perceived disenfranchisemant and find solidarity with the -- how should I put this? -- um, "Morrowind elitists" (hereby defined as the vocal section -- usually, though not always, PC players -- who believe that various efforts to "dumb down" the series are hallmarks of a great decline in quality; with that decline falls their devotion to the series).

Now, being an "elitist" is a positive thing because, by terms such as "casual" and "dumbing down", they have implicitly defined people who play on consoles (ostensibly those who enjoy the games) as idiots -- and no one wants to be thought of as stupid.


Phew.

But I like your word -- "superstitious". Powerful connotation.

For legit users of the game? I have no idea. For not so legit users, I could take a few guesses, but I don't think any of them are forum legal topics

Don't know if it's legit or not, but over on the Nexus forums, there's some folks claiming there's a problem with the new CK and the Dawnstar BSA, and that it's causing the CK to crash. I can't confirm since I haven't got Dawnstar.

Dawnguard.bsa? If so, it's probably ye olden localization crash and their SkyrimEditor.ini files were replaced when the updated CK was installed. All they've to do is add the *desired BSA(s) to their INIs again. If adding that to SkyrimEditorPrefs.ini, the addition will be retained across updates as that file isn't replaced and takes precedence over SkyrimEditor.ini.

[Archive]
sResourceArchiveList2=*

ScriptCompile.bat also gets replaced and will need to be edited (if applicable) as it'll be pointed to a directory most of us don't have (C:\Projects\TESV\...).

Yeah apparantly some peoples ini's get reset (Mine still hasn't. >.>) so anything you fixed via and INI change has been undone. You simply need to redo those changes.

If you want stuff to stick the *Prefs.ini files are the way to go. It's not unheard of for updates to add new INI settings, so I'd rather let the non 'Prefs' files be replaced and keep anything I've personalized elsweyr.

I keep waiting for

[General]
bIs64Bit=1

and

[Display]
bEnableTessellation=1

For storing things elsweyr, I swear by a certain bag of holding.

Thanks for the information regarding the inis. I had wondered what the "prefs" ini files were for and now I know.

Ha! For safe keeping The prefs files rock, overriding the default INIs much like a plugin overrides its master.

The anti-patch thing predates even 1.2. I'd say it goes back to the Day 1 patch, or was it Day 2, that properly enabled the DRM.

Hmm. Did it? Mine is still as I left it.

But here, mine got wiped and briefly told me to take a flying leap into Lake Honrich.

I'm guessing he verified game cache so it re-downloaded the files SKSE replaces and other modified files.

ScriptCompile.bat? Yeah, mine was reverted/replaced and I couldn't compile until replacing it with a backup.

I'm having a problem with my CK since the update. I can no longer add a new mesh to the CK and use it right away. I get a warning message saying that it could not queue the model. I can only use meshes that were present when I loaded up the CK. So now I have to close down and start up the CK everytime I want to add and use a new mesh. I assume that something has been changed in the ini's. Does anyone know how I fix this?

I've been getting that too. After adding the new static (in my case), that error pops up, and the missing mesh indicator shows instead of the static. However you don't have to restart the CK, fortunately; just refresh the render window (F5 key with focus on the render window).

Still, it's pretty annoying and it would be great if there were some way to fix this.

ahh Thanks for that tip. Hopefully that will make things a little less tedious.


Edit: I just went and tried that. That works great! Thanks again.

Don't get why people assumes always that players not wanting to update are suppersticious or didn't own a legal copy (It's common sense to assume that pirated copies will be as updated as the owner want, if a game is pirated why not an update). Keep in mind that not all the users have a new computer. Enb antifreeze was a lifesaver for people owning an old PC, but it stopped being entirelly compatible at some point (I think it was in 1.5)

Until the CK was released, I read carefully the forums before deciding to use a new patch. I was used to Mount & blade, were most patches used to break more than they fix. The best move was to stick to the last stable patch, untill a new stable one was released. I used the same approach with Skyrim untill they release the CK.

I skipped 1.2 and 1.3 and before starting with 1.5 I had 4 CTDs, with little bunch of mods. Now I can't play the game for an entire hour, even without any mod. Didn't botter me much, since I only play the game to test the changes I made with the CK, but my game is simply unplayable. Should I be playing instead of modding, I would stick to 1.4.

In my case it's pretty obvious that my system can barelly run Skyrim and without the aid of Enb antifreeze patch I'm simply modding for others. I'm not complainning, I really enjoy modding, but I can easilly understand people not wanting to update.

Yes, but at least you understand why you're doing it, and hopefully realize that by sticking with 1.4 you will not be able to use anything made for the game from 1.6 onward.

The problem is that the vast majority of people doing this have no idea why they're not updating, they just seem to oppose the very idea of needing to and will resist it irrationally. the resulting nightmare of mod support that causes is a big problem.

Truth to be told, given Bethesda's history of occasionally causing pretty big issues with their patches, ranging from introducing new modding nightmare to the VATs bug, and adding in the normal delays for script extenders and the sort to get updated, its pretty damn smart to be "superstitious" for a few weeks. I often patch early and end up regretting not waiting for Script Dragon and such. That much seems reasonable.

IIRC the 1.4 patch was the worse patch of them all and screwed up the game pretty badly. If you want stable but no more updates, 1.5 is the way to go.

I'm not sticking to 1.4. I couldn't mod should I do it. I'm simply not playing the game.

You have a point about the problems derived for modders from this. We are having a problem with this in 'Vilja in Skyrim'. Various users reported a problem that could only mean the the esp is not reading the BSA.

Eend, one of the betatesters, tracked it as being caused by non updated games (we are sure it happens with 1.1 and it didn't with 1.6, not sure about intermediate patches). Can't blame those users though.

If their computer is as crappy as mine, they simply can't play the game past 1.5.
1.4 was the best patch. It fixed all the problems from 1.2 and 1.3, while includding things like increassed memory allowance and improved compilation. It was as stable as 1.1, but with various improvements.

1.5 bring more kill moves and mounted combat (or that was in 1.6?), along incompatibility with ENB (some users claimed also a lost in stability and performance, but it could be just because ENB antifreeze no longer working propperly).