New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
internal/graphicsdriver/directx: DirectX can be unexpectedly chosen even when the feature level 12 is not supported #2478
Comments
Thank you for reporting!
What about the latest version?
This seems pretty odd... Isn't this an OpenGL operation? I'll take a look
This seems a device lost. Isn't the actual device unstable? TBH I have no idea how to fix this 🤔 |
I'll try to upgrade to the latest version during my next client update, but I can't guarantee that those players will be still playing 😄 |
Fixed the first issue at 15c2fe0. As this bug seems pretty rare, I will not backport this to v2.4, maybe (and I believe you are using v2.5) |
thank you! there is no need since I'll just use the HEAD. |
Hm, I'll take a look further tomorrow. I'm gonna sleep soon.. |
Nothing so far, thanks! |
you are great, thank you so much! 😊 |
I can confirm that the third one happens whenever I move a file over the game window. |
This is in #1868 |
So now the remaining issue is
but, as I have already said, I have no idea how to fix. Probably there is nothing we can do... |
@erexo Does this happen when lancuing a game, or during a game? |
Currently It's hard to say, because the "I was playing for a while and then suddenly the game stops" was probably describing the third panic, but when that player sent me his logs I also discovered this one. There is a good chance that it happened during game launch.
So is there an option to disable it? |
Ebitengine doesn't have a feature of drag and drop so far. We might have a new one in the future, but you can ignore it if you don't use it. I have already fixed the crash anyway. |
I can confirm that the 2nd error is still viable at 6a0eb82 . |
In the machine, as DX12 is not supported directly, OpenGL should be used. Does this bug still occur with the newest commit? |
What did you specify |
It was set to "auto", so DirectX was actually used and launched, but during game the game crashes. When it's set to "opengl", it works fine |
The latest version should not choose DirectX as Ebitengine tries to choose the feature level 12(#2447), and this machine doesn't seem to support it. Please try the HEAD version. |
That player tested the game on 760e6b9, and the problem persists. |
That's pretty odd. This GPU doesn't support the feature level 12, right? |
|
Now Ebitengine supports feature level 11 for DirectX, this should no longer be an issue. |
Ebitengine Version
b3be334
Operating System
Go Version (
go version
)1.19.1
What steps will reproduce the problem?
A few of my players reported, that while running my game on DirectX the game suddenly and without any observable reason closes. I can't really force them to look deeper on what could cause this, but every player is claiming that they are not doing anything special in particular, and the game will crash after ~5-20 minutes after launching.
There are two distinctive errors and I'm not sure how related they are:
First error reported by 2 players:
EDIT(hajimehoshi): See #2481 for this issue.
Second error/s reported by one player:
EDIT(hajimehoshi): See #2480 for the latter issue.
Only a few players reported those errors, I couldn't get their system specs or directx status, and when they switched to OpenGL everything is working as intended.
What is the expected result?
Game does not crash
What happens instead?
ebiten.RunGame
return errorsAnything else you feel useful to add?
As OpenGL is working fine for them and they can play normally, that's the another "I told you" about usefulness of having the ability to switch the engine.
The text was updated successfully, but these errors were encountered: