mGalaxy forum

Sometimes, when I exit a MAME game, mGalaxy doesn't respond to keystrokes. It happens like 1 in 10 times or so.

What happens is, that I can't move the cursor selecting games. I can open the "top 10" menu, but I can't move the cursor there either. I can also run games, even though the cursor isn't moving on screen, it seems to actually move in "background", so the game I start isn't necessarily the one highlighted.

When I open the filter keyboard, everything returns to normal.

I run Windows 7 64-bits and use an I-pac. I have customised the key mapping scheme for mGalaxy.

v5.0 also acted this way for me. MAME versions 0.149, 0.150 and now 0.152.

Ah yep me too, on others emulators , but I thought it was because I m using a x360 wrapper (perhpas it s same because of the I-pac). All the buttons work except the cursor (up/down/right and left)

But I don't know how to reproduce this bug , it s really rare, and when happen I do like you or with escape key.

edit:
I have just remade the test with 4/5 emulators with 10 roms everytime, no bug
Perhaps a background application ?
Are you using X-padder too ?

Not using any keyboard emulation software or anything. The I-pac runs as a keyboard without any drivers. I don't have any background applications running, and I don't use any scripts.

For me it happens totally randomly, seems to happen in every game on occasion.

For me the cursor actually works, it just doesn't show on the screen.. So if you move down a couple of times and hit start, the game a few rows down will start. So it seems more like a graphics issue than a controller issue to me.

I have an nVidia-card, can't remember exactly which one, probably a GT 630. Could try updating drivers?

And yeah, escape also solves it.

I have an nvidia too, but I don't think it s an hardware problem.

I have made somes others tries, but impossible to have the bug again, sorry.

I'm also having this problem, when returing to mGalaxy the screen seems to be frozen.
Can select and start other game in the background but the sceen stays the same.
(ati card)

I have the same problem (Intel VGA) with the output of mame to mGalaxy nothing left to wait for the next version of the last update was on January 19 from what I remember. How much we will have to wait for the next update that no one will say 

It s really strange, I had this bug before (and on all system but really rarely), but I haven't it since  at least 1 month.
Which one version mGalaxy/Mame have you ?
MaMe 0.148 and mGalaxy 5.2 for me

In Systems.xml my command is Can you reproduce the bug easily ?

i use mameuifx32 + mGalaxy 5.2 Os:W7

I have made a try with  mameuifx64 0.152 still no bug, sorry. I use defaut config, without joypad.
You need to run the game some minutes to have the bug ? I just wait 1 mn to check.

I finally had it again yesterday with kega/fusion.

Sames symptom, to unlock it I have.
1 - press ESC > The emulator window appear but 50% transparent, all command/mouvement still invisible.
2 - press down > same
3 - press 1 > all is now unlocked with the windows "do you really want to quit, yes / no"

No more bugs for you ?

Did anyone ever figure out a solution to this bug? It was happening to me over the weekend with a stock MAME64 0.153 and an official XBOX 360 controller. It seemed like every time I closed MAME, I would have to press all sorts of buttons to regain control of mGalaxy.

Thanks!

It s the first time you have the bug, or it s the first time you are using this MAME version ?
No recents changes in your configuration ?

And nope, no news for me, the bug is too unusual, I can't reproduce it. Perhaps someone else have better information.

Well actually it was the first time I ever ran mGalaxy on this particular machine... it's possible I was doing something wrong, but I don't recall it happening whenever I closed console emulators. Just MAME. I'll give it another go in the next few days to try and narrow some things down.

Perhaps mGalaxy can give you some special version to make some test, if you have the bug every time, it s possible to correct it. Not possible if the bug appears 1 time by week.