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
Nipton (and the Madre) is usually trouble for AMD video card owners, since those cards always had more trouble with smoke and particle effect than nvidia ones.
Also, keep in mind that ENB itself can randomly drop fps when it suddenly wants to render a lot of different things at once, and you cna only disable ENB by deleting all files, including the New Vegas INI files, and letting the engine re-detect hardware and reset all options.
One is that FPS games usually put heavy emphasis on graphics, and they use graphics engines that can adapt to GPUs easily. Plus since most cards are benchmarked with FPS games, both manufacturers optimise their drivers for them.
The second is that New Vegas doesn't give a *beep* about your muscle-rig, it's limited by the CPU's single core performance. (If you don't believe me, run a process explorer that is more sophisticated than the built-in in Windows one, and you'll see that it puts load on the first core, and some on the second.)
So you can have a quad SLI/Crossfire rig with octa-core CPU, this 15-year-old engine will still use only one processor core, and most modern CPUs suck at single-core operations to the point that current AMD CPUs– despite being a really excellent line of products, and I use them with great satisfaction– are usually outclassed by 5-yo i3s or even Pentium IVs in this regard. (And Intel CPUs aren't that juicy in this department either.)
Granted, you can help it a little by using the Stutter Remover's initially disabled feature and replace heap so the game does use a secondary core in a more efficient manner, but the good heap replacement algorithms only work on some CPUs.
Master\bReplaceHeap: (defaults to 0, consider changing to 1)
This is still off by default because some people experience instability with it. Turning on heap replacement does improvement performance though. The amount it improves performance by depends upon how much multithreading your copy of the game tries to do - if it tries to do a lot of multithreading then this setting can produce really huge improvements. This also helps with some serious performance issues that arise in longer game sessions when playing a heavily modded game on Windows XP. If you have trouble with Master\bReplaceHeap turned on then you might try different heap algorithms by changing Heap\iHeapAlgorithm, which should usually be either 6, 5, 4, 1, or 3.
I used to get choppy performance as well, this fixed it for me.