No. None. Ever. Not a single, solitary one. From the CC or Nexus or the workshop. 100% Vanilla.

UPDATE: So I "updated" my graphics driver because there was a new one dated just a couple of days ago (25 Feb or 26 Feb my dam memory is unsure which now). And I played for about an hour and the tearing was much better.... but still there. What I mean by much better is it only occurred about three times in that hour and then only lasted a few seconds whereas all day long it was happening nearly all the time. As I said in a post above, it was basically unplayable.

I have no idea why the same graphics driver that was working fine for literally months (the old driver was dated Dec 2017) with NO tearing issues all of sudden, on the same day as an OS update AND it turns out an F4 update, has serious tearing issues. But no one will ever convince me without hard evidence it was a coincidence (i.e. it was the fault of the graphics driver). I will, until I see evidence otherwise, believe that one of those two updates "did something" that caused my troubles..... most especially because every damned time Win10 updates I get new issues with old games.

I'm sure I'm exaggerating with the "every time" part because WIndows does update quite often (at least once a month doesn't it???) but I guess what I'm saying is this: Over the past year I've had several times issues with old games that worked perfectly fine all of sudden out of the blue have problems. And every single one of those several times it was associated with an OS (Win 10 64-bit) update.

what video card are you running? I can't remeber.... go into the control panel and set Vsync to application controlled.\
Then in game settings Turn off Vsync, try that.
if it doesn't help try these:
fallout 4 fixes

One benefit of playing old games is they don't get constant updates that may mess up things, so once(if) you get it running, you are good.

Might I suggest Fedora, Arch or something more upstream than Debian?

I haven't trusted Microsoft for years. I install XP (SP2/SP3) or W7(SP1) and turn off automatic updates immediately.

Something like a year or two ago i said if my drive(s) failed i'd move to linux. Well my laptop drive died and i'm on Linux Mint. Takes a little getting used to, but aside from little things it's almost unnoticeable.

The biggest problem is unnecessary,stupid and frequent updates. What was wrong with putting out a service pack once in a while and the odd security patch when needed.

If people wanted to be tethered to the internet and always having to download updates for who knows what, where things are unexpectedly broken if you don't have some file or requirement then they would have jumped over to linux or something else which is what I expect a lot of people will be doing once windows 7 becomes properly obsolete.

1. Windows updates break his graphics driver.
2. People tell him to update his graphics driver.

Common, people. Should we tell him to try rebooting his computer, too?

Go to the OEM of the graphics card and get the driver from there. If that doesn't solve it, revert to VESA/VBE by uninstalling the graphics drivers (which will make everything slow), then try to use the OEM's drivers again. Never accept automatic updates. Pick and choose your updates carefully, and never accept non-generic drivers from MS. There's no reason why MS has to buffer corrupted drivers all the time, but they do it anyway.

This is why I don't allow Microsoft updates on any of my Windows 10 systems

Actually what you described could also be a resolution issue, not just tearing. Usually tearing doesn't make something unplayable, just annoying. Make sure the in game res matches your desktop resolution.

EDIT: Give me a screenshot, even if it comes from your camera phone, and i'll see what i can figure out. I've written a few graphics drivers in the past, myself, so i'm used to weird issues.

Things have improved greatly as i just now played another two or so hours and it only happened about 3 or 4 times. Granted I never, EVER, saw it before today, but compared to earlier today where it was doing it all the time this is a vast improvement and if I have to, I can live with it.

But no, my in-game resolution and my "native" screen resolution do not match. But they didn't before today either. And as I said, before today I never saw it before. (In fact, before today I never ever saw it in any game on any computer... mine or anyone else's. I had heard of "tearing" but had never actually seen it. Boy have I seen it now.)

But since you mention it.. I'm going to try that tomorrow (right now it's about 20 minutes to 1 in the morning so I need to at least try and get some sleep LOL). Of course that's frustrating too..... every time I want to play a game go into settings... change resolution... go out of settings... play game... quit game... go back into settings... change resolution back.... go out of settings.

Weren't computers supposed to make things easier? lol

New Vegas was good enough to not need mods and was rich enough. Fallout 4? I'd go at least with an expansion of the dialog so you know what you're actually saying and not a vague 'yes', 'no', 'maybe', 'snarky' responses which you have no clue what they are going to say.

But from a debugging point of view, i can see going full vanilla.

Actual images and/or video of it happening will be useful in diagnosing the exact problem. What I've had happen to me before on linux a few times was when updating a graphics driver, it actually went to a screen resolution that wasn't actually supported, which caused the frames to be drawn incorrectly. While I don't have any screenshots from that time, I do have some screenshots from Deus Ex, which for whatever reason (i forget how i fixed it, too), screenshots would not save with the correct color and/or resolution. The effect you see in this screenshot shows what it looks like when this happens, however, normally, it'd be alot more blurry if it were a video. When it happened on linux, the actual resolution was of a totally different ratio, so instead of a diagonal line, it was horizontal, and the frames had similar blank lines as you see in this screenshot. My mouse pointer, when at certain locations, showed up twice.

http://kohlrak.sytes.net/~kohlrak/res_mismatch.png

This is screen tearing, which comes from vsync not working properly: http://nerdburglars.net/wp-content/uploads/2015/08/screen-tear-2.jpg

The idea of a tear is that if you see one, it's because the frame was in the middle of drawing to the frame buffer as the screen was updating. Sometimes due to the screen locking during refresh, but can also result without the locking since the screen can update (frame buffer reading) faster than the buffer memory can be written to. If you see more than one tear in a single frame, your graphics driver is severely borked. And, yes, it can happen, but the amount of things that'd have to go wrong to see a double tear are bad enough that it's unlikely to see one.

I used to have tearing issues with my drivers, and it's usually related to the fact that many video cards have broken or non-existing vsync support. Some games don't react well if vsync is broken, since some games actually rely on the vsync to determine when it's time to move the game logic forward. Since the CPU can sometimes render faster than an individual frame, you can end up with several frames happening within the time of a single frame. Usually these problems end up noticeable, and this is precisely what happened to my first driver. Then i discovered "the vsync pin" for VESA and was able to make vsync work, but it came at a huge cost, unfortunately: a good chunk of the cycles of a single CPU had to be devoted to polling, which made the already slow vesa code even slower, because I couldn't set it to an interrupt, so i had to draw, wait for it to go hot, then wait for it to go blank again.

With such great moments as and [url=https://clips.twitch.tv/WonderfulTangibleScallionHeyGuys]this, I can see how someone would want to keep the game unmodded.

PLS NO.
You just bought an uber expensive card that most of us dream of.
You cannot become a peasant now >:(
:P

Btw f**k Win10, once more.

Heh... two of them actually. And not long after my health dipped badly for two or three weeks where getting out of bed was nigh impossible. Still haven't built the damn thing. Not sure when I will either as I'm still not moving around so well now. Got a million dollars worth of parts (i7-8700k CPU, 2TB SSD, 4 TBSSHD (hybrid drive), 32GB 3600Mhz mem, and 2 Nvidia TitanXp GPU's. Probably be an awesome system if it were ever built. The very first parts (MB, CPU, SSD's) that I bought were bought for the black Friday sale... that's how long they've been setting in their original boxes... still. I wasn't able to get the GPU's until a few weeks ago but then my health dipped. Always something it seems.