Open eMSX opened 7 years ago
I think the problem is on your end -
"RetroArch [INFO] :: [GL]: Vendor: Microsoft Corporation, Renderer: GDI Generic. RetroArch [INFO] :: [GL]: Version: 1.1.0."
If it shows that then it means it can't find a REAL GL driver on your system and it instead resorts to a Microsoft-provided software rendered implementation of OpenGL, which utterly sucks. Don't even bother trying to use it since it will suck majorly, and find valid video drivers instead so that you can get a real GL driver for Windows.
Can confirm, have the same problem with Intel HD Graphics 3000. v1.3.6 works fine. I dunno how to get logs, retroarch_debug.exe also crashes on start (and I can't find any log files?). Setting
menu_driver = "rgui"
in retroarch.cfg fixes it and uses the older GUI. My drivers are up-to-date and I'm on Windows 10 Pro 1607 64 bit.
i can guess 2 reasons:
On Wed, Feb 8, 2017 at 12:55 AM, Andreas Bielawski <notifications@github.com
wrote:
Can confirm, have the same problem with Intel HD Graphics 3000. v1.3.6 works fine. I dunno how to get logs, retroarch_debug.exe also crashes on start (and I can't find any log files?). Setting menu_driver = "rgui" in retroarch.cfg fixes it and uses the older GUI. My drivers are up-to-date and I'm on Windows 10 Pro 1607 64 bit.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/libretro/RetroArch/issues/4580#issuecomment-278063313, or mute the thread https://github.com/notifications/unsubscribe-auth/AWPDtiKYyJC75lBCoALbhhCtDUI3bDBQks5raKICgaJpZM4L4nf2 .
I have also tried it on my Laptop an Acer V571G (also featuring a Sandy bridge cpu with GMA 300 HD. When i disable the Nvidia GPU it is giving the same error als the tablet.
It is failing the reconize the Intel 3000 adapter. The drivers are the ones installed by Windows 10 by default. 9.17.10.4229 on Windows 10 home 1607
Here 1.3.6 also works fine on the intergrated gpu.
You may try the latest driver version 9.17.10.4459 available for Win10.
I have installed that driver but Retro Arch still crashes directly when started.
I also did the installation and stillI have same issue.
Can you try to install Win8 driver ? Thank you.
Man, install newer driver, older driver it's all same. This error persist.
@loganmc10 There's anything I cany do? I am sorry, I am just a noob.
Can someone with an affected system try this MSVC build and see if it works any different?
From the previous log, the line:
RetroArch [ERROR] :: [WGL]: wglCreateContextAttribsARB not supported.
is very peculiar since 1.3.6 also uses this function and it appears to work fine there. The entire reason for the crash is due to the failure to look up the pointer to that function in the OpenGL library. Since an OpenGL context cannot be created with the missing function, any further attempts to call a GL function will crash.
At first I would have also suspected a system driver issue, but I don't think this can be if 1.3.6 works.
@bparker06, thank man, it does works but doesn't load any core and any game.
Then I suspect the issue may be related to some GL code that gets compiled on msys2 builds that doesn't on msvc, like glslang or something.
You'll have to start bisecting.
loganmc10 pushed through some extensions in RA that enable certain graphic features but this apparently was not properly tested against most common hardware as we can already see certain iGPUs no longer working on Windows.
@Mohamed28 The build I linked you to is 32-bit, so it will only load 32-bit cores.
Can you also try the 32-bit version of the current msys2 build and see if that works?
Until someone with the same/similar hardware, and the knowledge, time and patience to be able to bisect this comes forward, I don't think a whole lot of progress can be made, simply because we cannot reproduce it elsewhere.
@bparker06 version 1.4.1 x86 working fine...thnx man... I tried latest nightly but with same error...
@sm199 Were you trying an x86 nightly or was it an x86_64 one that didn't work? Trying to narrow down exactly what versions work and what doesn't.
@bparker06 i tried both versions...recently downloaded both versions but they are not working...
So neither nightly works, and 1.4.1 x86 works, what about 1.4.1 x64? And have you tried the MSVC build I linked to? That one is more recent than 1.4.1 as well.
I tried your MSVC build so x86 version worked...before it was not working... x64 build not working...xmb menu successfully opened but no cores are working because that exe belongs to x86...
Sorry for bad english...
I found a machine here with an hd3000 and tried it myself, and it is working here: https://i.imgur.com/YdBYAZe.png
This is the latest 64-bit nightly also. Driver version is 9.17.10.2932 on Windows 7 with i7-2600k.
I don't know mine is intel hd 3000 or not...how to check it...???
I tried both latest nightly builds on windows 10 64 bit...with latest video driver installed...
@sm199 Right click on the desktop -> Display settings -> Advanced display settings -> Display adapter properties
Okk i will check it and post screenshot here...
@bparker06 I tested here, version 86x with your file works fine, the cores and games also worked. I used the yabause_libretro.dll to do the test.
@Mohamed28 Are you saying the 32-bit MSVC build works or the 32-bit msys2 one works? And have you tried both?
I have also being testing. the 32 bit MSVC works perfect, the 32 bit msys2 gives the same eror. Also the nightlys of 10-2 are giving the same error.
@bparker06 It is not showing anything about 3000.it is showing intel hd graphics only....u can see screenshot here... http://imgur.com/a/ivFe6
@sm199 HD3000 was the built-in IGP for the Sandy Bridge line of i-series CPUs. If you can look up what series your CPU came from, that should tell you.
@bparker06 Yes man, actually I tried your file in both x86 and x86_64 in both it makes the GL works, but only in x86 runs cores and games.
@Mohamed28 did you try 32 bit msys2...???
@sm199 Yes, I did sir, it's working. I did as @bparker06 has requested.
U mean u tried latest nightly not v1.4.1,right...???
@sm199 Yes, sir. The latest nightly from yesterday.
Okk now nightly is working fine for you but i am having the same error...only MSVC 32 bit build working fine... :(
I have an automatic msvc build setup here:
https://s3.amazonaws.com/retroarch/RetroArch-x86-msvc2005.exe
Works on all Windows versions from 98 and up.
It rebuilds every hour if there's any code changes on the master branch. At least it is something until we can figure out what's going on with the msys2 builds.
Thanks @bparker06 but how to use it...??? Should i have to copy this in current nightly build...???
You can run the exe by itself anywhere, or you can put it in an existing folder that you had from a nightly, sure.
So you mean all the nightly buids will work now...??? :D
And will i have to download it everytime when i will download latest nightly or upcoming stable build till it fixes...and thank you so much @bparker06 ...
I don't quite follow what you're saying but, whenever you want a newer build you can just re-download that same exe, and keep it in the same folder, overwriting the old one. You don't have to re-download any actual nightly stuff from the buildbot, just my exe.
@eMSX can you just build from source? it takes a while, and bisecting is a PITA I know, but it's the only way to get to the bottom of it. Build guide https://bot.libretro.com/docs/compilation/windows/
Once you can build you have to bisect https://git-scm.com/docs/git-bisect
I'm able to complile retroach, but i am experiencing some black blocks in front of the menu's.
The bisecting doesn't go according to plan.
I am receiving some errors:
$ git bisect bad ': is geen geldige naam: regel 88: export: 'dashless Bisecting: 2949 revisions left to test after this (roughly 12 steps) error: Your local changes to the following files would be overwritten by checkout:
but even if i say bisetct bad, is doesn't give me less revisions te test.
That error is telling you that you have modified the source of the current commit you're on, so the bisect will not continue until you remove those changes.
I have been bisecting till there isn't a single version left to test, with no luck, it still crashes directly after loading, while on my nvidia machine's it runs without issue. Even the 1.3.5 which i build crashes.
$ git bisect bad 7191465dcb038ce77991238a24e01bc91901cbfe is the first bad commit commit 7191465dcb038ce77991238a24e01bc91901cbfe Author: Mikael Brunnhede mbrunnhede@hotmail.com Date: Sun Jul 17 12:15:44 2016 +0200
Fix bug in calculation of blocksize for savestates.
:040000 040000 0f8cef8d38a74224f54e36cbc31f971bab36059c e923966015f4721398342eea3f536d7901ff9fc6 M managers
Has there been a change in the way retroarch is compiled since 1.3.6 ?
Please note that i am by no means a programmer, just a guy who read the above tutorials to compile his first program since "the game of life" in turbo pascal at school.
@eMSX If the bisect is done correctly then the commit right before "the first bad" one should work. Can you confirm this?
Also, how is it that you narrowed done a commit from July if 1.3.5 crashes too?
I have a intel3000-Windows10ProX64, with the issue here. Let me know if I can help test whatever is wrong. I changed video driver = d3d in the cfg and it doesn't have any graphics like PSP's XMB but the program opens up. It plays VBA-M games just fine the GUI is fairly non-existent or not pretty in d3d mode though.
The .4229 is the latest driver from intel direct, what ever is on microsofts site isn't officially supported for my i5-2520m. I tried the newer one above with no luck the installer prompts to allow, then quits itself realizing that my version is the MS approved one.
Hello guys, i am having trouble with the latest version of Retroarch.
Retroarch 1.4.1 crashes directly when opened. Error message retroarch.exe stopped working.
Version 1.3.6 runs fine and reconizes the HD 3000 graphics drivers. When i run 1.4.1 it crashes immediatly
I am running Windows 10 home 64 bit. I have tested both the 32bit and the 64 bit versions, makes no difference.
I am running it local, not using RDP.
The hardware is an Acer W700 tablet running Windows 10 home 1607 with all updates
Intel(R) Core(TM) i3-2375M CPU @ 1.50GHz Intel HD Graphics 3000 Driver version 10.17.10.4229 Also tested with version 9.17.10.4229 same issue
Here is the debug log.
Here is the log of the working 1.3.6 on the same system.
If more info is required i am happy to help.