Thx RocketRobz for reply!! As I said, I'm completly new to Ds...How do you launch the gba_db.bin (which is Open_AGB_FIRM)??
Open_AGB_FIRM is a .firm file, not the "gba_db.bin" file.Thx RocketRobz for reply!! As I said, I'm completly new to Ds...How do you launch the gba_db.bin (which is Open_AGB_FIRM)??
It's a database for saves to work correctly.So what is the gba_db.bin inside open_agb_firm_alpha_20220425.7z ???
You need to launch it each time to start a .gba file.What will happen once I open open_agb_firm.firm with Luma? Will it install something or do I need to launch the program like this each time to launch a *.Gba file?
Yes, there's GodMode9 (which does not matter in this case).Are there other program in the .Firm format?
GBARunner2 works fine on 2DS, but the slowdown cause on your side is unknown. mGBA is slow, because the O2DS/O3DS hardware can't emulate the GBA fast enough.Still wondering one last thing: Why doesn't GBARunner2 or Mbga doesn't work on 2DS? Is it work in progress?
Nope, the BIN file goes on SD:\3ds\open_agb_firm\ in order to work! I had to find this ^^"Make sure the .firm file is placed in "sd:/luma/payloads/". The .bin file also goes there, I think."
Yes, it is fixed in GBARunner3.Hey RocketRobz, thanks for your work, has audio in Fire Red been fixed?
As it is still in development, you need to build it from the source code.Where is it possible to download a version of GBARunner3?
GBARunner3 should be able to run faster than GBARunner2.Will I be able to use GBARunner3, on my 2DS? As when I use GBARunner2, it is unusable because much too slow
It'll bring improved sound emulation, as well as better compatibility. The unused screen will also be turned off.What does GBARunner3 will bring in the future please?
Will I be able to use GBARunner3, on my 2DS? As when I use GBARunner2, it is unusable because much too slow
What does GBARunner3 will bring in the future please?
People on Linux seem to have this issue. Use windows instead.How do I build GBARunner3? I always get this error message:
```
ArmDtcm.o: in function `memu_armDispatchTable':
(.dtcm+0x8): relocation truncated to fit: R_ARM_ABS16 against symbol `memu_armLdmStmRnTable_0' defined in .dtcm section in ArmLdmStmRn.o
(.dtcm+0xa): relocation truncated to fit: R_ARM_ABS16 against symbol `memu_armStmRdTable' defined in .dtcm section in ArmLdmStmRd.o
(.dtcm+0x10): relocation truncated to fit: R_ARM_ABS16 against symbol `memu_armLdmStmRnTable_0' defined in .dtcm section in ArmLdmStmRn.o
(.dtcm+0x12): relocation truncated to fit: R_ARM_ABS16 against symbol `memu_armLdmRdTable' defined in .dtcm section in ArmLdmStmRd.o
(.dtcm+0x18): relocation truncated to fit: R_ARM_ABS16 against symbol `memu_armLdmStmRnTable_1' defined in .dtcm section in ArmLdmStmRn.o
(.dtcm+0x1a): relocation truncated to fit: R_ARM_ABS16 against symbol `memu_armStmRdTable' defined in .dtcm section in ArmLdmStmRd.o
(.dtcm+0x20): relocation truncated to fit: R_ARM_ABS16 against symbol `memu_armLdmStmRnTable_1' defined in .dtcm section in ArmLdmStmRn.o
(.dtcm+0x22): relocation truncated to fit: R_ARM_ABS16 against symbol `memu_armLdmRdTable' defined in .dtcm section in ArmLdmStmRd.o
(.dtcm+0x28): relocation truncated to fit: R_ARM_ABS16 against symbol `memu_armLdmStmRnTable_0' defined in .dtcm section in ArmLdmStmRn.o
(.dtcm+0x2a): relocation truncated to fit: R_ARM_ABS16 against symbol `memu_armStmRdTable' defined in .dtcm section in ArmLdmStmRd.o
(.dtcm+0x30): additional relocation overflows omitted from the output
```
GCC 11.1.0, ld 2.36.1
Not gonna happenPeople on Linux seem to have this issue. Use windows instead.
That moment when you finally think your software is easy to compile for anyone.