Benchmarks / Hardware Specs

General discussion regarding the OpenMW project.
For technical support, please use the Support subforum.
User avatar
Posts: 2152
Joined: 18 Feb 2012, 11:51

Re: Benchmarks

Post by scrawl » 30 Nov 2015, 22:08

Repeating test from a week ago, with the recent changes to master.

openmw commit e5ec4fe042f34a163c441b9de7ab04be1e8377c6
scrawl/osg commit c69b3ac6b43b37577053ad9197394dac1f00b26b

water shader = ON


200 fps (previously 193 fps, improvement = 3.6%)

Not too much of an improvement here because we're starting to hit a draw bottleneck.

water shader = OFF


295 fps (previously 230 fps, improvement = 28%)

I'm pretty sure we should be faster than vanilla MW by a decent margin now.

Posts: 14
Joined: 05 Dec 2015, 21:01

Re: Benchmarks

Post by Ferik » 05 Dec 2015, 21:20

So, this isn't technical benchmarks but I do think it shows just how fast the OSG version is considering it's capable of this with my somewhat middling GPU.

I modified my settings.cfg file to force some extra draw distance. Despite this I was still running smooth.

What I changed were these lines:
viewing distance = 6666 ==> viewing distance = 14000
exterior cell load distance = 1 ==> exterior cell load distance = 2

The end result, at least I think (I'm not very programing inclined actually), is the game is forced to generate exponentially more terrain and objects at once without the benefit of LODs or anything of the sort. Is that correct? In any case, despite this my computer is still managing to hold 60fps in most instances with vsync on and drops somewhere to an average in the lower 50's in particularly bad areas like Balmora. Overall still entirely manageable.

I'm currently running:
Windows 7 64-bit
Intel Core i7 4790k at its base clock of 4.0GHz
16 GB of Kingston DDR3 at 1866
EVGA Nvidia 670 GTX FTW (the 4gb edition)
and Morrowind is installed to a 7200 RPM WD Blue Drive

Posts: 6
Joined: 29 Sep 2014, 09:12

Re: Benchmarks

Post by rlilewis » 16 Dec 2015, 20:12

OK well i've repeated my tests from 0.36.1 build in comparison to new 0.37. Using the same position as shown in Scrawl's screenshots.

Win7 x64
8GB Ram
GTX 770
i5 4690K @ 4GHz

1680x1050, FOV 90, water shader on, reflections on, draw distance max. I am using texture packs.

0.36.1 - Getting 36 FPS
0.37 - Getting 75 FPS

I haven't seen it once drop below 70FPS when roaming around. Very nice job indeed! 8-)

I'm genuinely excited about future graphical options with this new engine, for the first time I'm actually able to play Morrowind consistently above 60fps with a bunch of texture packs and trees etc, i'm drooling at the prospect of shadows and distant terrain. :D

Posts: 428
Joined: 21 Nov 2013, 13:20

Re: Benchmarks

Post by ezze » 17 Dec 2015, 02:29

But, there is any reason to go over 60 fps? It is not already much higher than what human eyes can perceive? I am asking because I am not sure.

Posts: 186
Joined: 19 Sep 2014, 13:37

Re: Benchmarks

Post by Cramal » 17 Dec 2015, 03:55

Higher than 60 fps is not really usefull, but being sure to never go under is pretty appreciable

Posts: 1579
Joined: 04 Sep 2011, 08:33

Re: Benchmarks

Post by Chris » 17 Dec 2015, 04:10

ezze wrote:But, there is any reason to go over 60 fps? It is not already much higher than what human eyes can perceive? I am asking because I am not sure.
The human eye doesn't work in "frames". Frames are discrete-time samples, while the eye works with continuous light waves that get filtered into brightness and color information for the brain. You can't really measure the way the eye works in terms of a frame rate (though even if you could, it would require hardware that can properly reconstruct continuous signals from discrete-time samples/frames over a period of time, rather than just displaying each frame as it comes in).

User avatar
Posts: 1851
Joined: 26 Nov 2015, 03:25

Re: Benchmarks

Post by AnyOldName3 » 17 Dec 2015, 04:32

A decade ago or so, the US air force did an experiment involving 220 Hz displays to test what the minimum framerate required to fly a fighter jet with a screen instead of a window was. Every pilot could easily identify details in an image flashed for a single frame, so the project was postponed indefinitely until display technology improves enough to try again. The average person may not be as fast as a fighter pilot, but it's not likely that they're a whole four times faster than everyone else (which would be the case if 60 FPS was enough for everyone).

The gist of the arguments that humans can only see at around 20-40 FPS is that individual light receptors in your eyes can only fire around that often, but because you don't actually see in discrete frames, all these receptors are out of sync with each other, and your brain can piece everything together much in the same way as a STAMP camera. (These were in the news a bit ago for recording light travelling at 4.4 trillion frames per second, but they actually work by recording the footage at about 10,000 FPS and then repeating the experiment another 100 million times, starting the camera slightly later each time, letting you display the first frame of each recording, then the second of each and so on.)

As for why movies work (mostly) fine at only 24 FPS, it's because cameras record all the light they receive over nearly a whole 24th of a second, which makes each individual frame pretty blurry if anything's moving, but gives your brain enough information to fill in the blanks (it's not dissimilar to what it'd have to do if you were drunk or very tired). In a game, though, a frame is (almost always) just a single snapshot in time, and doesn't have any motion blur, so it looks more like objects are hopping from point to point, instead of moving smoothly. This can even be enough to make some people nauseous. When rendering graphics for movies, they do so at around 240 FPS, and then blur sets of ten frames together to get rid of this effect, but there's not enough time to do this in real time for games. Some games try and blur objects that are moving, and it can help, but it's not as good looking as doing things properly.

One final tidbit: While I'm not sure how much I believe this, some bungee jumpers have reported being able to see individual milliseconds count up on their watches while in freefall. If this is true, it's yet another crazy thing that adrenaline can do to a person.

tl;dr: 60 FPS may well be 'enough', but humans can definitely see more.
AnyOldName3, Master of Shadows

User avatar
Posts: 2152
Joined: 18 Feb 2012, 11:51

Re: Benchmarks

Post by scrawl » 17 Dec 2015, 04:42

Comparing movies and games is apples and oranges. In games you actually control the screen, so you have to deal with something known as "input lag". 60 fps may be enough for a fluid picture, but it's not enough for responsive mouse movement. That is why 120/144hz screens are popular these days. Enabling VSync further increases input lag, since frames have to be buffered up before being displayed, making the difference between 60 fps and 120 fps even more noticable.

Even on monitors that can not display more than 60hz, having the game render more than 60 fps still results in reduced input lag.

Video on the subject.

Posts: 84
Joined: 19 Aug 2015, 15:58

Re: Benchmarks

Post by TechNoirMK » 19 Jan 2016, 18:37

New PC:
Core i7-4790k 4.0 GHz, ASUS STRIX GTX 960 2GB, 16GB RAM

1920x1200, AA 4x, everything else maxed out:
Interiors - 400-700 FPS
Exteriors - stable 80-90 FPS, both Seyda Neen and Balmora
[Same FPS without AA.]

Further optimization is post-1.0, right?

Posts: 15
Joined: 02 Jun 2014, 14:21

Re: Benchmarks

Post by dontpokethebear3893 » 23 Jan 2016, 01:48

getting the same performance hiccups as in the 38RC but I found out something interesting. Enabling the water shader doesn't reduce performance when near a lot of water, it somehow reduces performance in the city/town or in major inland areas with a lot on screen. I just started a new game but I'm sure something similar would happen if you were in Balmora

Again I have an amd 8350 and amd 290x OC. 2nd core is maxed out almost all of the time and the only other one that gets significant usage is the 8th core. the other 6 basically don't function in the game at all. I think that there's two problems here:

>the engine is not properly multithreaded
>certain effects like water shaders which should be utilizing the GPU are instead being rendered on the CPU

please let me know if I'm speaking out of my ass or if there isn't a way to solve the issues.

Post Reply