How exactly does one go about building the 3DS port of mGBA? Asking for curiosity's sake.

In the new update 0.6.3, the solar sensor does not work. I tried it with the three games of Boktai, in the first title appears the message "The solar sensor is broken" and the other two games just not recognize it, I also tried to calibrate the sensor, but the result was the same. (I do not know if the versions of other platforms have the same problem)


Excuse my bad English

Hi folks,

I'm interested in understanding how the mgba works and therefore I want to follow its
dynamic behaviour. I woul appreciate to import the mgba in a usual ide like eclipse, netbeans etc ...
I'm currently working with linux, but I could easily switch to windows.
I already followed this tip but that's not the final solution. The source compiles and
immediately exits after start.

Greetings,
Interested_One

Let's admit it: Vita users, such as I and many others, would greatly appreciate mGBA to utilize VitaGL.  The emulator in its current state on the Vita is overshadowed by Retroarch's option to use VBAnext, and neither as of yet can allow most games to run at a constant 60fps or above.  VitaGL is an openGL wrapper for the Vita and it's open source.  VitaGL has allowed it's quake port by Rinnegatamante to achieve 60fps on the Vita's native resolution.

Would VitaGL ever come to mGBA on the Vita?  pls?

I noticed that playing using mGBA at different speeds (audio/visual --> target FPS) distorts the audio pitch. I suppose this isn't exactly a "glitch" but is certainly not a welcome feature.

If I had to speculate, I suspect a 60hz tone played at 120 fps (double speed) means now 2 60hz waves fit in one second, or in other words 120hz fits in a second, effectively raising the entire game audio an octave.

Do other GBA emulators face this problem while playing on turbo?

If the devs ever see this, a couple work arounds to consider include:
1) Fixed turbo (fixed at 4x) comes with fixed audio (lower pitch by 4 octaves). [Of course, this assumes emulation is held steady at 4x, and doesn't fluctuate significantly. It would be up to the user to decide if their machine can hold a fixed turbo or not]
2) Variable turbo (such as unbound) comes with variable audio fix (dynamically approximating and lowering audio) to match approximated pitch. This option would of course take more resources to dynamically access the speed at which each frame comes out.

Thoughts or suggestions? Am I the only one finding chipmunk sequels at 6+ octaves too high annoying?

When opening the application I receive this error message: mGBA quit unexpectedly.

I ran this in the terminal: sudo spctl --master-disable to disable the annoying popup that blocks unidentified applications but I'm not able to run any of the versions available for download. I tried the newest release version 0.6.3 and the development build: mGBA-build-2018-05-15-osx-5116-7c058ea13ff03f78d0610944747ebfaabbd24bb4.

Here is the detailed error message it gives me when I open the release build:

The three Pokemon games that use RTC boot normally the first time, but if you exit and try to load them again, they crash the app. If you delete their save file and load them again, they boot just fine, so I'm guessing it's a problem with the save file. This doesn't happen with other GBC games that I tried.

I'm using macOS High Sierra and I'm trying to unzip the archive but all it does is create duplicates of itself instead of unzipping... I'm not very familiar with the Mac OS so I'm not really sure what I'm doing wrong. Usually I double click an archive to unzip it and it generally works.

I unzip the initial file: mGBA-0.6.3-osx.tar.xz. And I get this file: mGBA-0.6.3-osx.tar.xz.cpgz. I double click that new file and it just creates new copies of the first file: mGBA-0.6.3-osx.tar 2.xz etc. When I try unzipping those new duplicates it just creates new duplicates of itself. Is there something I need to be doing? I feel like it shouldn't be this difficult just to unzip a file. Any help would be appreciated. Thanks!

Been looking for this answer for quite a long time now and forgot only until recently when I decided to play some GB/C/A games again and see the messages popping up again.

How do I turn off that message?
I don't see it in settings and see no ini to do that.

Hi endrift!

Lately I've been playing a lot of toruzz's new colourization hack for Super Mario Land 2 found here:
http://www.romhacking.net/hacks/3784/

However, I've been experiencing some weird issues when using Savestates and loadstates on multiple builds of mGBA.
I tried RetroArch's, 3DS and Windows build of mGBA (latest nightly) and they all seem to do the same.

You can reproduce the issue by simply starting up a new game, making a savestate in the first level, and then reset the game and try to load the state from ANYWHERE else in the game except the same level (this can be easily tested if you made the save at the fisrt level, and try to load the state from the World map)
The result ends up being Mario/Luigi dying instantly upon loading a state, and the background/level layout being a complete mess.

Other GB/GBC games seem to work fine with states, it's just this hack so far that I am experiencing issues with saving and loading states with.

If you need any more info to debug this, please let me know!