ma1025

Delete "workshop.swf" in your Interface folder if you have it.

Did you install just the Wrapper > d3d11.dll from ENB, then all other files from Tsar Bomba afterwards? Using http://www.nexusmods.com/fallout4/mods/5347/? should delete at least the majority of ENB for you so you can try again.

I had this problem. The game wouldn't even launch, then removing my Fallout4.ini files worked but I couldn't play. I had to delete Fallout4.exe and Fallout4Launcher.exe and let Steam redownload them. Then my old .ini files worked again and everything was back to normal. Apparently Steam didn't update my .exe files or something when it updated the first time.

https://www.youtube.com/watch?v=FgE92aOBuWk You'll probably wanna watch that on the highest quality you can. Honestly, I didn't notice a difference except for the deathclaw AI process stopping when I got the minigun really going with more of the scene in view. That might be because of some .ini entries accounting for double the RAM, but I don't know for sure. This was also recorded with my ENB and ReShade enabled and I still didn't notice any kind of stuttering with weapon fire or debris. If annotations are disabled for you, the first segment is with 16GBs RAM and the seconds is 8GB.

Intel i7-4770K Haswell CPU G.Skill Ripjaws X Series 16GB RAMAsus Z87-A LGA 1150 Intel Z87 motherboardEVGA GeForce GTX 770 2GB SuperClocked GPU

I've been using the debris effects since they were released and I can't say I've noticed any issue like that. I'm using an EVGA GTX 770 SC.

You can use "player.removeperk 001d2495" to remove rank 2 of Night Person. If that removes rank 1 as well, you can use "player.addperk 0004c93b" to add rank 1 back.

Do you have rank 2 of Night Person? That activates a nightvision effect when sneaking inside buildings at all hours and outside at night.

What is your load order and what kind of armor are you wearing? It's definitely some IMOD that keeps playing for whatever reason when you stealth. i thought it might be the chameleon armor effect but it's different. I made a batch file for someone a few weeks ago that clears all IMODs currently running, though if this keeps happening to you then someone keeps calling the effect. http://www.nexusmods.com/fallout4/mods/9852? It might help you in the meantime while you try to figure out the cause though.

You can totally turn off IMODs with "sisme 0" in the console, but it will disable every screen effect (fade to black, crippled head, night vision, etc) sisme 1 will turn them back on.

A couple of people said their pipe weapons have turned invisible with Pipe Guns Plus. http://forums.nexusmods.com/index.php?/topic/3524395-pipe-guns-plus/?p=32901265 I don't know what PipeGunRedux is since I can't find it anywhere but I'd say either that or PGP (or a combination of both) would be the most likely culprits.

I'm glad the batch file took care of it. Stuck imagespace modifiers are a common but easily fixed problem. There won't be anything permanently affected by using the rimod command. All it does is clear the current effect - in the case of my batch file, all of them at once - but it doesn't disable them completely. For example, looking through a scope with night vision loads an imagespace modifier to give it the bright green look. If you used my batch file while you're looking through it, the effect will disappear. However, when you lower the gun and then look through the scope again, the effect returns. IMOD effects will return normally when the game calls on them again.

Try disabling DoF. http://www.nexusmods.com/fallout4/mods/4172/?

Well, I see it's not working again. Okay, what are your system specs? In the meantime, in the console, type "sisme 0" That will completely disable all IMODs. (using sisme 1 will turn them back on) That will tell you definitively if it's because of an IMOD or not.

Yeah, just put the imod.txt file into the Fallout 4 folder. You don't add it to any other files. EDIT: I just saw that it's working for you again (for some reason, lol). Glad you can see again, at least.

The folder you put the file in is "Program Files (x86)>Steam>steamapps>common>Fallout 4" It should be the same folder that has Fallout 4.exe and Fallout4Launcher.exe. Just dump the .txt file there. When you're in-game and you type "bat imod" into the console, you should see a bunch of "rimod" commands appear in the console, like this: rimod 00000162; rimod 00000164; rimod 00000166; rimod 0001928B; rimod 0001ED7C; rimod 0001ED7D; rimod 0001F5AD; rimod 0001F60F; rimod 00021184; rimod 0002119C; rimod 0002458E; If you see that, the file launched the commands properly. Make sure you're typing it without the quotations. Just bat imod.

I saw another topic a few weeks ago where version 1.9 of Scrap Everything did this to someone's game. http://forums.nexusmods.com/index.php?/topic/3712160-weird-visual-lighting-glitch/ Reverting back to 1.8 fixed it for them, although SE has a 1.91 version that apparently fixes this issue.

Dynamic DoF has the camera keep in focus whatever your cursor is pointing at. Since your cursor is pointing past your character, you're out of focus. The DoF for Fallout 4's ENB is a really early build so it's not quite up to par with Skyrim's right now. I don't play in third person myself but you can try this mod (and maybe this one too) to see if it helps.

You mean something like Realistic Death Physics? I use it myself and I haven't had any suborbital deaths.

https://www.youtube.com/watch?v=BLba9gNiTKE Okay, see if this guy's video helps you; he's got it written out in the description. Make sure you're in third person when you do it and it might have similar results. I've also looked on the Skyrim forum (since it's the same engine) and other people that have had this problem either installed some animation mods that weren't working right or said that sprinting and instantly stopping have fixed their problem.

Have you altered the third person FOV somehow? Try setting it back to 70. I think it's the fDefaultWorldFOV= in Fallout4.ini/Fallout4Custom.ini although if it's in the Prefs files, then change it there too I guess.

It might be this: http://forums.nexusmods.com/index.php?/topic/3781395-graphical-glitch-that-makes-my-game-unplayable/?p=34473765 Seems like a lot of people are getting it.

Try using this file I typed up. http://www.nexusmods.com/fallout4/mods/9852/? Place it in your main Fallout 4 folder - where Fallout4.exe is located - then load your save file and open the console. Type: bat imod And see if that gets rid of your onscreen effect.

Well in that case, it seems like it's an Imagespace Adapter that's gotten stuck somehow (like the rifle scope problem, but from another source). Is there any way you can record a short video of it using something like FRAPS?

Are you using some kind of shader like ENB or SweetFX/ReShade? Try disabling them to see if they're causing problems. It's usually Shift+F12 for ENB and Scroll Lock for the other two.