Is there a Streamline release thread in these forums, because I couldn`t find it? I`m also wondering which version you are using? The 3.0 version comes as an .exe file on http://www.tesnexus.com/downloads/file.php?id=10400. Why`s that? Can this be trusted? You don`t know nowadays...

I just use the two streamline files from Wrye's bains' http://www.tesnexus.com/downloads/file.php?id=22170 - take the patch apart to just replace the files in the steamline bain, so you have just one bain

Are these files newer than those from TES Nexus (3.1 Open Beta + Patch)?

*Edit*

Ok, I checked it. These files are the same that are on TES Nexus. I think I`m safe with them.

Yep the same. All documentation is also included in the bains. I cant remember seeing a dedicated streamline topic for ages (maybe munched by the forum now), but a search for the word streamline in any optimization topics will bring up loads of information on the subject, it quite often pops up in many discussion.

Do you know if Streamsight causes problems in conjuction with RAEVWD?

I`m also looking through the ini and the quick config right now and what puzzles me is the following sentence:



This is set to "set SLfpsmon.High to 31" and "set SLfpsmon.Low to 26". Does that mean Streamline is going to reduce the details in this fps range? I`m wondering if these values are good? Why not set lower value lower, say, to 15?

only if you let it adjust your view distance, RAEVWD is only a collection of meshes for generating distant LOD. streamsight can't really conflict with them

With older rigs, Streamsight and RAEVWD is a very good combination. I wouldn't be able to run RAEVWD without lowering uGridDistantTreeRange/uGridDistantCount and with Streamsight's fog it still looks quite nice.

Another question:

With All Natural I need to set SLv.WeatherUnsticker to 0. If I deactivate the streamsight in Streamline, does Streamline read this setting nevertheless (this setting appears under the section of the streamsight feature? I guess it doesn`t matter if don`t use streamsight anyway.

This feature seems to be strange to me anyway, because I don`t know, why I would like to have appear fog much sooner and set the uGridsDistantCount lower than vanilla? It`s a bad trade-off visually. Isn`t a big world about seeing far?

By default weather unsticker is on, so if you use streamsight with AN you need to turn it off.

If you dont use streamsight, no need to change it, it will not be used by streamline.

The only things I use out of the main selections these days is Purge Cell Buffers and Streamsave, because I have OSR installed which handles FPS better.

As for fog, AN has its own settings if you want to reduce distant fog, as does RedBags fog if not using AN

So Streamline with PCB and Saves

OSR managing FPS

And if required distant fog by AN (or in my case on the laptop RedBags fog).

If you do use streamsight though be sure to read the streamsight .mht file in the documentation for UGrid settings (which you change in your documents/my games/Oblivion.ini file) which correspond with distant fog.


Edit: One or two further tips before you get there - If you start a game the settings in the ini file are checked on first run by streamline. Thereafter they are not automatically re-checked at each game load....

So you start from your save, but you have changed your ini settings since the last game session, you will still be using the previous ini settings - You have to press Right Ctrl key and Home key together in-game, and streamlines menu pops up, then choose the special actions / re-initialise ini settings - This has now re-read your new ini settings. Exit the in game menu, and save. When you continue the new ini settings will be used.

This has to be done everytime you tweak the ini settings outside the game (if you edit it with notepad for instance), your ini settings become part of your save game, so streamline does not re-read the ini file at game load, just uses the ones in your save game and continues - hence the need to re-initialise them.

One further potential problem:
After spending lots of time perfecting the ini for your machine, and if you use BAIN installers - Change the ini in your BAIN to match your perfected ini, if you anneal all your BAIN installers, Wrye Bash will spot the difference between the ini in the bain and the one you have been editing, and re-install the original ini from the installer, overwriting all your work on the previously installed ini. (There is an ini backup in the original if all goes wrong)

May I ask, what did you set in OSR (I guess under FPS Management) and why?

Oh boy, large subject, Just remember before you read on the default settings in OSR are good, and manage FPS well enough on my Core2Duo for me not to even have Streamline manage fps details (as posted above), I have tweaked OSR slightly though from defaults....


Also remember
dont use the purge on travel option in streamlines ini when combining streamline with OSR.

But as mentioned I dont use Streamline fps management anymore - Just re-iterating what has been found with that combination should anyone try it.

Heres the start of my Streamline ini (the only thing you cant see here is the streamsave settings, adapt those to your needs ....


Using OSR defaults with that is all you need to do really if the OSR details are too heavy to understand.

One last question (hopefully):

I set MaximumFPS = 60 because I have a 60Hz monitor (OSR default is 30). Is that ok? Because from the readme description below I don`t get, what it really does.

Damn I knew there was a detail I missed - Yes setting the max fps in OSR to your refresh rate is a good idea - ( or multiples/division of - 60 is my laptop refresh rate, and I have 30 set, I could use 60 but the laptop gets a bit warm after a while , I use 60 on the desktop )

I think I read somewhere the minimum FPS the human eye can detect before things get noticeably choppy is 25 fps, personally I believe you can perceive finer or smoother framerates above that say 30-40. If you have a constant FPS above that range its wasted graphics power really. Edit: See Dragoowraith's post below.

Edit: Expanding on the spoiler above reference using OSR and Streamline FPS combined - (and tying in the 10% recommend with refresh rates)....

Edit2: Those figures for 10% are rough guestimates.

Thank you for all your help. It`s much appreciated. :foodndrink:

No problem - If you want to monitor framerates just use TDT in the console. OSR will still push the boundary of the fps setting you have set, for example watch your fps while in the games menus, my desktop goes up to a ridiculous 75+ sometimes.

This is a pretty common urban legend: in reality, your eyes are not digital devices and therefore don't have a "refresh rate" or "FPS" (or, indeed, "frames"). Your eyes see all light that enters them continuously, and can in certain situations pick up extremely subtle differences.

More important than your eyes for this, however, is your brain, and how it perceives motion. This is sometimes referred to erroneously as "persistence of vision" (which is a separate effect not as important for movies and games as was once believed). Basically, your brain is willing, under certain circumstances, to "fill in" the gaps between frames of a movie/game. The higher your framerate, the more likely your brain is to do this, but it also depends a lot on what it is (or thinks it is) seeing. So in some situations, you'd never be able to tell the difference between 30 and 60 FPS (or even lower; most movies are shot at 24 FPS IIRC), while in others you could have much higher FPS while still preventing your brain from seeing it seamlessly.

A good example of this is if you rotate the camera quickly in Oblivion - the greater the difference from one frame to the next (because you've spun that much), the more likely your brain is to see the two as separate images rather than movement from one to the next. In reality, I'm pretty sure you can spin fast enough in Oblivion that your brain will see the two as separate images even at extremely high (~200 FPS) framerates. Of course, the fact that Oblivion may also lag slightly when you spin suddenly as it has to paint a lot of new things it wasn't worrying about before also contributes to this. Various effects like motion blur can cause your brain to accept the same "motion" that it wouldn't before. Again, there is no hard number, it's all about what your brain thinks it's seeing.

An opposite example would be very slow movement - even at very low framerates, if the total movement from one frame to the next is low enough, your brain will see it as (very slow) movement. If a large-ish object - several hundred pixels - is moving at a rate of a single pixel per frame (or half a pixel using anti-aliasing, or whatever), you could have framerates as low as single digit FPS and still probably see it as seamless movement.

Since this was the only open and recent Streamline thread, I thought I would bring up my issue here.

I am only using the Streamsave and Streampurge features. I have Streamsaving set to save every 10 minutes, 30 slots. However Streamline saves about once a minute, especially if I'm roaming on horseback, as I've been doing stability testing.

I only have OBGE, OSR, and FastExit 2 installed at the moment.

Anybody aware of Streamline mysteriously disobeying the INI?

IIRC there ase additional settings for streamsave like save on door use, save after combat, etc. Perhaps one of tose?

Also, if you make changes to the ini you have to reinitialize it through the ingame menu (loading a save does not do this, I think it only initializes the ini once when installed, then you have to do a manual initialization).

Hmm, if it counts combat as anytime the combat music starts up. I was on horse and wouldn't even engage anybody... I'll just turn off all of those then. You would think combat implied enemy aggression + your weapons out + enemy getting killed. Not fleeing like I technically was.

It definitely wasn't the second thing you said. I changed the INI before I ever loaded any new games, and it also did the same on new games from that point on. And the default to save was 5 minutes anyway.

But if I try to remember when it was actually saving, I still feel like it was saving every minute on the dot, even when I was on foot and not near enemies...