SureAI

This might've been an issue with someone else a while ago, but I couldn't find it and I couldn't find an FAQ either, so here I am.

I followed the read-me for installation in Steam and such exactly and when I began my game, I had weird little yellow boxes showing up everywhere in game.. I'm guessing these boxes are triggers or where textures are supposed to be or something, but they really do take away from the atmosphere of the dark, ominous looking cave in the beginning, so I'd like to not see them anymore. ;P

Any suggestions are welcome. I didn't fool around with it much 'cause I'm not exactly sure what could possibly fix this.

Did you activate the NehrimData.esp in the Launcher? To run Nehrim properly, you need to active the Nehrim.esm and the NehrimData.esp

Yes, I have only Nehrim.esm, NehrimData.esp, and NehrimEnglish.esp checked. Everything else, including Oblivion.esm, is disabled.

I missed this thread yesterday when I searched, but yeah, same thing is happening to me.

Should be a graphic setting problem.

1) Configure your video settings in Oblivion, and run the original game once.

2) Then go back to the Nehrim launcher, and try different video settings. (Lower textures quality, set the RAM use to 1024, decrease the anti-aliasing...). Worth a try... I can't assure you it'll work. Though most of the freezes, crashes, or video glitches I got were solved using the right video settings.

If it is a video setting, I can't figure it out. I have tried everything.

The same thing is happening to me, I have tried all graphics options as well.

This is NOT a video problem. It is a problem with Nehrim being unable to locate some of the necessary data files. This might be due to different reasons, like:
- Steam has "updated" your Nehrim back to a vanilla Oblivion (this happens if auto-update is active in Steam);
- you have installed your Oblivion or your Nehrim in a folder (like C:\Program Files (x86)) which requires admin privileges to write in;
- you have moved your Oblivion folder without changing the corresponding path in the registry.
Do you recognize any of these things as the culprit?