The Oblivion Performance Project (TOPP)

Post » Thu Aug 19, 2010 1:47 am

.ini Settings and Tweaks to Consider(DO NOT simply apply all of these changes without knowing what you are doing, or you will probably cause more harm than good. The 1.2 Oblivion patch updates the .ini file with fairly good default settings for the most part, so don't change anything you aren't sure about unless you are willing to test the difference and reverse the change if it doesn't work out. Input on updated recommended .ini tweaks is welcome! Make sure you not only make a backup .ini, but that you compare frame rates and game stability before and after making changes: changes that speed things up on one computer may cause problems on another.)Recommended (Defaults are in parenthesis.)1) iPreLoadSizeLimit = 26214400 (26214400*)2) uGridstoLoad = 5 (5)3) uInteriorCellBuffer=3-5** (3)



Please correct me if I am wrong but Line one above its same number 25 meg. if ya add a 0 then you get 250 meg. Mine was already set to 262144000 ..


The code box is from the OP.


Disregard this...lol...im an idiot ya have to keep reading.....
User avatar
Krista Belle Davis
 
Posts: 3405
Joined: Tue Aug 22, 2006 3:00 am

Post » Thu Aug 19, 2010 3:24 am

And to add to it ... http://www.gamesas.com/bgsforums/index.php?showtopic=1071593 has really contributed to performance in my game. Used in combination with OSR on my Vista 64 rig is working great.

Interesting, thanks for the link.
User avatar
yessenia hermosillo
 
Posts: 3545
Joined: Sat Aug 18, 2007 1:31 pm

Post » Thu Aug 19, 2010 12:10 am

Goodness gracious. Turning down prerendered frames in nvidia control panel from 3 to 1 gave me an FPS boost in most areas by 20-40. Wow. Changing it to zero creates problems though, right?
User avatar
Gen Daley
 
Posts: 3315
Joined: Sat Jul 08, 2006 3:36 pm

Post » Wed Aug 18, 2010 1:28 pm

Am I correct that the advantage of packing files into a BSA is solely to reduce fragmentation and keep the assets close together on the disk?

One would expect, though, that looking through the BSA for a particular asset introduces some overhead. If instead, one uses a defrag tool that optimizes file placement (rule: Oblivion/Data files together in the outer rim) wouldn't unpacking and removing all BSAs lead to better performance?
User avatar
Nathan Barker
 
Posts: 3554
Joined: Sun Jun 10, 2007 5:55 am

Post » Wed Aug 18, 2010 5:44 pm

So in reviewing this thread some And seeing this section in the first post about how to set the pagination file size:
►"Making BSAs was far more efficient. With loose files, defrag will put them where it thinks is best. Which may separate them by quite a bit. As a BSA, it's all one file to the OS. So there's much less time spent running all over the platter to get the stuff . . . The bigger key here is that getting it to fall in one large contiguous chunk so the disk access is smooth and not jumping all over the platters. Pick a size for the paging file that's large enough to handle 4x your physical RAM. Don't just let Windows manage it, because Windows does a lousy job of this and leads to mass fragmentation." -Arthmoor
►The_TJ's response:
CODEUsually, one should not change the pagefile size unless one gets messages that it is too small. The pagefile works in a complementary way to the RAM, which means that the more RAM you have the less pagefile you need. It may be true that when Windows changes the size of the pagefile it causes some fragmentation. It may be possible to counteract this (and eliminate overhead) by setting the pagefile minimum and maximum at the same size, rather than allowing it to change in size during operation. For the best results, defragment your hard drive before doing so, preferably not by the Windows defragmenter (which isn't very good). As a general rule of thumb follow the scheme below:

If you are running a 32-bit Windows version and:

1. You have less than 2 GB of RAM, set pagefile at 1.5 times your RAM
2. You have between 2 and 4 GB of RAM, set pagefile at 2 GB
3. You have more than 4 GB RAM, you probably have 64-bit Windows because anything over 4 GB of RAM doesn't work on 32-bit computers and setting pagefile higher than 4 GB has no use either

If you are running a 64-bit Windows version:

1. Click Start, point to Administrative Tools, and then click Performance
2. Click System Monitor
3. In the right pane, click + (the Add button)
4. Click Use local computer counters
5. In the Performance object list, click Process
6. Click Select counters from list, click Page File Bytes Peak, click Add, and then click Close
7. Let the counter run while playing Oblivion, or whatever it is you spend your time on
8. Note the maximum value for the Page File Bytes Peak counter, multiply that value by 0.70 and set your pagefile accordingly
9. The theoretical size limit of the pagefile for 64-bit Windows is 16 TB

Sources:
http://support.microsoft.com/default.aspx?...kb;en-us;237740
http://support.microsoft.com/default.aspx?...223&SD=tech
http://support.microsoft.com/kb/889654
I'm not using 64 bit XP - I'm using Vista 64. And these instructions for setting up monitoring don't quite match up.
Can someone please post the instructions to get Vista to do that? Those links are dead too Or all lead to the same generic help page at MS.

thanks for any help.
User avatar
Rachel Eloise Getoutofmyface
 
Posts: 3445
Joined: Mon Oct 09, 2006 5:20 pm

Post » Wed Aug 18, 2010 5:39 pm

Since this guide is a bit dated, does a higher iPreLoadSizeLimit actually help stuttering?

Is FPS effected if you run a FCOM+QTP3 setup with the default iPreLoadSizeLimit?
User avatar
NAkeshIa BENNETT
 
Posts: 3519
Joined: Fri Jun 16, 2006 12:23 pm

Previous

Return to IV - Oblivion