Some more testing. I load up the mod in the pre 1.6 CK and the biped options for 1st person are unselected. loaded into 1.6 CK and they are selected. Back to pre 1.6 CK and I can select them, save out the mod and it appears to fix the 1st person view problem, but no idea if this is safe. Seems ok.

May I request that this one be added as well, please:

Once again this is true, so at least there I wasn't mistaken.

I made a simple 1-record test mod and looked at it with a hex-editor to see what happens, and it clearly is not a question of compression. Rather, it seems that within an ARMO record, there now is a shorter (by 4 bytes) BOD2 subrecord where there used to be a longer BODT subrecord, and the flag that was unknown to TESVSnip is probably something else altogether. If I recall correctly, this is along the lines of what behippo thought might be the case.

So, it would appear that CK 1.6.91 is simply more advanced than Skyrim 1.6.89. I assume that when the game engine meets the new BOD2 subrecord, it simply decides that it has had enough, and skips the remaining data.

So a schema change. I wonder why they didn't update the game to match the CK?

Maybe the CK was already in the Steam approval pipeline ahead of a Skyrim update? Poor timing? Just speculations at this point.

To follow up on Inki comment on Armo where it is now (have checked in mod did and has changed to below):

For an ARMO record, TEVSnip shows:
Flags 1: 00000004
(Unknown (4))

after 1.6 save ... prior to that the Flag 1 is 00000000, in all my backups done under previous versions of CK, so is possible that the ARMO records are being flag'd incorrectly. Snip could change easily but who knows what that might break at this date, so might try Hex Editor Nero and do some find/Replace and see what happens

Any chance of an unofficial bugfix?

That one isn't fixed, but could use a refined description. Only the "water height" and the three "linear velocity" settings get lost. Everything else is retained.

This was explained further down in the thread as an intentional feature, thus not a bug.

This is a game-side engine but that was fixed in a previous patch.

CK just updated (downgraded?) to 1.6.89.0, version now matches the game version. Time to do a full recheck.

• http://www.gamesas.com/topic/1381788-the-new-unofficial-creation-kit-bug-list/page__view__findpost__p__20977559
  
• http://www.gamesas.com/topic/1381788-the-new-unofficial-creation-kit-bug-list/page__view__findpost__p__20978594

With the downgrade to 1.6.89, these two bugs are gone.

And vanilla dialogue?

Yup. Confirmed race fix. Might need to rehook the biped info back up if you saved out in 1.6.91.

Small addition: If someone saved the game with the higher CK-version and don't have a clean backup version, so there isn't everything lost. But all armors, which were modified, has now complete empty (non-tagged) biped obects. So you have to go in every armor object and set the biped objects to normal. Then it works and no one has to be naked anymore

Still borked. All I can tell you is that the devs are looking into it.

Well, that's something...do you think it'll take long? And will you update the interim USKP version to reflect the .89 fixes?

No idea on the timeframe for the dialogue issue. I'm in the process of updating the interim USKP release now.

Bug list updated.

As the race and armor bugs were not in fact bugs with the editor, but rather caused due to the CK being a later version than the patch itself, I have removed them from the list altogether.


Sorry, but that's a game-side issue. Player-enchanted items are saved within the save file, and save files are not affected by and cannot be modified by the CK. Neither can one create a papyrus script that allows the manipulation of such items.

That's a relief, at least.

Fixed at some point.

Reporting again because this one was due to user error and not an actual bug.


These two are actually the same bug, sadly not fixed yet though.

As of CK 1.6.89, I think this one is safe to drop as the initial batch of errors has been reduced to almost a single screen in a text editor. I doubt very much every possible error source will ever be removed, but it's easy to spot stuff caused by your own mod now.

Appears to be fixed. The camera is sticking to the point of the last object to be deleted, and I just axed most of a dungeon testing this one.

Appears to be fixed as well, sorting in either direction on the landscape editing window displays all available texture choices.

Fixed at some point, column headers have been maintaining their widths for as long as I can remember. Perhaps 1.5.24 got this one.

I'm a boob and didn't realize that was solved via the "general subtitles" option at the time.

Appears to have been fixed, assuming I'm looking in the right place.

Can you add the fact that tree LOD is not correctly generated for cells outside of a 64x64 area? For example, trees in cell (0, 32) will generate properly, but trees in (0, 33) will not. http://i993.photobucket.com/albums/af55/EljhHck/TreeProblem.jpg I made of what I'm talking about. It's a pretty large issue holding back the true potential of any large world mod.

EDIT: On a related note, I can confirm that the Creation Kit now properly generates Object LOD Textures. Previously, it would cap out at a 1024x1024 file, pushing the remaining "overflow" textures into a second atlas_out texture, but it now adjusts the size of the generated texture as needed. The Creation Kit just produced a 2048x1024 file for me with correct UV mapping.

Fair enough, though a couple of points:

• There appear to be other issues in the list that look like game-side issues, such as the small scale havok bug. It's unclear to me what the dividing line is between features offered by the CK and not handled correctly by the game. The navmesh bug falls into this category too, imho, since it took a game-side fix to finally repair it.
  
• The non-working EquipItem means that any equipment-set-switching mods (among other things) are likely to be significantly reduced in utility. If not a bug, this is a missing feature in the CK.

Anyhow, I don't mean to harp on about this, but I am a little frustrated that there seem to have been only two of us on this forum who have acknowledged that this problem exists. It makes it far less likely that it will be addressed by Bethesda, if at all. Do any of you know a place where issues like this one (grey area between CK and engine) are being tracked? Apologies if I've missed something obvious.

A long-standing bug that annoys me (if no one else) is the fact that you can't remove an NPC's additional head parts (scars, that stuff) even if you have just added them.

are the races bugs still present?

Don't think so, it was caused by Skyrim and the CK using different records. Now that the version is the same it shouldn't happen. Anyway, files with this problem won't be corrected (which would happen should skyrim had been upgraded instead of CK being downgraded).

that one ok, what about the other race bugs, like being unable to duplicate one? I wonder if they hve been fixed,