I've seen that happen plenty of times long before stutter remover even existed. I don't think that's a problem you can specifically say goes with this mod. In fact, I haven't seen it happen again since installing it myself, so in my case I'm inclined to say it fixed the problem. But I doubt it has anything to to with it at all.

Now for a general question. Isn't this plugin supposed to cap framerates at the maximum setting chosen? That doesn't seem to be happening anymore. My ini is set to cap at 60 but I've seen some situations where I'm indoors or staring at the ground/sky outdoors where frames register way above 60.

I had this LOD problem after using the MiniMap mod -> removed Minimap and no problem. Perhaps there is a problem with the Minimap mod or it's a problem with the combination of my installed mods.
I think OSR is not responsible for the LOD problem.

I've seen this happening a few times with my MiniMap aswell. I'm not sure how it happens but it is a rare side effect of toggling the LOD on and off, it could be in combination with OSR but it could be completely seperate. If you really want to find out I suggest removing OSR for a while and see if the problem does not appear anymore. Although I doubt OSR has anything to do with it. :shrug:

Fast4MM has some minor issues for me as well (but I don't care seeing as I can finally use it again thanks to wrye) such as all in-game sounds being "disabled", sometimes a vague LOD issue, failure to load textures but nothing that's ruining the game (A restart fixes the issues + the issues don't occur often). IMHO, Fast4MM performs the best out of all of them so I'm keeping it.

It always caps it for me (EDIT: except for when I am in menu mode).

Is there a way to completely remove the console spam? All that thread errors and spin error crap is annoying.

editable in the ini

Where? All I see is "bFPSConsoleSPAM" which enables the spam. It's already set to 0.

OSR does not have an option to disable console output. However, it does not normally produce significant quantities of console output after initial startup unless some kind of performance monitoring is enabled. If you are getting additional console messages during normal operations, check your bHeapProfiling and iCriticalSectionMode settings (the former should be 0 and the later should be 2 I believe). I could add an option to suppress all console output, but... at the moment, I have no ability to do much of anything (dead computers + I have the flu). In a few days I should be able to do things again.

Given this, what should the setting be for an 85Hz refresh rate?

Since no one has answered you yet.
Given that, it would seem to be 17 or 85.

I recall SkyRanger-1 commenting about this in a recent OSR thread. It didn't apply to me so my recollection is foggy... I think 40 was suggested. Experiment and see what works best- nothing will break! Better yet, search for "stutter", thread title only, and read up on the OSR threads.

Well I don't know what the heck is going on with my install right now.

yes added a few mods recently - testing a few now.

But what I'm finding is that OSR is not working well - and after removing the mods I'm testing now and still getting problems such as crashing on save, crashing on 10-15th cell change, Complete soupy morass in barter menus, etc.

I first changed the heap mode to 3 from 5 (which had been working great up till now) with some success. Then I just took this out and the game is stable again.

Errr. I don't want to lose this.

So I'm not an expert on the console spam that this produces but here are some outputs that maybe others can decipher:

hook mode 1: using main GetTickCount callcrit_sec_mode 2MemoryHeap Optimization Mode 3: attempting to replace the Oblivion heap manager with my SimpleHeap1Heap Initialization (268435456, 0)critical section b32b80 overriden to spin 1500critical section b32b80 overriden to spin 1500Special crit. sec. 1 (@ 1848CC80, thread FA0) spin 2000 -> 2000Special crit. sec. 2 (@ 1848CE00, thread FA0) spin 1000 -> 1000Special crit. sec. 3 (@ 18582A80, thread FA0) spin 4000 -> 4000initialize2() running in thread fa0Suppressing CRITICAL_SECTION Renderer+0x180 (3A15F50)Special crit. sec. 4 (@ 23313880, thread FA0) spin 4000 -> 4000

and oh darn it conlog deleted the other ones. Well if I get some stability I can count on back I will reinstall and get more info.

The Spin 4000 thing was usually the last data recorded before ctd.

So then the most recent crashes have led to new notification by windows (Vista - yeah I know, Vista):

Data Execution Prevention (DEP) is a security feature that can help prevent damage to your computer from viruses and other security threats. Harmful programs can try to attack Windows by attempting to run (also known as execute) code from system memory locations reserved for Windows and other authorized programs. These types of attacks can harm your programs and files.

DEP can help protect your computer by monitoring your programs to make sure that they use system memory safely. If DEP notices a program on your computer using memory incorrectly, it closes the program and notifies you.

I've never seen this before.

Found it. Thanks.

Turn off DEP completely - It's quite a nuisance. Use bcdedit ( or VistaBootPRO if you prefer to be safe ) and edit Vista's boot flags.

ShadeMe-

I followed this tutorial on turning off DEP: http://vistasupport.mvps.org/disable_data_execution_prevention.htm
it matched a few others as well.

Double checked that it is off. Not sure what you mean by editing boot flags though.

Didn't handle the issue though - which has progressed to the game crashing at load every time now.

Need to look at save games files - maybe they're bad.

==========================

edit - think I found the answer - I updated the mod Pure Immersion and it was downhill from there. Reverted to older version (thankfully I don't throw old versions out right away) and stability returns.

Sorry for muddying up the thread with this - of course in hindsight it seemed like the right track (misuse of memory ... OSR - OBSE would have been next in that line of thinking).

[General]
MinimumFPS=12
MaximumFPS=61
iSmoothFrames=0
iSmoothMode=0
iSleepExtra=5
bFix64Hertz=0
bFPSConsoleSPAM=0
iSchedulingParanoia=2
iSchedulingResolution=1
iHardMaxFrametime=200
iHeapMode=1
iHookMode=0

[CriticalSections]
iCriticalSectionMode=2
iCriticalSectionSupression=1
iDefaultSpin1=500
iDefaultSpin2=500
iMemorySpin=1500
iMemoryUnfairness=4
iExtraDataSpin=-1
iUnknownSpin1=-1
iUnknownSpin2=-1
iUnknownSpin3=-1
iUnknownSpin4=-1
iUnknownSpin5=-1
iUnknownSpin6=-1
iSpecialSpin1=2000
iSpecialSpin2=1000
iSpecialSpin3=4000


OSR doesn't seem to be capping my FPS at 61 anymore. Very smooth though. What do iSmoothFrames and iSmoothMode do?

This mod is so much win. Thank you very much good sir, in conjunction with streamline my game now runs so smooth it seems flawless, even with 13+ enemies attacking me in the open while riding on horseback... I tried it lol. Once again thank you all.

I just upgraded from 3b5 to 3b6 and there is definitely a noticeable improvement. I installed 3b5 a long while ago and remember not noticing much difference, but figured I might as well keep it. I messed around with the heapmodes and couldn't find one that worked; 1 crashed on startup, 5 crashed on save, 3 crashed out of nowhere, didn't try 2 or 4. Nonetheless the improvement is there, so thanks!
Edit: Tried heapmode 2 for completeness, also crashed on startup. Ahh well.

I salute the you good sir. This works phenomenally well... well except for the crashes during exterior -> interior transitions, but I suspect I can resolve that with some fiddling =3

BESIDES that little hiccup the results are amazing.

Edit: Solved it with fiddling

SkyRanger-1, are you still working on this?

Sort of. There was about 2 months that went by with no work getting done, but for the last week or so I've been actively working on... Fallout Stutter Remover. But in theory I just change one flag and it compiles as Oblivion Stutter Remover instead.

In practice, what OSR really needs is someone to put a lot of hours in with a debugger figuring out wtf is causing the known bugs (most of which involve heap replacement). Whereas what I'm working on atm is a system which allows the configuration file to specify what OSR/FSR should do at a much finer granularity and with fewer hardwired constants (ie the configuration file could tell OSR/FSR how to find a particular critical section that OSR/FSR did not know about, and specify a particular mode and spincount to apply to only that particular critical section).

Also, IIRC the last alpha release for FSR included preliminary code for optimizing Oblivion/Fallouts hashtables that code has not yet been released for OSR.

sweet to know you're still working on this. thank you so much

Just out of interest: for anyone using Windows 7 64bit, which heap mode do you find the most effective?

I'm using 3 right now, but wondering if 1,2 or 5 are any smoother? I've tried 1 and 3 so far, but can't see much difference with the brief glance i've taken.



"ie the configuration file could tell OSR/FSR how to find a particular critical section that OSR/FSR did not know about, and specify a particular mode and spincount to apply to only that particular critical section"

I have no idea what any of this means, but i'm going to assume you're discovering yet another way to make Oblivion run even smoother. That thought makes me beam with glee! You're going to be around for the release of TES:V right? I'll bake you a fresh batch of cookies if you are. The secret ingredients are caffeine, and a mysterious herb that witch doctors say inspire the consumer to write lengthy amounts of code... :blink: