A while back someone reported that the MWRender refactoring resulted in a significant FPS drop in exteriors. I am semi-convinced now that such a slowdown exists. I would like more input from other other developers. Do you see such a slowdown too? And if yes, anyone any idea what is causing it?
I have two branches in my repository (mwrender and nomwrender) that should offer a convenient way to compare performance. Don't use the master branch, because it contains other rendering stuff that will affect FPS:
MWRender slowdown
Re: MWRender slowdown
70-420 in interiors
20-250 in exteriors
in both branshes
If i look at all objects in the cell the fps goes down to about 20fps. When I look at a wall directly in front of me and all other objects are behind the wall the frames are still low. If I look into the sky the fps gets around 250fps. I dont know... but should'nt it ignore whatever is behind the wall?
20-250 in exteriors
in both branshes
If i look at all objects in the cell the fps goes down to about 20fps. When I look at a wall directly in front of me and all other objects are behind the wall the frames are still low. If I look into the sky the fps gets around 250fps. I dont know... but should'nt it ignore whatever is behind the wall?
- lgromanowski
- Site Admin
- Posts: 1193
- Joined: 05 Aug 2011, 22:21
- Location: Wroclaw, Poland
- Contact:
Re: MWRender slowdown
Hi,
I don't see any major difference in fps between mwrender branch and nomwrender branch on integrated Intel video card (fps is between 29 and 60 frames).
I don't see any major difference in fps between mwrender branch and nomwrender branch on integrated Intel video card (fps is between 29 and 60 frames).
Re: MWRender slowdown
Okay then lets chalk up the FPS variations I saw to measurement errors for now.
Re: MWRender slowdown
I experienced such slowdown. I profiled app and looks like that there is problem with bullet (strange?).
Here is profiling report https://gist.github.com/311bb9c9d6bae6aafbbd
I just can't move in exteriors ~1 fps.
P.S. I'm using bullet 2.79
UPD:
tried nomwrender... no luck, looks like bullet issue. I'll try to fallback to older version.
UPD2:
On bullet 2.77 everything is ok.
Here is profiling report https://gist.github.com/311bb9c9d6bae6aafbbd
I just can't move in exteriors ~1 fps.
P.S. I'm using bullet 2.79
UPD:
tried nomwrender... no luck, looks like bullet issue. I'll try to fallback to older version.
UPD2:
On bullet 2.77 everything is ok.
Re: MWRender slowdown
That is a known issue. A regression in bullet (newer than 2.77 I think).
- psi29a
- Posts: 5361
- Joined: 29 Sep 2011, 10:13
- Location: Belgium
- Gitlab profile: https://gitlab.com/psi29a/
- Contact:
Re: MWRender slowdown
When the release 0.12 is out the door, can we also release a list of libraries to compile against for the package maintainers? I would hate to make a release using the wrong/buggy libraries.
known good libraries:
libbullet = 2.77
known good libraries:
libbullet = 2.77
Re: MWRender slowdown
I think there is such a list in the wiki. But it probably needs updating.
Re: MWRender slowdown
Cheers for posting this. I was having real problems in exteriors.corristo wrote:I experienced such slowdown. I profiled app and looks like that there is problem with bullet (strange?).
Here is profiling report https://gist.github.com/311bb9c9d6bae6aafbbd
I just can't move in exteriors ~1 fps.
P.S. I'm using bullet 2.79
UPD:
tried nomwrender... no luck, looks like bullet issue. I'll try to fallback to older version.
UPD2:
On bullet 2.77 everything is ok.
- sirherrbatka
- Posts: 2159
- Joined: 07 Aug 2011, 17:21
Re: MWRender slowdown
swick said that the problem is fixed on the recent svn revision of bullet as well.