Release Emu EX Plus Alpha ported to the Pandora


Okay, will check if there is something consistently triggering the issue.

Some additional info.

There was a underrun message in the out file and I noticed some slowdown in the last game I played before the issue occurred.

Code:
ALSA lib pcm.c:7843:(snd_pcm_recover) underrun occurred
./runscript.sh: line 62:  2593 Terminated              ./gbcemu $@
[SUCCESS]--- Starting the application ( runscript.sh  ) ----------
 
Those sound buffer underrun messages are quite common in normal operation in my experience. Perhaps not that many in concentration, but I don't immediately think it's anything to worry about. Did your run crash at the end, because I can see it terminated with error, or otherwise how did you exit it? Maybe that error code is relatively normal, I'm not that familiar with this code.
 
Those sound buffer underrun messages are quite common in normal operation in my experience. Perhaps not that many in concentration, but I don't immediately think it's anything to worry about. Did your run crash at the end, because I can see it terminated with error, or otherwise how did you exit it? Maybe that error code is relatively normal, I'm not that familiar with this code.

Thx! If they are common it will probably not be the cause of the issue. The out file will not be very helpful then.

At the end, pressing the spacebar resulted in a hidden menu, only to reappear with an up/down key but couldn't select anything anymore. After that I think I forced to program to stop with a long press pandora key.
 
Yeah, that's probably the normal exit code if you quit it that way. I don't think there's anything useful in the out file then, unfortunately.

To go further you're going to need to know more about how the code works, and playing for long enough with debugging enabled is unlikely to be an entertaining exercise.
 
To go further you're going to need to know more about how the code works, and playing for long enough with debugging enabled is unlikely to be an entertaining exercise.

The bug usually happens within 0 - 15 minutes of play. I tried to continuously play, save state and repeat but without actually playing the game even pressing the menu 100 times didn't result in the error.
I did notice that right before the bug starts playing the game gave a slight sound hiccup. Not sure if the gameplay was also effected - just too short to really notice what is going on.
Immediately after the sound hiccup the menu is not working correctly anymore. Pressing space doesn't show the menu but after that pressing the up key shows the menu again.
Then any key command results in doing the previous action. So if the last action was up and then I press down, the key will still go up one more time before it goes down.

Continue to use the menu once this happens finally results in freezing the menu. Can then only quit GBC emu by restarting or pressing the pandora button (out file does only give a lot of underrun messages)

@ptitSeb hope the even more detailed description above gives you some pointers. No problem to do more tests to help you find the bug. Just let me know what could help.

BTW. Start GBC emu from minimenu and the Pandora is a classic.
 
I'll see if I can reproduce this. Are you suggesting this behaviour doesn't happen under minimenu?

I have had situations in the past where the desktop fires up a dialogue (if my pandora falls off the network, or my battery runs low) but you should still be able to see that after killing GBC.emu so I guess it's not that - also space wouldn't normally clear the error.
 
I'll see if I can reproduce this. Are you suggesting this behaviour doesn't happen under minimenu?

I have had situations in the past where the desktop fires up a dialogue (if my pandora falls off the network, or my battery runs low) but you should still be able to see that after killing GBC.emu so I guess it's not that - also space wouldn't normally clear the error.

No it does happen under minimenu. Haven't tried to see if there is a difference using XFCE.
Battery running low issue isn't the problem as well - Pandora was fully charged and not connected to the internet.
Would be nice if you could confirm the problem, or not..
 
So I tried running GBC.emu running uCity (the only GBC game I could find to hand) while I was testing out the bluetooth joystick, and I ran it for about 25 minutes (although I didn't play all that time) and the menu still came up as expected when pressing space. So I couldn't reproduce it.

FWIW, what games have you been playing while experiencing this problem. And I could try not having bluetooth on while playtesting. Can you confirm just starting the game and maybe occasionally testing space still exhibits this bug?

Also FWIW, I'd just upgraded to get the latest bluetooth goodness, and was launching from XFCE. What OS are you on? I could try minimenu, but it's not something I normally use.
 
Last test I did was with a puzzle game Pitman/Catrap and using minimenu.
Would be interesting to see if I notice the same issue happening using XFCE. Thanks for testing - I don't mind switching to XFCE if that helps.

btw. starting the game and just press space will not cause any problem (I think) done that a lot without causing the problem.
[doublepost=1507049428,1507035298][/doublepost]Nope - same issue in XFCE.. within 3 minutes had the sound hiccup three times and every time after that the menu was 'broken'. Will give the same SD card a try in my 1Ghz Pandora.
[doublepost=1507055021][/doublepost]Played for quite a long time on my Ghz and no issue at all. Not planning to use my Ghz for this emulator so still looking for a solution. Might be performance related, will try overclocking the emulator on my classic next.
[doublepost=1507056657][/doublepost]Nope - not performance even though the hiccup feels/sounds like a sudden drop in performance. Just played a couple of minutes on 975 mHz and it happened again.
Tried it on another classic Pandora and the same issue. So I guess it is hardware related.
 
It maybe SGX driver related. EMU are now using GLES2, and that has never been a strong side of the classic SGX hardware/drivers.

(still, you can also try with some other drivers, or with a swapfile, in case it's memory related).
 
It maybe SGX driver related. EMU are now using GLES2, and that has never been a strong side of the classic SGX hardware/drivers.
(still, you can also try with some other drivers, or with a swapfile, in case it's memory related).

Thx will try both and let you know if it worked.
 
Unfortunately other drivers introduced other problems (freezes) - EMU EX seems to be very picky indeed.
The swap file didn't help solving the issue either. Luckily there are alternatives for the classic (eg GnGB) so not a problem if it isn't fixable.

Of course if other members have more luck with their classic, I am interested in their setup.
 
Ok, there is now updated build of the whole serie. They use latest source code, and have been a bit difficult to build. C64emu had a lot of changes, but seems to run now. Not that I didn't enabled SegaCD code in MDemu (it wont build, and I don't feel like fixing it, as it's not a simple fix).

Build 16
----------

  • Updated (finally) to latest source code
 
Back
Top