Re: mGalaxy 5.2 trouble when returning from MAME
Posted: Mon Nov 10, 2014 11:41 am
I have the same problem, sith a freshly installed mgalaxy and NES/Nestopia only configured.
mGalaxy forum
A frontend with a soul
https://mgalaxy.com/forum/
mGalaxy 5.2 trouble when returning from MAME
Page 2 of 2
Re: mGalaxy 5.2 trouble when returning from MAME
Posted: Mon Nov 10, 2014 5:02 pm
The same bug ? with the transparent menu if you press ESC key ?
Re: mGalaxy 5.2 trouble when returning from MAME
Posted: Tue Nov 11, 2014 6:20 pm
Sorry I was talking about this bug. I used a Logitech F710 on xinput mode (has a switch which changes between dinput and xinput mode).fleskebacon wrote: 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.
I also have a xbox 360 for windows wireless pad, but I dislike the big dead zone. Anyway I've been using it and since then the bug didn't happen again. So it could be related to not pure xbox 360 controllers.
BTW any chance of getting directinput also supported?
Re: mGalaxy 5.2 trouble when returning from MAME
Posted: Wed Nov 12, 2014 4:47 pm
I m using an xbox 360 emulator too, maybe it s the cause, but I don't see how this can happen ???I also have a xbox 360 for windows wireless pad, but I dislike the big dead zone. Anyway I've been using it and since then the bug didn't happen again. So it could be related to not pure xbox 360 controllers.
Re: mGalaxy 5.2 trouble when returning from MAME
Posted: Sat Nov 15, 2014 8:06 pm
I was using genuine MS Xbox 360 controllers when I ran into this bug, so I don't think that's it... 