TTW Performance Guide (OLD, Do not use!)

Post by **Dead Sirious** » Thu Aug 04, 2016 1:08 am

I didn't touch any value upon collecting the INI files. Will update by tonight

Post by **RoyBatty** » Thu Aug 04, 2016 3:12 am

I actually don't know what that setting does or if it's even relevent.

Post by **RoyBatty** » Sun Aug 07, 2016 1:44 am

That setting is in the experiemental section which should not be enabled, so it doesn't matter what it's set to.

Post by **Bandy** » Sat Oct 22, 2016 12:19 am

OK, after months of monumentally stable TTW gameplay this summer/fall, I start getting random CTD this morning, going through doors, just walking outside, etc. having made no OS, driver, or mod changes to my install. I keep saves to 100 or so, and re-write unimportant old ones, and yes, number of mods below 124. I restarted system, a few times in fact...

Stumbled upon the bUseThreadedAI=1 and iNumHWThreads=2 edits on another FO site, but contra to what is said here in OP step 2 where edits are recommended for the three ini's (Fallout.ini , FalloutPrefs.ini , Fallout_default.ini), the other post I found said "DO NOT edit fallout_default.ini" [emphasis theirs].

I made the two-line edit just to fallout.ini and CTD's stopped, game play is stable for 3+ hours where it CTD about every 5 min before. Searched here afterwards to find this thread.

Just wondering if there is further insight. As mentioned in posts above, and after time spent in TES, some of these Bethesda "fixes" can amount to nothing more than placebo, so wondering if all 3 ini's need the edit. So far so good with only one.

Win7 x64 Pro, i7 2600K @ 4.4 GHz, 8 GB RAM, beefy GPU, NVMO 1.3.11, steam FO3/NV off C:\ ...

Post by **Risewild** » Sat Oct 22, 2016 2:37 am

The fallout_default.ini is only used by the game to revert the other ini files to vanilla state at game launch. If you use something that bypass the vanilla game launcher (which most people do) then the game does not use the fallout_default.ini for anything at all.

Post by **CVB_Taihou** » Sat Oct 22, 2016 2:22 pm

It looks like an iNumHWThreads value can be set to 4(more than 2) if a CPU has more than two cores. Can anyone test it?

Post by **khumak** » Sat Oct 22, 2016 5:53 pm

Honestly I think the biggest thing I could do to improve game performance would be to disable Windows Defender but I'm not willing to disable and re-enable it constantly every time I play and I'm also not willing to permanently disable it so I've just accepted the annoyance of knowing that Windows Defender will decide Fallout is malware several times a day and force me to kill it and restart the game.

Post by **paragonskeep** » Sun Oct 23, 2016 12:21 am

[quote=Risewild]

The fallout_default.ini is only used by the game to revert the other ini files to vanilla state at game launch. If you use something that bypass the vanilla game launcher (which most people do) then the game does not use the fallout_default.ini for anything at all.

[/quote]

I always edit all three (with keeping a default backup) due to whenever Steam updates and you click a launcher I get the Steam default launcher and it would revert all to vanilla. Not sure if I'm the only one this happens to, but I always edit all 3

Post by **Bandy** » Mon Oct 24, 2016 10:53 am

Thanks for replies. I would have thought most here are using MO (or variant) and the 4GB-patched-FONV, which I assume is by-passing the vanilla launcher.

As I understand, editing ini's using MO only makes altered copies for use when launching the game from that platform, so no change to vanilla files. MO also only allows edits to Fallout.ini and FalloutPrefs.ini, not Fallout_default.ini, so going to have to assume there is a good reason for that...

Post by **jlf65** » Mon Oct 24, 2016 4:17 pm

I don't use MO with FO3/NV because it's never worked for me. The guy who writes MO tests with Skyrim, and any questions I asked about FO3/NV were always ignored. I mostly hand install mods. It's a little more work, but usually gives better results.