TTW Performance Guide (OLD, Do not use!)

[khumak]

I heard the guy who wrote MO is the lead developer for NMM now and that they're redoing it from scratch.  Supposedly the goal is to make something with all the features MO has but the ease of use of NMM.  Will be interesting to see how that turns out.  I'm loving MO so far after figuring out some of the quirks.  I only use it for TTW so far but I plan on migrating my Skyrim mods from NMM to MO when I get back into that.

[generalmx]

Wanted to make two comments here:

 

1) I HIGHLY recommend anyone who wants to squeeze out extra FPS try out Process Lasso, especially on laptops or other builds where there may be even a slight CPU or I/O bottleneck, setting "falloutnv.exe" and "fnv4gb.exe" as Game Process and/or exclude them from Pro-Balance Restraint. Link: https://bitsum.com/

I've successfully gotten more frames out of Oblivion, Skyrim, etc. before on lesser hardware. One can do this all manually but Process Lasso makes it pretty easy.

 

2) Shader 3.0 on my Nvidia GTX 560 Ti with recent drivers (373.06) on Windows 10, despite Nvidia saying it's supported, caused some errors with the vanilla Pip-boy Light as well as Flashlight NVSE and some problems with textures popping in/out, so I went back to default shader support.

[Bandy]

I used Process Lasso in the past with good results in flight sims (very CPU heavy), but since Win7 find that the OS does a pretty good job of prioritizing threads. I haven't had it installed in my latest gaming sys, but might try again. Thanks for reminder.

As far as GPU drivers go, if you have an aging card (560Ti is several generations old...) then just IMHO the new drivers may be compatible and work to render an image, but you are better off using an older driver from closer to the era of the card.  Nvidia resources will be spent on new products, and newer drivers are simply not going to be optimized for older architecture, so as you identified GFX issues will likely result.  Search and find the driver sweet-spot for your card.  Again, just IMHO from my experience and other anecdotal posts.

[CVB_Taihou]

https://forums.redacted.tv/threads/ultimate-windows-10-gaming-tweak-guide.1205/

 

Is it okay to follow an windows optimization guide like this along with it?

[RoyBatty]

Bunch of snake oil.

[jlf65]

renderinfo.txt is simply telling you what it finds. It's not a settings file - changing anything in it is futile. All changes to settings are done in the ini files that are in the documents\My Games\FalloutNV directory. Unless you're talking about enb settings, then those are set in the enblocal.ini file in the main game directory.

[RoyBatty]

If you run the default launcher it will reset everything, don't worry about changing that stuff.

[H1ms3lf]

[quote=John]So I should ignore steps 6-7?[/quote]

I also didn't get why it's mentioned to change letters A's into B's at step 6, seems to serve no purpose.

[RoyBatty]

Updated 1st post with current instructions.

[CyberDanz]

[quote=CVB_Taihou]

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?

 

[/quote]

 

I can verify while using my quad core processor, I set my value at 4 and it works for me!

@Dead Sirious and @RoyBatty ...  Thank both of you gentlemen for all info on this thread!  I haven't tried messing with any of the experimental settings.. but after using the latest LAA Patch and all linked items (including the vorbis.dll's for audio) with the recommended settings works!  After the LAA Patch, I too, can use DefaultHeapInitialAllocMB=500 and ​ScrapHeapSizeMB=128 under my [Memory} setting created in the nvse_config.ini file.  I set my NVSR heap setting at 0 (Default).  I don't use ENB either, for those wanting to know.