If you are experiencing game breaking issues after the 1.10.980 update, please detail your setup here.

[flayman]

I thought I'd have a stab at being helpful and compiling some data. There seems to be a minority of players who are reporting issues like constant crashing to desktop, unbearable loading times, and other issues rendering the game unplayable since the update was applied.

Some are saying that they never ran any mods and have been completely vanilla, that they installed the game during the sale and had fun playing for about a week until the patch. If we believe them, then there must be something weird about their setups that did not get tested.

So if that's you, then I invite you to share your experience and list some system particulars, such as:

1. Your experience (what is happening?)
   
2. CPU make and model
   
3. GPU make and model
   
4. The driver version number
   
5. total system RAM

And anything else that might be helpful. There could be common data points. Thank you for your participation.

EDIT: This should go without saying, but it probably doesn't. If you're not using the video driver supplied by the card manufacturer (and the latest at that), you really should be. Don't use Microsoft supplied drivers. Go get the driver from Nvida or AMD or whatever. If it's onboard graphics like Intel, then you might not have a very good time.

And for troubleshooting, have a look at this very helpful topic: https://steamcommunity.com/app/377160/discussions/0/4361250442642108947/
Alt version: https://steamcommunity.com/sharedfiles/filedetails/?id=3241230342

[The Inept European]

Originally posted by Gray Matter Guerrilla:

My game is playable but was crashing until I found the 'weapon debris' issue - solved it. However, voice overs seem to be out of sync and when one line is finished, the next voice line starts before the first is finished. Lips are also out of sync. I wonder if this is related to high frame rate? Will have to check into this more.

Specs:
13700K (OC'd)
32 GB DDR5 @ 6000
4090 w/ 551.76 driver version
installed on m.2 SSD
Win11
4K resolution @ stable 144 frames

Yes voice lag is caused by running at unsupported FPS.

[Gray Matter Guerrilla]

Originally posted by The Inept European:

Originally posted by Gray Matter Guerrilla:

My game is playable but was crashing until I found the 'weapon debris' issue - solved it. However, voice overs seem to be out of sync and when one line is finished, the next voice line starts before the first is finished. Lips are also out of sync. I wonder if this is related to high frame rate? Will have to check into this more.

Specs:
13700K (OC'd)
32 GB DDR5 @ 6000
4090 w/ 551.76 driver version
installed on m.2 SSD
Win11
4K resolution @ stable 144 frames

Yes voice lag is caused by running at unsupported FPS.

Good to know, thanks buddy.

[Lunar Umbra]

AMD Ryzen 7 5800X3D
NVIDIA GeForce RTX 4070 SUPER
32GB DDR4-3200 (16x2)
2TB SSD NVMe PCIe 3.0 x4
2560x1440 360Hz Monitor

I had not played Fallout 4 in a couple years, so this was a fresh first time install no mods on this system.

Client launching game with black screen issue (Windowed/Borderless), no menu visible (Alt+F4 to force close). Fullscreen seemed to work fine (no black screen), but the desire was to have Windowed/Borderless. Default settings already had Weapon Debris - Off (unlikely related to game launch anyhow).

What worked for me; (an absolute) lower refresh rate to 120Hz (anything higher than 144Hz - black screen), also keep Fallout settings .ini files as Read Only unless editing.

Its possible that not all settings below are related to the black screen issue, but they did provide further in-game stability for my system.

NVIDIA Control Panel - Manage 3D Settings - Program Settings - Fallout 4
Max Frame Rate - 60 FPS
Monitor Technology - Fixed Refresh
Preferred refresh rate - Application-controlled
Vertical sync - Use the 3D application setting

Fallout4.ini
[Display]
iPresentInterval=1
bNvGodraysEnable=0

Fallout4Custom.ini
[General]
sStartingConsoleCommand=gr off

Fallout4Prefs.ini
[Display]
iPresentInterval=1
bTopMostWindow=1
bMaximizeWindow=1
bBorderless=1
bFull Screen=0

[The Inept European]

OP I have given you a cookie because what you are trying to do is very public spirited and laudable.

[The Inept European]

Originally posted by Lunar Umbra:

AMD Ryzen 7 5800X3D
NVIDIA GeForce RTX 4070 SUPER
32GB DDR4-3200 (16x2)
2TB SSD NVMe PCIe 3.0 x4
2560x1440 360Hz Monitor

I had not played Fallout 4 in a couple years, so this was a fresh first time install no mods on this system.

Client launching game with black screen issue (Windowed/Borderless), no menu visible (Alt+F4 to force close). Fullscreen seemed to work fine (no black screen), but the desire was to have Windowed/Borderless. Default settings already had Weapon Debris - Off (unlikely related to game launch anyhow).

What worked for me; (an absolute) lower refresh rate to 120Hz (anything higher than 144Hz - black screen), also keep Fallout settings .ini files as Read Only unless editing.

So this is exactly as per the official release notes.

[The Inept European]

TL;DR: RTFM

[Bobby Digital™]

W10 Home
I5 10400f
16 gigs ddr4 2666 RAM
AMD 6700 non XT
Steam and the game installed on a secondary storage device - it's a HDD hybrid with a small amount of ssd cache

No issues to report at this time, no crashes, no failures to launch, stable fps, 1% and 0.1% lows high

[Death Approaches]

the only thing I can report that's consistent, leaving a virginal vanilla .980 running 24/7 on a tertiary intel/NV machine, over 6200 minutes (over 4d 8h) now, is that this is barely an update, and definitely deserves only an #.#.### in standard software development nomenclature... a build change, not a code update.

for me, it doesn't crash, not once, doesn't memleak, free(s) and malloc(s) don't run amok, it seems a good compile at least... load times are near-instantaneous on a 4th gen SSD NVMe, even faster than with mods to accelerate, (go figure, no mod overhead), audio is fine except for known previous issues like HDMI streams not re-initializing if you alt-tab away, I've alt-tabbed about 100 times and the game has restored every time be it windowed or exclusive fullscreen, et cetera.

one frustrating one I notice from earlier builds is there's a persistent math fail in VATS, where the hit is calculated, the crit meter increments, but the shot / beam passes right through the target, no damage... this is a regression from years back.

It's the same game, with the same problems, and I'm guessing if you get enough reports, the ratio will be roughly the same - the issue being, those without issues don't always come into the discussions section til they want something, mod suggestions, friends who also enjoy Fallout 4, etc. That bias should be roughly the same, too... but how many people pop in just to say "works for me!" after an update? Probably not many. They're enjoying playing.

I feel for those gamers without technical ability or years experience dealing with "Bethesda's ways" but it seems the divide is the same as it's always been; those who click Install and then Play and just expect the game to work, and those whose skills go slightly above driver updates and running Windows Update one more time, hoping for a miracle cure.

while what you're planning is commendable, you have absolutely no idea how their systems are configured, if they're overclocking/undervolting, if they have thermal issues, driver issues, wonky hardware bought used off of ebay, warez off of disreputable torrents laden with all kinds of things no one wants on their systems, piecemeal updates in a system that shouldn't even boot but somehow does, further complicated by a non-technical user submissions (eg. "every other game I have runs fine!")

I'm not sure your compilation of this data will yield any useful metrics other than tabulating how many are experiencing issues amongst the chaotic noise and foul-weather trolls; you'd have to make a system image that everyone would boot from, perform burn-in stress testing, lock .ini values to a standardized "test set", etc. to gain truly useful data. So keep that in mind. testing methodology is a methodology for a reason, after all. there's just too many variables otherwise.

[flayman]

Originally posted by The Inept European:

OP I have given you a cookie because what you are trying to do is very public spirited and laudable.

I thank you kindly.

[Lunar Umbra]

Originally posted by Death Approaches:

...testing methodology is a methodology for a reason, after all. there's just too many variables otherwise.

Well, I can say for certain perusing the array of posts while searching for context similar to mine gave me the direction to tinker with settings and discern the applicable modifications needed toward a solution. In my case Windowed/Borderless always produces a black screen unless refresh rate remains 144Hz or lower. It was also a reminder of past optimizations that I had used for stability.

[flayman]

Originally posted by Death Approaches:

...while what you're planning is commendable, you have absolutely no idea how their systems are configured, if they're overclocking/undervolting, if they have thermal issues, driver issues, wonky hardware bought used off of ebay, warez off of disreputable torrents laden with all kinds of things no one wants on their systems, piecemeal updates in a system that shouldn't even boot but somehow does, further complicated by a non-technical user submissions (eg. "every other game I have runs fine!")...

This is true, but we can start with assumptions like someone doing overclocking or undervolting is probably savvy enough to troubleshoot. Follow-up questioning can shed some light. What I'm interested in particularly are the stories of "Day before the update and for days or weeks prior, it ran just fine. Immediately after update and ever since, I can't even play it." Then we can try to shine a light on the environmental factors and at least try to educate someone and help them get it working if it's just failure to RTM. Or there could be a pattern. This effort might uncover nothing more than the fact that people don't read, which we know anyway, and that a developer has to work extra hard to make it effortless.

[The Inept European]

Laudable.

[The Inept European]

Originally posted by matt f:

"Day before the update and for days or weeks prior, it ran just fine. Immediately after update and ever since, I can't even play it."

99%+ of these reports are F4SE users, many of whom don't even know they are F4SE users.
Genuine instances of this for mod free users - other than where their video settings don't match the release notes - is going to be close to zero or zero. But as they say, "prove me wrong". 😁

[Lunar Umbra]

Originally posted by The Inept European:

So this is exactly as per the official release notes.

Are there further detailed PC release notes?

I must be aware of the wrong release notes. The only mention of FPS, Hz and Resolution that I read are specific to the Performance and Quality modes of Consoles.

[The Inept European]

Originally posted by Lunar Umbra:

Originally posted by The Inept European:

So this is exactly as per the official release notes.

Are there further detailed PC release notes?

I must be aware of the wrong release notes. The only mention of FPS, Hz and Resolution that I read are specific to the Performance and Quality modes of Consoles.

I don't read the release notes as saying those FPS / Hz / mode statements apply only to consoles. But you're right, it's ambiguous.