Ebitengine Version
760e6b9ebd228554bed191410ce47d8a93a329dd
Operating System
- [X] Windows
- [ ] macOS
- [ ] Linux
- [ ] FreeBSD
- [ ] OpenBSD
- [ ] Android
- [ ] iOS
- [ ] Nintendo Switch
- [ ] Xbox
- [ ] Web Browsers
Go Version (go version)
1.19.1
What steps will reproduce the problem?
Note: This is a developing Issue that I will try to update when I gather more information.
One of my players (and probably more) are experiencing "unpleasant" experience on DirectX, that is low FPS, lags between frames, and most importantly white screen (not responding state).
Given that this player's machine is quite good, and on OpenGL everything is perfectly normal (2 white screens during 4 hours on dx, and no white screens on opengl for 15+hours and counting).
His dxdiag:
DirectX having observable worse performance than OpenGL on this particular machine is repeatable, and there is no shadow of a doubt that OpenGL is much better for this particular player.
I have no evidence that this not responding state is because of ebitengine's DirectX, there are more players who reported this issue but I did not ask about details, I will from now on and I'll update this Issue to gather as many informations as possible.
What is the expected result?
No "not responding" state, better DirectX performance.
What happens instead?
Measurably worse DirectX performance on Windows.
Anything else you feel useful to add?
I don't really expect anyone to do something with this case right now, as I already mentioned I'll treat this Issue as a documenting page for my observations regarding those issues, especially the "not responding" state since there are a couple of players who reported that and I don't think that this is my game's fault since most of the players are doing the same activities, and only a handful of them are reporting such scenario.
