Usually, I would think that these Geck warning would fall under the category of ignorable. But I am having a small weird issue with a cell and I was wondering if anybody had any idea as to the cause of these particular warnings:






The first comes from a locker that I retextured, but the error seems to come from the nif, which I didn't touch.
The last three come from vanilla objects that I did not touch, so I doubt they are causing any problems.

The problem that I an encountering is that some users are experiencing intermittent CTDs or freezing when the player reaches a certain spot in the cell. My game doesn't have these issues, and both people who reported the issues said it only happened the first day they tested, but not on the second day.

Hmmm interesting. I don't think any of these errors would cause a CTD. The objects referenced in the errors, are any of them close to the spot where the CTDs occur?

Cheers,

Miax

I'm just guessing at this point. Without being able to re-create the CTD/screen freeze myself, its hard to pin down what might be causing it. Since I had a few Geck warnings, I though I would just check. None of the listed objects are directly near the problem location, but my cell did not have any room markers, so the entire cell was getting rendered. I just added some room markers and am going to ask them to test again. There is a trigger near the location that spawns some enemies - that seems a more likely culprit, so I'll disable its script for the new testing phase, just to see. There is also a disabled sentry-bot and a human idle marker within close proximity to the problem area along with 4 of the big enclave doors - that give their own NiControllerSequence warnings that all of these doors give no matter where they are used, so I dismissed these errors as ignorable for this problem.

1) TESModelTextureSwap
Do you have a 'new' NIF file for this object? The unofficial patch has a new locker NIF. If you attach the texture sets to the vanilla version, but you later installed the unofficial patch, it has a new NIF and would use different slots now, thus giving you this error.

2) Unidentified collision
A lot of vanilla objects have this, I would not worry too much.

3) missing a Normal map
The mesh cannot find the normal map that should go with the texture. Or, the normal map was not made correctly and cannot be loaded. There are a number of vanilla objects with this issue. It may also be that no normal map was assigned to the NIF inside the NIF itself.

Thanks everybody for the info. I have decided that these warnings are not the cause of my issues, so this topic is done.