Given this pullback and the errors loading the .91 saved files, I think it is safe to say that a change occurred to the BipedObject class (inside Race and Armor) in Skyrim 1.6.91. The CK was saving files with that new schema which 1.6.89 couldn't understand. So we'll clearly need that CK update to 1.6.91 when (if) Skyrim 1.6.91 becomes the official PC patch.
Yes, you were right all along, as you can see http://www.gamesas.com/topic/1381788-the-new-unofficial-creation-kit-bug-list/page__view__findpost__p__20985902.
This doesn't surprise me (other than the mistake of releasing the incorrect CK - perhaps that is because the 360 build was released at 1.6.91 so there was a little confusion.) What this means is the BGS team continue to make memory and performance improvements. We'll have to have a lot of due diligence on the SKSE side with the next build, as a bunch of our actor/armor functions may be broken because of the shrinking of the BipedObject class. Well at least we know to keep our eyes out for those changes and not release until a more serious set of tests have been performed.
behippo, In your experience,do you think those of us that have saved out a mod in 1.6.91 should (I know we can) be loading it up in 1.6.89, fixing the biped info and saving it back out? I know it WORKS but to what extend unknown damage could have been done is .. well... unknown?
So, they included a newer version of the CK than they should have, right?
P.D: Armor and Race bugs seems fixed, what about vanilla dialogue?
Armor is fixed? Do we just need to save our esp/esm in the 89 CK or must we manually reassign all the biped slots? (Arthmoor said he tried and it didn't fix it, I think)
And the dialogue broke with the Skyrim 89 patch, not the CK patch, so I doubt a CK patch would fix it...
I see a problem with the downgrade. All mods changed by the previous (next?) version of the CK will continue having those bugs. So, no joy for people experiencing them again. Especially since this coulnd mean the needed update 1.6.91 could not happen for some time.
I think it would be better to go to a pre-1.6.91 save and work from there. Hopefully everyone still has access to that build. However it should be pretty safe. Think of it this way, the .esp is saved out in its entirety each time. The 1.6.89 CK doesn't know about the new BOD2 storage type, only the BODT storage type. So when it goes to save out the biped model information it saves out BODT and the game is happy.
The danger is that when you loaf the 1.6.91 .esp into CK 1.5.89 it won't find the information in the new field and therefore some of your data will go missing. Who knows what other classes (if any) might have the same issue. So while it would probably work, it would be much safer to go back to a 1.5.26 CK build than to use one from 1.6.91.
Edit: Note that this is reasoned speculation on my part. My day job has similar data migration issues, so I am familiar with the circumstances. But the code is different and I haven't tested this at all.
This doesn't surprise me (other than the mistake of releasing the incorrect CK - perhaps that is because the 360 build was released at 1.6.91 so there was a little confusion.) What this means is the BGS team continue to make memory and performance improvements. We'll have to have a lot of due diligence on the SKSE side with the next build, as a bunch of our actor/armor functions may be broken because of the shrinking of the BipedObject class. Well at least we know to keep our eyes out for those changes and not release until a more serious set of tests have been performed.
Sorry, that came from the link Inki gave above regarding the changes. The BipedObject class shrunk in size and the data type saving the slot for the armor/race was changed. A bunch of the changes in Skyrim 1.6 came from this sort of change to reduce the memory overhead of the game and improve performance. Removing 2 or 4 bytes from a class doesn't seem like much, but when there are thousands of instances of that class it makes a big impact. The less memory needed the better the game will perform.
Armor is fixed? Do we just need to save our esp/esm in the 89 CK or must we manually reassign all the biped slots? (Arthmoor said he tried and it didn't fix it, I think)
I haven't tried that, had no reason to. I took a 1.5.24 copy of the USKP and saved it in 1.6.89 and noted the armor and race stuff was working properly. The 1.6.91 copy I touched got tossed out as soon as it was broken.
Sorry, that came from the link Inki gave above regarding the changes. The BipedObject class shrunk in size and the data type saving the slot for the armor/race was changed. A bunch of the changes in Skyrim 1.6 came from this sort of change to reduce the memory overhead of the game and improve performance. Removing 2 or 4 bytes from a class doesn't seem like much, but when there are thousands of instances of that class it makes a big impact. The less memory needed the better the game will perform.
So armor slots will not be shrinked? (that's what I feared).
Alright my random save from the 13th seems to be okay. Luckily all I lost was a few hours I spent getting some books into the CK. I can just load up my corrupted save, copy+paste into word, then paste back into the CK.
So armor slots will not be shrinked? (that's what I feared).
I haven't seen the change but no one reported having fewer slots listed in the .91 CK - though perhaps no one looked. So my guess is that the same number of slots are there, they've just compacted the data in the class down to the smallest size that was needed.
If you can I would strongly suggest that. If you can't you take the risk of some data being lost and perhaps not knowing it.
I have done a lot of work using the newest CK, and really don't wanna go back to an old backup from before the new version...
So I've been trying to understand this discussion.. a mod edited with the highest version CK (which causes armor, custom-skinned creatures, etc go invisible) will keep having those issues until Skyrim the Game is eventually (and hopefully) updated to that same version?
So right after I fully finished balancing 98% of the 300+ weapons in my mod yesterday, a ninja update of the CK causes my entire mod to become invalid? Awesome!
I may have missed something crucial, but why is the discussion continuing in this thread, which is named after the erroneously released CK version (1.6.91), that was pulled? Even the thread title is factually incorrect and misleading.
And whatever happened to the thread about the Creation Kit that we actually have (1.6.89)?
Does it mean, that somebody with influence has inside information, that 1.6.91 is really just around the corner for both the game and the Creation Kit?