There has to be another mod messing with it somewhere. If you aren't running vb 4.1.2, as you have stated, then you would have gotten the error and that should have been it. Others have made the same mistake of installing the 4.1.2 version on pre-4.1.2 vb and have not shown the symptoms that you have had. I did it myself to see if I could duplicate it, but nothing stuck. My advice would be to disable one mod at a time to see if that clears it up.
|