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
Multi-core CPU tweaks[edit]
If you have a Dual/Quad core Processor or a processor with Hyper-Threading, then set these values to this:
bUseThreadedBlood=1 (default 0)
bUseThreadedMorpher=1 (default 0)
bUseThreadedTempEffects=1 (default 0)
bUseThreadedParticleSystem=1 (default 0)
bUseBackgroundPathing=1 (default 0)
bUseBackgroundFileLoader=1 (default 0)
iNumHavokThreads=3 (default 1)
iThreads=10 (default 3)
Otherwise leave them at the default.
However, it should be noted that an article on FiringSquad found no benefit in using these settings. Whatever the configuration of these INI variables, it is generally acknowledged that Oblivion makes very little use of additional CPU's/CPU cores. This may be because all of the functions that these variables enable multithreading for are not CPU intensive tasks, there appears to be no variable related to enabling multithreading for the main scene renderer, which would most benefit from such an optimization. Things such as the Particle System and Shader Effects are not used in excess in Oblivion, so using multiple threads for processing related to them will likely not have much benefit.
Despite dubious significance to performance, these options can effectively prevent or at least reduce crashes on multi-core systems.
Warning! Before you make any change, make a copy of your Oblivion.ini and your latest game save files. Changes in the Oblivion.ini can corrupt game saves or prevent the game from starting. In the event of an issue arising, simply replace the modified INI file with your backup and try using a backed up or earlier save file.
===============
Acouple other sites say the same thing. you may try to limit your fps. you can search online to do this.
iNumHWThreads=2
to the ini in the General section. Same tweak applies to Fallout 3.
You can also limit your fps with Oblivion Stutter Remover. Capping to 60 fps or even lower might help smooth things out. The game wasn't made to run with 200 fps and I can imagine it would screw with some of the animations, and greatly hasten the onset of the A-bomb. Of course A-bomb is easy to deal with on PC, but it still sucks when it pops up.
Also limit the number of mods that add NPC's since AI chokes the game engine more than anything and is usually the single biggest source of fps-drop.
Thanks Iwaloa.
I wonder if there are enough skilled people who are as passionate about the game as with Morrowind though. Of course a fork from OpenMW that added a physics engine and formid processing would apply to Fallout3 and NV as well.