» Wed Jun 20, 2012 9:23 pm
The texture errors seem not to matter (they happen with just skyrim.esm loaded), at least not in my mods. I wouldn't worry about them but that 'bsFixedString' thing is almost certainly mesh-related. In one of my mods, I made respawning Nirnroot and minable Salt using static NIFs assigned to new/custom Tree objects. When I load the modded areas which have these placed in them, it gives me 'bsTreeLOD' whatever.. because the NIFs I assigned don't have the unique LOD data as real trees should. CK doesn't see the data present, so can't render in the window what it thinks it should; but it works fine nevertheless. (except my Nirnroot doesn't glow, but I think that's scripted to the real Nirnroot somehow, not part of the mesh) But the "bs" prefix is havok-related... so almost always will be caused by a NIF.
Back in preCK days, I had a bunch of exposure to crashing GECK (then later, the CK). It was almost always because of corrupt data in a hacked ESP - usually music, weather, and a couple other things... but that's like 4 or 5 months ago now, don't really recall. The data may not have been corrupt per se (for FO3), but Skyrim acknowledged it as such or it was missing data newly implemented in Skyrim. I doubt this is your problem (unless you used non-CK, non-Skyrim specific apps and have been trying to get by without remaking it 100% in the CK).
More recently, I found 'wrong' data in NIF files will cause CTD. In my case, I tried to get custom collision to work (exported out of 3DSMax)... but CTD when trying to load it in-game (or CK). I removed the collision and it works fine. This was attempting to get the 'old' format of rigid bodies with packed strips/shapes/whatev... Skyrim hates that - it only wants havok collision (the compressed MOPP stuff). Although... I DID get convex shapes working.
Another thing which caused strange happenings (possibly CTD in-game for some)... it was the resolution of the DDS files assigned in a NIF. I found it had to be certain increments.. I didn't test to see how far down, but I think 128 or 256 pixel worked. For me though, wrong resolution caused the load-screen to hang indefinately (smoke still animated, but never loads).
I hope something here helps... noone else has any ideas I guess