rvtr/wiki
1
Fork 0
mirror of https://github.com/rvtr/wiki.git synced 2025-10-31 06:31:13 -04:00
Code Issues Actions Packages Projects Releases Wiki Activity

Update GBARunner2 Wiki (#63)

Browse Source 
* Update builds.md

- Add links to builds
- Add Hicode/DSP build by therealteamplayer
- Some grammar tweaks and such

* Update faq.md

- Remove nightly builds FAQ (there hasn't been a nightly build in a long while)
- Add "Why is a ROM not working, even though the compatibility list says it works?"
- Add "How do I fix duplicated layers at the bottom of the screen on 3DS?"
  - This could maybe use a better name

* Minor edit in builds.md

I forgot to edit the stuff at the bottom
This commit is contained in:
triangle 2022-04-30 11:36:28 -05:00 committed by GitHub
parent 1c14b55adf
commit a5dbc1bc9f
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 34 additions and 24 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

44
pages/_en-US/gbarunner2/builds.md
View File

@ -7,11 +7,11 @@ description: Information on the various GBARunner2 Builds and their uses
---
There are a number of different GBARunner2 releases or "builds" which one can use. They come from different branches and forks of GBARunner2 and have different features targeting either different GBA games or some different functions. **For most users** using the build that comes with TWiLightMenu++ is enough.
There are a number of different GBARunner2 releases, or "builds," which one can use. They come from different branches and forks of GBARunner2 and have different features targeting either different GBA games or some different functions. **For most users**, using the build that comes with **TW**i**L**ight Menu++ is enough.
## DS vs DSi vs 3DS Builds
GBARunner2 has had builds made that makes use of the extra hardware found inside the DSi and 3DS. Naturally, these DSi- and 3DS-specific builds will not work on a DS. However, they also will not work if you are running GBARunner2 from a flashcard on any of the systems, DSi and 3DS included. The details about this will not be covered here.
GBARunner2 has had builds made that make use of the extra hardware found inside the DSi and 3DS. Naturally, these DSi and 3DS-specific builds will not work on a DS. However, they also will not work if you are running GBARunner2 from a flashcard on any of the systems, DSi and 3DS included. The details about this will not be covered here.
This means that you can use builds for the DS on both DSi and 3DS, but not vice-versa.
@ -19,15 +19,15 @@ This means that you can use builds for the DS on both DSi and 3DS, but not vice-
These are the builds that are present for all three lines of systems.
### Master
### [Master](https://github.com/Gericom/GBARunner2/releases)
The Master builds or "main" builds are the proper releases of GBARunner2. This should generally be the most stable build.
The Master builds, or "main" builds, are the proper releases of GBARunner2. This should generally be the most stable build.
All other branches than this one are considered experimental and not stable enough to be included into the Master.
The Master builds are divided into different builds for the DS, DSi and 3DS. They each have the name of the corresponding system appended at the end of the filename.
### Wi-Fi-Link
### [Wi-Fi-Link](https://github.com/Gericom/GBARunner2/releases/tag/v20200217-194452_0b8bbe3)
The Wi-Fi-Link branch adds the possibility to link up two systems wirelessly. Note that this does not go over the Internet, and this will never be possible. Currently your mileage will vary, and the only sure-fire game that will be able to keep a stable connection is Advance Guardian Heroes, and that is provided that you follow very specific instructions. Needless to say, consider this branch in its current state a novelty and a proof of concept, and not something to actually use. A few other games are able to connect, but they are very dependent on external factors like interference from other Wi-Fi signals, among many other things.
The Wi-Fi-Link branch adds the possibility to link up two systems wirelessly. Note that this does not go over the Internet, and this will never be possible due to latency. Currently your mileage will vary, and the only sure-fire game that will be able to keep a stable connection is Advance Guardian Heroes, and that is provided that you follow very specific instructions. Needless to say, consider this branch in its current state a novelty and a proof of concept, and not something to actually use. A few other games are able to connect, but they are very dependent on external factors like interference from other Wi-Fi signals, among many other things. To setup Wi-Fi liking, please see the [WikiTemp page](https://wiki.gbatemp.net/wiki/GBARunner2/Link).
## DS-Specific Builds
@ -36,33 +36,41 @@ The Wi-Fi-Link branch adds the possibility to link up two systems wirelessly. No
**Normally use the ARM9DLDI**, and if that does not work then try the ARM7DLDI.
Some flashcards need either the ARM7DLDI or the ARM9DLDI, and some might work with both. There is no list of which flashcards work with which builds, but if you are running into issues getting GBARunner2 to run then you might want to try the other one.
If you are using **TW**i**L**ight Menu++ on your flashcard, you can switch between ARM7DLDI and ARM9DLDI in the **TW**i**L**ight Menu++ settings.
There are no feature or performance differences between the two so there is no use in testing both to see if a game runs better or has less issues on the other.
See further down to find out what build you are currently using.
### ROM3M
If you are using TWiLightMenu++ then you are already using this feature in the GBARunner2 build that comes with it.
### [rom3M](https://github.com/Gericom/GBARunner2/releases/tag/v20190911-201047_371815e)
This branch might help if trying to run ROMs that are a bit larger on the DS, but there is a limit due to the limited amount of RAM present in the DS. This is basically the Pokémon Emerald branch for the DS.
Void Star made [a fork of GBARunner2](https://github.com/unresolvedsymbol/GBARunner2-DSL-Enhanced/releases) that combines this ROM3M branch with some other neat features, and this is the build that comes with TWiLightMenu++ if you are using a DS.
Void Star made [a fork of GBARunner2](https://github.com/unresolvedsymbol/GBARunner2-DSL-Enhanced/releases) that merges the rom3M branch into the latest Master with some other neat features, and this is the build that comes with **TW**i**L**ight Menu++ if you are using a DS.
## DSi- and 3DS-Specific Builds
The DSi and 3DS can generally run the same builds, but due to the difference in amount of RAM between the DSi and 3DS the compatibility for games can differ. This generally means that the DSi might have trouble running larger ROMs that the 3DS can run fine.
The DSi and 3DS can generally run the same builds, but due to the difference in amount of RAM between the DSi and 3DS the compatibility for games can differ. This means that the DSi might have trouble running larger ROMs that the 3DS can run fine.
The 3DS also has an accelerometer chip for gyro controls built-in, and this can be used in a 3DS-specific build.
### DSP
### [DSP](https://github.com/Gericom/GBARunner2/releases/tag/v20200809-113646_551ae99_dsp-audio)
The DSP builds make use of an extra processor present in both DSi and 3DS. This helps to produce a lot better sound and give better performance. There are some regressions like a couple of ROMs that do not work in this branch.
If you are using **TW**i**L**ight Menu++, then you are already using this feature in the GBARunner2 build that comes with it.
### Hybrid Hicode
The DSP builds make use of the digital sound processor present in both DSi and 3DS. This helps to produce a lot better sound and give better performance. There are some regressions, like a couple of ROMs that do not work in this branch.
### [Hybrid Hicode](https://github.com/Gericom/GBARunner2/releases/tag/v20200812-130512_d5dc8d8)
If you are using **TW**i**L**ight Menu++, then you are already using this feature in the GBARunner2 build that comes with it.
The Hybrid Hicode branch deals with ROMs that are large and have problems running on the Master branch. This is a very useful branch for the DSi since this mostly solves the issue with having less RAM than the 3DS.
### 3DS-Specific: Gyro
### [Hicode/DSP merge](https://github.com/therealteamplayer/GBARunner2/releases/tag/v20210911-merges-and-tweaks)
This fork by therealteamplayer merges the Hicode and DSP branches into one build, along with some other tweaks listed in the release notes. This build is currently used by **TW**i**L**ight Menu++ for the DSi/3DS SD card.
### 3DS-Specific: [Gyro](https://github.com/Gericom/GBARunner2/releases/tag/v20191228-021638_ee7f6a0)
This branch makes use of the internal accelerometer in the 3DS so that GBA games that had this functionality can be played properly. There are several steps needed to take to make it work. Note that since there are different accelerometer chips between 3DS systems, this will not work on all 3DSes because all chips do not have code supporting them.
@ -70,10 +78,10 @@ There is no consistency in what type of 3DS has what chip, at least as far as an
## Finding the Build Info
GBARunner2 has an menu you can open by touching the touch screen and pressing the right shoulder button. Within this you can find the about menu which tells you what build you are on. However, the builds that come with TWiLightMenu++ do not report a build version because they are based on forks by other people. This means that if your About page shows blank for build, you are most likely using one of these.
GBARunner2 has a menu that you can open by touching the touchscreen and pressing the right shoulder button. Within this you can find the About menu, which tells you which build you are on. However, the builds that currently come with **TW**i**L**ight Menu++ do not report a build version because they are based on forks by other people. This means that if your About page shows blank for build, you are most likely using one of these.
This tells you if you are using an ARM7DLDI or ARM9DLDI build
The About page also tells you if you are using an ARM7DLDI or ARM9DLDI build.
Knowing what build to use is useful when checking the official compatibility list in case you are having issues with running a game.
Knowing which build to use is useful when checking the official compatibility list, in case you are having issues with running a game.
The release ID can be seen on the release page of the GBARunner2's github repository, where the last seven alphanumeric symbols represent the version. For example, the current latest Master release is "v20200812-131430_6e4ce45" and "6e4ce45" is used to represent its version.

14
pages/_en-US/gbarunner2/faq.md
View File

@ -13,16 +13,11 @@ You can read and follow [this guide](https://docs.google.com/document/d/1owjiW-1
#### Are cheats supported?
Not right now. Instead, you can permanently inject cheat codes into your GBA ROM with [GBAATM](https://gbatemp.net/threads/gba-auto-trainer-maker-gbaatm.99334/).
#### How do I use nightly GBARunner2 builds in TWiLight Menu++?
1. Download the nightly build
1. Rename it to `GBARunner2_arm7dldi_3ds.nds` (or `GBARunner2_arm7dldi_dsi.nds` if you're on DSi)
1. Place it in `sd:_nds`
#### Which build of GBARunner2 should I use?
Usually, the builds that are included with TWiLight Menu++ is enough. For more information on the various builds of GBARunner, see the [Builds wiki page](https://wiki.ds-homebrew.com/gbarunner2/builds).
#### How do I use Wi-Fi link features?
You will need a build from the [wifi_link](https://github.com/Gericom/GBARunner2/tree/wifi_link) branch to use the features. You can find detailed instructions on how to setup the builds on its [GBAtemp Wiki page](https://wiki.gbatemp.net/wiki/GBARunner2/Link).
You will need a build from the [wifi_link](https://github.com/Gericom/GBARunner2/tree/wifi_link) branch to use the features. You can find detailed instructions on how to setup the builds on its [WikiTemp page](https://wiki.gbatemp.net/wiki/GBARunner2/Link).
#### Why isn't RTC (Real Time Clock) supported in a ROM hack?
RTC is supported on a per-game basis. You will have to change the ROM's title ID to that of a game that supports RTC so that GBARunner2 will recognize it.
@ -36,3 +31,10 @@ You can change the title ID using the following:
<input id="save" class="btn btn-secondary" type="button" value="Save" onclick="save()" disabled>
<script src="/assets/js/change-gba-tid.js"></script>
#### Why is a ROM not working, even though the compatibility list says it works?
The GBARunner2 compatibility lists are primarily tested with the offical GBA BIOS, which improves compatibility. See [GBA BIOS Info](https://wiki.ds-homebrew.com/gbarunner2/bios) for information on obtaining the offical GBA BIOS.
#### How do I fix duplicated layers at the bottom of the screen on 3DS?
This is a bug in TWLBg that is rather prevalent in GBARunner2. The only way to temporarily fix this is to restart GBARunner2.
- If applicable, you may be better off using other options for running GBA ROMs on 3DS, such as VC injects, open_agb_firm, or mGBA on n3DS models