* Problem: After I load a savegame, a message box tells me that Project Nevada wasn't properly installed. Again, two things that can cause this:
1. Project Nevada wasn't properly installed... If you did a manual install and forgot to follow step 3 in the guide above, this is what happens. To fix it, install Project Nevada properly as described in Section 3.
2. If this problem suddenly occurs when you were already running Project Nevada successfully, this means some other mod overwrote an interface file. With FOMM, this should be fixed by simply deactivating Project and then activating it again. If you don't use FOMM then this is where things will get complicated. First you have to find out which other mod causes the conflicts, then with that specific information you can ask for help in the comments.
* Problem: After I installed Project Nevada, my game is lagging/stuttering more than usual. Even though we tried to optimize our scripts as good as possible, they can still cause considerable strain especially if your computer barely meets the minimum system requirements for Fallout: New Vegas. You should try out the New Vegas Stutter Remover, in most cases it will will significantly increase performance. If that doesn't help, try deactivating some of the features, for example the crosshair recoil or visor overlays.
* Problem: Since I installed Project Nevada, my game is very unstable and crashes all the time! Personally, I've been playing with Project Nevada for over 20 hours without a single crash. Same goes for our other testers. So currently the mod is not known to cause any instabilities. The problem is most likely somewhere else.
* Problem: After I installed Project Nevada MANUALLY, another interface-related mod is no longer working. Unfortunately, when doing a MANUAL installation this can't be avoided. Either the last installed UI mod automatically overwrites files of all previous ones, or installation will become very complex for the user. We chose the former. If you can't fix the problem yourself by editing the XML files, the solution is simple - just use the FOMM installer, it should automatically resolve any conflicts.