Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
I whittled it down to adding (or modifying) the following lines :
[NVFlex]
bNVFlexEnable=0
bNVFlexInstanceDebris=0
bNVFlexDrawDebris=0
In fallout4prefs.ini
however, the same thing can be achieved by installing Fallout4 Configuration tool, typing 'nvflex' in the filter, and changing the values manually to 0 for each of them there, then saving it out. This should add the relevant lines for you.
I've been playing it non-stop since I tried this fix. I presume it could be legit useful for a lot of setups.
Did you start with a clean version of fallout 4 -meaning fresh install, folders cleared of all previous files and settings?
Did you roll back manually? Or did you use the 2 minute downgrade patcher? Or the archive download patcher?
Did you use a Mod manager to install it? Or a Manual install?
If a Mod manager - how did you do it?
Forming a list...
Brigde/quarry not loading textures bug also. Faraway Area Reform seems to solve things.
Patch are incoming from FOLON.
Buffout4, ENB with forceVram ease things a little bit. Game doesn't know newer vcard specs.
Default will only utilize 4096 or something of vram. "Stutter feast on city center".
16 hours had only 3 ctd/crash/freeze problem.
But also installing the xSE plugin pre-loader mod, then re-running the game installation from the FOLON app (GOG Galaxy), then starting F4 native in Steam just to the F4 launcher to set graphics options (shadows medium - the often mentioned weapon debris setting is off by default), then running the game from the FOLON app, have reduced the problem for now.
Turning down the graphics really helped with reducing crashes. But buffout 4 also feels like a necessary mod to have.
Everyone appreciates the work put into the mod but people's first impressions matter and apart from installation ongoing moans are going to be about the crashes
The installation wasnt that bad really - I did manual rather than auto - just follow the instructions and it only has to be done once
But crashes still happen and they lose progress
Also some of the instructions - like these extra mods and making it clear to use the FOLON launcher to run the game with a Steam installation - should have been better explained at launch
Common problem I see on the discord is not downgrading properly. After the downgrade has been performed, you need to find the steam manifest for Fallout 4, then set it to read-only to avoid Fallout updating back to the 'next-gen' version.
There are recommended mods on FOLON's website. I installed all, aside from Sim Settlements. Before starting a new game, I first deleted my ini files so new ones could be created on launch. I then used the provided ini patches from the GOG download.
I launch it through vortex, and make sure all of your plugins are enabled.
If the game has updated, you'll hear the original soundtrack. Reapply the patch, and make sure to set that manifest as read-only (reiterated, because this is the most common mistake.)
I did revert one setting for the ini files as I'm only using an i5 4690k, 16GB DDR3, RX590 8GB. Most of your systems are fully capable of running this compared to my ancient relic.
Use either the configuration tool, or BethINI to edit your settings (I suggest BethINI, do this after you've applied the provided INI files from the GOG FOLON download)
On the discord after sending a crashlog, it was suggested that I edit the Buffout 4 config for the MemoryManager to False. This created more frequent crashes, and I no longer received a crash log. After reverting it back to True, I haven't had a single crash in the past two days. This will run close to flawlessly, they've done a very good job.
A bit of time on the Discord, reading the 'Solutions' tab, and using the handy little bot Codsworth to assist fixing your submitted Crash Logs will go a long way, and it'll help the team to fix any actual issues.
Settings wise. I just lowered the shadows to medium with BethINI. I didn't try the 'recommended' edits, although that does work great on the base FO4 game.
If you haven't joined the discord, please do. There's a huge amount of help, and the community themselves are helping others to be able to play this game too.
Honestly, it's so bloody good too. It would be a shame for any of you to give up on it and exile yourself from the playerbase out of frustration. There's help to be had, and a good supportive community. (The search function is very handy with the discord. They have been completely overwhelmed since the game's launch from what I've seen)
I just want to be clear here:
1: You started with a clean install of fallout 4.
2: you followed the posted instructions
3: you tweaked settings for your rig's performance
4: you used the Discord to find answers and applied them as directed
5: you game is working and have not experienced many crashes since following the directions.
AND you paid ZERO (0) dollars for any of this.
Do I have this summary correct?
The game's great when it doesnt crash - though tough - maybe there's something off in the balance of health/armour/damage - but TBH it's better than anything thats come along in Game Pass for example
But being great and free doesnt mean it's wrong to mention problems and want there to be official fixes that are part of the install
Very true. but where you voice the problems and desire for solutions do matter too.
If you are having problems with your Chevy, you don't go to Toyota to point out issues and ask for fixes, you go to Chevrolet.