Azlidor wrote:I'm currently running 0.38 and these are my specs:
Intel G3258 3.2GHz Dual Core
8GB DDR3 Ram
AMD R9 270X 4GB
Windows 10 Pro
SSD
Game Settings
Resolution 1920x1080
Texture Filtering=Trilinear
Anisotropy=16x
View Distance=Far
Water Shader=On
Refraction=On
Texture Quality=High
I was able to get an average of
70 FPS walking around Balmora (exteriors)
390 FPS walking around Balmora (interiors)
Very promising considering my PC is definitely not very powerful, yet got significantly better performance with OpenMW. I'm looking forward to the shaders getting added into OSG. Hopefully this information is beneficial for you all and let me know if I missed any information you'd need!
Perhaps. But 30 fps in interiors is, say the least, unnatural. I have 20 to 40 FPS in Balmora and stable 60 FPS in interiors with entry-level GeForce 610M card on maximal possible "settings", save extending view distance beyond slider and loading more cells.
That is strange, then, my 730 should be slightly more powerful than that. Maybe there is hope for some kind of software solution for my low fps, then. I thought it might be the weak i3 processor, as I think I have read that openMW is often processor limited?
mkborregaard wrote:I thought it might be the weak i3 processor, as I think I have read that openMW is often processor limited?
Press F3 (multiple times) to get more detailed information about where OpenMW is struggling.
My hunch is that your i3 is hanging up on all the physics based code.
My hope is that if we go with bullet3, we can offload a lot of physics to the GPU if it has time to spare. The chances are high that your GPU isn't being taxed very much is mostly idle.
Yes I think that could be true, as changing the graphics settings does not seem to affect the fps a lot. I will try the F3 several times trick once I get home (I am travelling this week), and check it out.
It is good to hear that there may be improvements on the way, especially as I would be keen to experiment with some modding as well!
mkborregaard wrote:I thought it might be the weak i3 processor, as I think I have read that openMW is often processor limited?
Press F3 (multiple times) to get more detailed information about where OpenMW is struggling.
My hunch is that your i3 is hanging up on all the physics based code.
My hope is that if we go with bullet3, we can offload a lot of physics to the GPU if it has time to spare. The chances are high that your GPU isn't being taxed very much is mostly idle.
Hi, I am back now and tried this, an unfortunately it seems to be my graphics card that is not good enough. Here are the stats (in Balmora, settings as before, view distance about 2/3):
FPS 22
Script 0.19
Mechanics 0.99
Physics 5
Event 0.01
Update 1.7
Cull 4.5
Draw 8
GPU 34
Hard to understand why my stats seem so much lower than Grey Fox'. The only mod I have is magic diversity. Turning the water shader off gives me another ~5 FPS and reduces GPU to about 27.
mkborregaard wrote:Hard to understand why my stats seem so much lower than Grey Fox'. The only mod I have is magic diversity. Turning the water shader off gives me another ~5 FPS and reduces GPU to about 27.
Do you have other operating systems installations for comparison? I don't think its that, but you never know.
Just a thought, and I do not even know if thats possible: A script which takes the player through a designated path and records the FPS data might be good for comparison.