I upgraded my pc 2 days ago from windows 7 to windows 10 , and when i open a rom with the gba emulator it only loads the sound of the game, how can i fix this? The emulator worked fine before the upgrade!
mGBA-0.6.3-win32
- Thread starter tall guy
- Start date
- Views 2,999
- Replies 20
Sounds like a problem with your graphics driver (just a wild guess). Download the latest official driver from the manufacturers homepage – hopefully Windows 10 drivers exist. I read about this problem before. It was a while ago:
https://github.com/mgba-emu/mgba/issues/274
You could also try the latest beta version of mgba but I don’t think it will change anything.
https://github.com/mgba-emu/mgba/releases/download/0.7-b1/mGBA-0.7-b1-win32.7z
https://github.com/mgba-emu/mgba/issues/274
You could also try the latest beta version of mgba but I don’t think it will change anything.
https://github.com/mgba-emu/mgba/releases/download/0.7-b1/mGBA-0.7-b1-win32.7z
You already mentioned it started after the upgrade Win 7→ Win 10.
Flame asked about your hardware.
What computer are you using? Especially: What graphics card/chip is in your computer?
In the old issue 274 endrift (the author of mgba) could not reproduce the error and suspected the graphics driver to be the cause. I can only repeat my general advise: Download the latest available driver for your GPU.
He's from this thread:
There are lots of missing details in this summary, but...
He tried to custom inject a Pokemon rom hack on his Windows 7 desktop using an outdated version of Asdolo's GBA VC injector. That didn't work for his 3DS due to save issues. Then, he tried using the newest NSUI injector but that didn't work in Win 7 due to some GUI menu bug, so he updated to Win 10 to fix that. Now, he can't use the desktop mGBA emulator on Win 10 because of a (supposedly) unknown driver issue as per @KleinesSinchen's GitHub link.
***
As for why he down
If the mGBA video bug can't be fixed, I personally think he should
Of course, this is assuming OP doesn't have any technical, moral, or financial setbacks that prevents him from switching to that older version of Windows.
this is my graphics card:
Manufacturer NVIDIA
Model GeForce 6200 LE
don't realy know which one to download, i'm on windows 10 home 32 bit.downloaded the latest driver but still the same problem.
Last edited by tall guy,
I thought as much. GeForce 6xxx and 7xxx series have been moved to the legacy branch of the NVIDIA driver about February 2015. Windows 10 was released… end of July 2015.
So you can guess it: no official Windows 10 drivers. Grrrr! And lost of people complaining in various forums. You can however try this one. A video on YouTube claims it will work without issues under Win 10 (uninstall any other NVIDIA drivers before):
https://www.nvidia.com/Download/driverResults.aspx/82829/en
If you do not trust the video or me (and you should not trust strangers on the internet) You get to this link in the driver download section by selecting:
Product Type: GeForce
Product Series: GeForce 6 Series
Operation System: Show all Operating System and then select Windows 8 32-bit
Use it on your own risk. If you want, I can do a limited test for you. I have a lot of old computers and one with a GeForce 7xxx. Just report back. If you want me to do this, I’ll install Windows 10 on this machine and try mgba before and after installing the above driver. I have to emphasize the word limited test once more because I’m not familiar with modern Windows. And it will take a day.
So you can guess it: no official Windows 10 drivers. Grrrr! And lost of people complaining in various forums. You can however try this one. A video on YouTube claims it will work without issues under Win 10 (uninstall any other NVIDIA drivers before):
https://www.nvidia.com/Download/driverResults.aspx/82829/en
If you do not trust the video or me (and you should not trust strangers on the internet) You get to this link in the driver download section by selecting:
Product Type: GeForce
Product Series: GeForce 6 Series
Operation System: Show all Operating System and then select Windows 8 32-bit
Use it on your own risk. If you want, I can do a limited test for you. I have a lot of old computers and one with a GeForce 7xxx. Just report back. If you want me to do this, I’ll install Windows 10 on this machine and try mgba before and after installing the above driver. I have to emphasize the word limited test once more because I’m not familiar with modern Windows. And it will take a day.
Correct. This was it. Forgot to link. Mea culpa.
@tall guy | I found yet another computer with a GeForce 6600 (Yeah!) currently with Ubuntu 16.04 and the 304.131 drivers. Just tell me if I should do the test. It is a lot easier with that computer because it is not in use for anything. Could easily erase the hard disk.
Okay. Don't expect the results before tomorrow. I've work to do now and will install Windows 10 afterwards.
Done. Faster than I thought. Just a short test, but my post is nevertheless long.
Test computer:
=============
Mainboard: ASUS A8V; 2GB DDR1 RAM (PC400)
CPU: Athlon 64 3700+ (this was still a single core processor)
GPU: GeForce 6600, 256MB RAM
HDD: old Maxtor 250GB (seems to be failing but the drive does not matter anyway)
Operating system 1:
=================
Windows 10, 32-bit, Version 1803, Build 17134.112
Operating system 2:
=================
Windows 8, 32-bit
Both were used offline. Each was a fresh install on an empty hard drive. No personal configuration, no updates, no software installed besides 7-Zip (because Windows is too stupid to open mGBA-0.6.3-win32.7z)
Test 1 Win 10 (no graphics driver)
============================
Windows complains at the first login about missing display drivers and tries to find them (good luck, you’re offline!). The video card is described as “Basic Display Adapter” in the device manager.
mgba just crashes immediately after loading any rom. Software rendering with Qt is possible, but a little to slow. The CPU manages around 50fps – 55fps in GBA games; (S)GB(C) are okay. A faster CPU might be able to reach 60fps.
Test 2 Win 10 (with NVIDIA driver 309.08)
==================================
The driver installed without any problems. The graphics card is now labeled with NVIDIA GeForce 6600. The NVIDIA settings work.
Sadly the results in mgba were not different to those @tall guy got on his machine. Qt Software rendering works, but slow; with openGL the sound plays without video. This was until I became angry and desperate, so I hammered down Alt+Return for fullscreen! There it was! Audio and video. Only the fullscreen mode worked with openGL. On my computer all test-games were playable. Sometimes there was a slight drop in the frame rate, but for the most it was good. I had no controller andI suck I’m not good at playing with the keyboard, so these were very brief tests. CPU load stayed at approximately 50% while playing Aria of Sorrow.
Test 3 Win 8 (no graphics driver)
===========================
Exactly the same results as in Test 1. mgba only crashes (openGL). The graphics card was named “Microsoft Basic Display Adapter” this time.
Test 4 Win 8 (with NVIDIA driver 309.08)
=================================
Similar results to Test 2. Only difference: The window-mode works as intended. Any windows size is possible. Fullscreen works as well. Performance seems to be the same as under Windows 10. I noticed the same slight drops in frame rate. Not better, not worse.
I've no idea why everything is okay under Windows 8.1 and under 10 only fullscreen. Like I mentioned before: I'm not familiar with modern Windows and have no clue where to look next.
Done. Faster than I thought. Just a short test, but my post is nevertheless long.
Test computer:
=============
Mainboard: ASUS A8V; 2GB DDR1 RAM (PC400)
CPU: Athlon 64 3700+ (this was still a single core processor)
GPU: GeForce 6600, 256MB RAM
HDD: old Maxtor 250GB (seems to be failing but the drive does not matter anyway)
Operating system 1:
=================
Windows 10, 32-bit, Version 1803, Build 17134.112
Operating system 2:
=================
Windows 8, 32-bit
Both were used offline. Each was a fresh install on an empty hard drive. No personal configuration, no updates, no software installed besides 7-Zip (because Windows is too stupid to open mGBA-0.6.3-win32.7z)
Test 1 Win 10 (no graphics driver)
============================
Windows complains at the first login about missing display drivers and tries to find them (good luck, you’re offline!). The video card is described as “Basic Display Adapter” in the device manager.
mgba just crashes immediately after loading any rom. Software rendering with Qt is possible, but a little to slow. The CPU manages around 50fps – 55fps in GBA games; (S)GB(C) are okay. A faster CPU might be able to reach 60fps.
Test 2 Win 10 (with NVIDIA driver 309.08)
==================================
The driver installed without any problems. The graphics card is now labeled with NVIDIA GeForce 6600. The NVIDIA settings work.
Sadly the results in mgba were not different to those @tall guy got on his machine. Qt Software rendering works, but slow; with openGL the sound plays without video. This was until I became angry and desperate, so I hammered down Alt+Return for fullscreen! There it was! Audio and video. Only the fullscreen mode worked with openGL. On my computer all test-games were playable. Sometimes there was a slight drop in the frame rate, but for the most it was good. I had no controller and
Test 3 Win 8 (no graphics driver)
===========================
Exactly the same results as in Test 1. mgba only crashes (openGL). The graphics card was named “Microsoft Basic Display Adapter” this time.
Test 4 Win 8 (with NVIDIA driver 309.08)
=================================
Similar results to Test 2. Only difference: The window-mode works as intended. Any windows size is possible. Fullscreen works as well. Performance seems to be the same as under Windows 10. I noticed the same slight drops in frame rate. Not better, not worse.
I've no idea why everything is okay under Windows 8.1 and under 10 only fullscreen. Like I mentioned before: I'm not familiar with modern Windows and have no clue where to look next.
Last edited by KleinesSinchen,
@KleinesSinchen, great job! I dropped a mention of you back at that mGBA GitHub issue. Maybe it'll lead to pinpointing a fix with scale-able, working screen.
Edit - Oo! * Additional testing.
Edit - Oo! * Additional testing.
enddrift said:
Last edited by TurdPooCharger,
Can confirm this: force 1.x makes no difference. On Windows 8.1 both openGL settings fully work, on 10 both only in fullscreen mode.
A little update (again using Windows 10 32-bit, Version 1803, Build 17134.112): Maybe the problem in this thread is not on the side of mgba. Now… How to express that? Only vague. Something with the interaction: Windows 10, OpenGL and this old NVIDIA driver/card is fishy.
I installed OpenGL Extensions Viewer. According to this program, the GeForce 6600 has EXT_framebuffer_object. More interesting than the detailed list of what functions the card has or not, was the graphical test:
Any attempt to draw the test into a window resulted in nothing but a window containing the last picture, that was on the screen at this place (much like the mgba window that only contains its logo). But in fullscreen mode it worked. In both cases the program reported success and gave details about fps although nothing was visible in window mode.
I had to use a poor camera for the fullscreen screenshot AND have no tripod AND this tremor in my hands AND converted it down before uploading… so the picture of the old CRT monitor looks like sh…
I installed OpenGL Extensions Viewer. According to this program, the GeForce 6600 has EXT_framebuffer_object. More interesting than the detailed list of what functions the card has or not, was the graphical test:
Any attempt to draw the test into a window resulted in nothing but a window containing the last picture, that was on the screen at this place (much like the mgba window that only contains its logo). But in fullscreen mode it worked. In both cases the program reported success and gave details about fps although nothing was visible in window mode.
I had to use a poor camera for the fullscreen screenshot AND have no tripod AND this tremor in my hands AND converted it down before uploading… so the picture of the old CRT monitor looks like sh…
Similar threads
-
-
@
SylverReZ:
@Maximumbeans, Indeed. I've been working on getting this Infecutus chip to work on my PS2. But after soldering, I realised that a plastic piece was missing from the power ribbon cable to the power and eject buttons. -
@
SylverReZ:
Now I could go with soldering the contacts from the cable to the connector on the mobo, but doesn't sound like a good permanent solution.
-
@
Maximumbeans:
Man, that's beyond my brain
I'm no good with hardware for now. I'd like to get into hardmods in future though -
@
SylverReZ:
@Maximumbeans, Maybe start practice soldering. Get a cheap-ass soldering iron and follow some good YouTube tutorials.+1
-
@
SylverReZ:
Least my experience has gotten better than over a decade ago. My iron would constantly bump into components and break them.
-
@
Maximumbeans:
Sounds good. I actually did soldering but like 16 years ago for school so uuuuh probably rusty haha
-
@
SylverReZ:
@Maximumbeans, Same here. I did soldering at school from a teacher who I honestly liked since he had plenty of good electronics experience.+1
-
-
-
-
-
@
SylverReZ:
It was like all clear and fancy. Tbf I'm not too experienced with chess, but would like to learn someday.
-
-
-
-
-
-
-
-
-
-
-
-
