-
Notifications
You must be signed in to change notification settings - Fork 382
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
Am I missing something? Can't run devbuild 2c6129fb #3939
Comments
It sounds like you overwrote your existing installation with the dev version. Please extract the bizhawk dev version into a separate folder and try launching it again. |
I'm going to close this due to inactivity. Please report back if you still have issues. |
Uh I almost forget this😂… So now I downloaded 90c79d2 then create an empty folder and put BizHawk in, but still can't open, EmuHawk.exe just stay a short while (using Task Manager to see) then disappear for no reason. |
Do you see any error message at all? If not, is there any error message related to Another thing you could try is download a debug build from Gitlab (directlink), open the folder in powershell (shift-rightclick the background in the explorer window and select |
Yeah this is something in the new D3D11 code failing when querying information about Direct3D<->OpenGL interop methods. Could you tell me what graphics card / cpu you're using? Also, are your drivers up-to-date? @CasualPokePlayer any other ideas? |
That seems like some kind of bug within the driver itself, which is extremely strange. Does the machine have multiple GPUs? If so, could you check if force enabling the dedicated GPU in Windows settings ends up changing anything? |
Intel HD4600, driver is not up-to-date for stable reason, my laptop has GTX850M (GPU only) but I not enable it to render BizHawk by default. |
Could you try to force it to use the GTX850M and see if it still crashes or not? If it doesn't, it sounds like BizHawk just needs to try to check if the OpenGL GPU is the same as the D3D11 GPU. |
Then my theory is right, the OpenGL driver was using the Intel iGPU and D3D11 was just using the GTX850M instead, and the extension ended up crashing due to not gracefully handling the difference (thanks Intel). Shouldn't be too hard to fix per se, just need to try to avoid using the extension if we detect the GPUs between the APIs are different. |
From 2.9.1 stable to 2c6129f dev, first time I run it, config file corrupted then deleted it. Later it won't pop up anymore, am I missing something? Windows 10 1809 64-bit.
The text was updated successfully, but these errors were encountered: