My screen goes black and there's odd sounds

[darkoraclegirl]

Ok I recently starting playing FO:NV again after getting a new computer and I install the NMM and some mods and started playing. Was having a great time until I got to the New Vegas strip. When I am outside the walls of the stripe and freeside I notice my screen will lose all hub stuff( compass, ammo, etc), the cross-hair will disappear, and there would be these weird sounds (one being like cloth rustling, another being this almost bang sound) then the hub stuff would reappear before it would repeat again (sometimes I get a second of picture before everything goes dark again). If I leave the area around the stripe/freeside the problem goes away, but if I go back I either have to move really fast to get inside a building or Freeside or fast travel away from the stripe.

 

I have uninstalled all mods and tried it only for the problem to continue. So it doesn't appear to be a mod problem. If anyone can explain this to me as well as how to fix it I would be very grateful.

 

Also I am having a problem with my character moving like the Flash for no reason. At the start of the game when I'm with the Doc I move normal but the second I leave his house I start moving so fast that even at normal speed I fly slightly when there's a dip in the road. How do I fix this?

[dubiousintent]

Uninstalling may not restore vanilla files. (It depends upon your mod manager and if the original vanilla files are available to it.) In which case you may need to have Steam "verify files" (it will always restore at least one), or even delete and reinstall completely. But before you do that, try renaming both the INI files in the "C:\Users\<YourAccountName>\Documents\My Games\FalloutNV" folder, and let the game rebuild them. It's simpler and often resolves similar problems.

 

Troubleshooting is a logical process of elimination. If all logic fails, you have to revert back to a vanilla game and slowly re-install mods, testing each one thoroughly before adding the next. It is a trade-off of "time" versus "effort". Where that tipping point lies is up to you. This is why you are always advised to follow a slow "install and test each mod one at a time" procedure when first setting up your game. Then you know specifically which mod is causing your problem, which saves time.

If you want a stable game, don't make any changes to your setup once you start playing and making "save game" files. Even updates to current mods run the risk of making things unstable after the point they are added. If you do update, ensure you know which save to revert to prior to that update if it goes wrong.

Removing a mod that has stored some elements in a "save file" will leave residue (even with a "clean save") that can cause problems down the road. It's better to find out what causes problems before you start to play in earnest.

-Dubious-

Edited May 16, 2016 by dubiousintent

[darkoraclegirl]

Uninstalling may not restore vanilla files. (It depends upon your mod manager and if the original vanilla files are available to it.) In which case you may need to have Steam "verify files" (it will always restore at least one), or even delete and reinstall completely. But before you do that, try renaming both the INI files in the "C:\Users\<YourAccountName>\Documents\My Games\FalloutNV" folder, and let the game rebuild them. It's simpler and often resolves similar problems.

 

Troubleshooting is a logical process of elimination. If all logic fails, you have to revert back to a vanilla game and slowly re-install mods, testing each one thoroughly before adding the next. It is a trade-off of "time" versus "effort". Where that tipping point lies is up to you. This is why you are always advised to follow a slow "install and test each mod one at a time" procedure when first setting up your game. Then you know specifically which mod is causing your problem, which saves time.

 

If you want a stable game, don't make any changes to your setup once you start playing and making "save game" files. Even updates to current mods run the risk of making things unstable after the point they are added. If you do update, ensure you know which save to revert to prior to that update if it goes wrong.

 

Removing a mod that has stored some elements in a "save file" will leave residue (even with a "clean save") that can cause problems down the road. It's better to find out what causes problems before you start to play in earnest.

 

-Dubious-

I only understood a small part of all that. Pretty must just the uninstall section. But I will try to follow your instructions and hopefully fix the problem. Thank you.

[darkoraclegirl]

Uninstalling may not restore vanilla files. (It depends upon your mod manager and if the original vanilla files are available to it.) In which case you may need to have Steam "verify files" (it will always restore at least one), or even delete and reinstall completely. But before you do that, try renaming both the INI files in the "C:\Users\<YourAccountName>\Documents\My Games\FalloutNV" folder, and let the game rebuild them. It's simpler and often resolves similar problems.

 

Troubleshooting is a logical process of elimination. If all logic fails, you have to revert back to a vanilla game and slowly re-install mods, testing each one thoroughly before adding the next. It is a trade-off of "time" versus "effort". Where that tipping point lies is up to you. This is why you are always advised to follow a slow "install and test each mod one at a time" procedure when first setting up your game. Then you know specifically which mod is causing your problem, which saves time.

 

If you want a stable game, don't make any changes to your setup once you start playing and making "save game" files. Even updates to current mods run the risk of making things unstable after the point they are added. If you do update, ensure you know which save to revert to prior to that update if it goes wrong.

 

Removing a mod that has stored some elements in a "save file" will leave residue (even with a "clean save") that can cause problems down the road. It's better to find out what causes problems before you start to play in earnest.

 

-Dubious-

I have done as you suggested and still get the same problem I'm afraid. Do you have another idea as to what I may need to do in order to fix it?

[dubiousintent]

Still getting the black screen and the HUD disappearing and then reappearing? That's really strange. Let's see if we can't pin it down more closely.

 

First we need to see if this problem still happens when you are running a strictly "vanilla" game with only official DLC added.

 

* Did you uninstall all mods, rename your INI files and then have Steam "verify" files OR delete your FNV game install folder and the FNV folder under the"C:\Users\<YourAccountName>\Documents\My Games\FalloutNV", and re-install the game from Steam? If so, which method did you use?

 

* Did you install to the Steam default location ("C:\Program Files")? If so, see the article "Installing Games on Windows Vista+" in my signature, and move it to a different folder such as "C:\Games".

 

* Did you then try the game as "vanilla" without any mods installed and still get the same problem? (You can Toggle God Mode {that is in the game tap the <~> key to enable "console mode" and type "tgm" (without the quotes) and hit the <Enter> key, then tap the <~> key again to exit console mode} and then run up to The Strip to test.) If so, what are your hardware specs (CPU, RAM, Audio and Graphics cards, and brand of mouse) and which version of Windows (and is it 32 or 64-bit) are you running?

 

* Are you using an ENB preset or SweetFX? If so, check the game graphic & ENB/SweetFX options do not conflict with video driver settings. (Anti-aliasing, ambient occlusion, anisotropic sample size, v-sync, anything else that is mentioned.) Those "enhancements" make changes to the INI files and the game's graphic environment.

If everything works fine in straight vanilla, then it is definitely a mod conflict. Let us know and we can point you to some guidelines that will help with that.

 

-Dubious-

Edited May 24, 2016 by dubiousintent

[darkoraclegirl]

Still getting the black screen and the HUD disappearing and then reappearing? That's really strange. Let's see if we can't pin it down more closely.

 

First we need to see if this problem still happens when you are running a strictly "vanilla" game with only official DLC added.

 

* Did you uninstall all mods, rename your INI files and then have Steam "verify" files OR delete your FNV game install folder and the FNV folder under the"C:\Users\<YourAccountName>\Documents\My Games\FalloutNV", and re-install the game from Steam? If so, which method did you use?

 

* Did you install to the Steam default location ("C:\Program Files")? If so, see the article "Installing Games on Windows Vista+" in my signature, and move it to a different folder such as "C:\Games".

 

* Did you then try the game as "vanilla" without any mods installed and still get the same problem? (You can Toggle God Mode {that is in the game tap the <~> key to enable "console mode" and type "tgm" (without the quotes) and hit the <Enter> key, then tap the <~> key again to exit console mode} and then run up to The Strip to test.) If so, what are your hardware specs (CPU, RAM, Audio and Graphics cards, and brand of mouse) and which version of Windows (and is it 32 or 64-bit) are you running?

 

* Are you using an ENB preset or SweetFX? If so, check the game graphic & ENB/SweetFX options do not conflict with video driver settings. (Anti-aliasing, ambient occlusion, anisotropic sample size, v-sync, anything else that is mentioned.) Those "enhancements" make changes to the INI files and the game's graphic environment.

 

If everything works fine in straight vanilla, then it is definitely a mod conflict. Let us know and we can point you to some guidelines that will help with that.

 

-Dubious-

I've no idea what you mean by ENB or SweetFX.

[dubiousintent]

Then you aren't using them, so that's fine. (They are "post processing" shader effects to enhance the graphic feel of the game as the cost of some processing power and "frames per second" (FPS). Their installation can make changes to the INI files in your "User" account folder.)

 

I would suggest you skip them for the time being, until you get a stable game going. If your average FPS is below 30, any post process shader is going to be a massive hit according to this thread. Only if you are then still interested, the following may be helpful.

 

ENB is found here.

SweetFX is found here.

 

They are two different approaches to the same issue and can be used together if your system can handle the load. (Though likely you will have to learn the configuration settings to deal with potential conflicts between them. They are considered generally complementary.)

 

And then there are various "presets" available for download from the Nexus, which are specific configurations by users to produce specific graphic atmospheres. The general subject of "ENB" is covered here and "SweetFX" here.

 

-Dubious-

Edited May 27, 2016 by dubiousintent

[darkoraclegirl]

Then you aren't using them, so that's fine. (They are "post processing" shader effects to enhance the graphic feel of the game as the cost of some processing power and "frames per second" (FPS). Their installation can make changes to the INI files in your "User" account folder.)

 

I would suggest you skip them for the time being, until you get a stable game going. If your average FPS is below 30, any post process shader is going to be a massive hit according to this thread. Only if you are then still interested, the following may be helpful.

 

ENB is found here.

SweetFX is found here.

 

They are two different approaches to the same issue and can be used together if your system can handle the load. (Though likely you will have to learn the configuration settings to deal with potential conflicts between them. They are considered generally complementary.)

 

And then there are various "presets" available for download from the Nexus, which are specific configurations by users to produce specific graphic atmospheres. The general subject of "ENB" is covered here and "SweetFX" here.

 

-Dubious-

Great news. I finally found the cause of the problem. It was that Silent Hill BETA mod I had. The one thing I kept forgetting to remove. And my speed issues was a hub rebalancing mod. Thanks for trying to help me and putting up with my lack of tech knowledge.

[dubiousintent]

I'm so pleased you fixed it! Often times conflict isolation is the only way that works. Betas are automatically suspect, simply because they have not been stress tested enough until they get into the hands of the players (like yourself). Do let the author know about your problem.

 

But I'm curious: what is "a hub rebalancing mod"? Never heard of that one.

 

-Dubious-

[darkoraclegirl]

I'm so pleased you fixed it! Often times conflict isolation is the only way that works. Betas are automatically suspect, simply because they have not been stress tested enough until they get into the hands of the players (like yourself). Do let the author know about your problem.

 

But I'm curious: what is "a hub rebalancing mod"? Never heard of that one.

 

-Dubious-

I will. Hopefully they still check in on here.