maboru Posted January 14, 2012 Share Posted January 14, 2012 Your welcome. Yes now just reactivate your mods one at a time (activate one then start the game to make sure it still works then quit and go to the next one.) Keep doing this until you find out which mod caused the problem then let us know which one it was. Link to comment Share on other sites More sharing options...
Razor444 Posted January 14, 2012 Author Share Posted January 14, 2012 (edited) Your welcome. Yes now just reactivate your mods one at a time (activate one then start the game to make sure it still works then quit and go to the next one.) Keep doing this until you find out which mod caused the problem then let us know which one it was. But because the loading / bethesda logo in red was specifically caused a Mod? I think No, because until yesterday was alright, it happened when I did the damn guide NVIDIA and the bloody code "uGrid" etc. .... Edited January 14, 2012 by Razor444 Link to comment Share on other sites More sharing options...
maboru Posted January 14, 2012 Share Posted January 14, 2012 Well the only way to know for sure is to check your mods. Sometimes mod conflicts only arise after a previously unexperienced particular combination of factors that bring them into collision. I've never heard heard of uGrids causing loading screen problems but as we go further along in this game we are seeing that some odd things do occur sometimes. The same applies to ini changes although ini problems usually appear soon after the changes are made. It's a continuing learning process for us all! Link to comment Share on other sites More sharing options...
Razor444 Posted January 14, 2012 Author Share Posted January 14, 2012 Then put all the mods that I had before and remains normal, as I said the cause was the code that NVIDIA said in the guide, and made a mess. I only have a small problem I crash very often, like when I leave "Breezehome" etc. ... : ( Link to comment Share on other sites More sharing options...
Recommended Posts