I've got this problem with my creation kit that developed whilst modding some cells today. Everything was fine until I decided to take a break and exited the creation kit. When I came back and started the cell interiors I got this message.


Assert File: C:\_Skyrim\Code\TESV\BSShader\Shaders\BSLightingShaderProperty.cpp

Line: 806


After that message I couldn't move the view anywhere, and I started in the gray void unlike before. I tried to "fast travel" to an object, but was still stuck in the view.

I tried to search for the file the message box refers to, but it doesn't exists in my disks.

Is this a common bug? Something I can do to fix it?

It's probably a common bug. I always just hit ignore and everything works fine. The file it's reporting is a developer source code file. We obviously won't have those and there'd be little most of us could do about it even if we did.

Thank you for your reply. Hmm, well "ignoring" doesn't work. Same result as before. I wonder if there is a setting I've ruined... something that disallow movement.

Any feed back would be appreciated.

I was getting this error for a while but it wasnt affecting my movement.

Mine was being generated by a mesh I was using that had some problem with the shader settings. I never did figure out exactly what the problem was, just stopped using the mesh.

This being told to ignore errors is very very bad practice to get in the habit of doing, especially since that one click on ignore often hides a number of errors.
I put it right up there on the bad practice list with an OnErrorResume command and if this was being done by the devs while making the game explains why there have been so many problems.

I also have this problem, hitting retry usually makes it work fine for me. When hitting ignore I noticed very odd bright pink rendering in some spots.

We don't really have much choice in the matter when these things can be triggered by vanilla content, and the vanilla files generate TONS more errors than our own work. You either learn to dismiss the errors, or spend all your time answering error prompts and getting nothing done.

This is what the EditorWarnings.txt file is for btw. Correct what you can in your own stuff and let Bethesda decide whether or not they'll fix what's broken on their side. Though I really wish they would if only for our sanity

I have learnt to ignore them all unless it causes some major graphical error or crashes the game.
I just need to remember not to take the practice to work with me. I could make my work life a whole lot easier with a simple Ignore() function.

The Error is a problem with a BSLightingShaderProperty within a .nif and is 100% correctable, if the file drawing this error is a vanilla one I would not worry but if its a modded.nif you should correct the problem, as this error causes game crashes.

Line 806 was a error I popped alot while decoding the EnvironmentMap Material it was dealing with the EnvMap Scale setting being read wrong.

Ah, the error was based on setting the movement to 0 on every line. I fixed it back to something random and just like that everything works again. If anyone would suffer this problem in the future, check /movement under "Render Window Properties".