Open hajimehoshi opened 1 year ago
@corfe83 Would it be possible to see the culprit by git-bisect? (I'm gonna bed soon and will reply tomorrow)
Oh, by the way, I assumed this is a regression, but is this correct? (i.e. did the same tab worked with 60FPS before?)
I know the performance has been slow on android for a long time (users complain UI is laggy, mostly). Battle tab and building tab are both affected by this problem. Later I'll try testing with some older ebiten v2 builds to see if it was better at a certain time.
Sure. I think I'll tackle this issue after v2.5 is released, as this is not a regression. (If this is regression, I'll prioritize this)
It's not a regression in 2.5, so tackling in 2.6 makes sense
Could you check the draw calls at the problematic scene by -tags=ebitenginedebug
on desktops?
Is it possible to know the debug log at the heavy screen? This doesn't have to be on Android.
Sorry for the delay. I tried looking into this and I don't think it's a problem now, at least in my testing in 2.7.3. So I think we can close this issue now.
Ebitengine Version
v2.5.0-alpha.12
Operating System
Go Version (
go version
)go version go1.20 darwin/amd64
What steps will reproduce the problem?
Run Idle Armada on Android (Pixel 6 Pro) and show the battle tab.
What is the expected result?
The app keeps 60 FPS
What happens instead?
The app runs with 30-40 FPS.
Anything else you feel useful to add?
This issue is forked from #2375