GBx includes the original GB and the GBC, not the GBA. They're referred to that way as the GBC is basically a GB++ of sorts, so they're referred to as one unit as usually they both apply to whatever is being discussed.
(That's my bad as I was talking about the GBA beforehand tho.)
I assumed by context that you lumped GBA into GBx with the mentioning of VBA, but yes GB VC and GBC VC have their pitfalls.
My ROM is part of the GoodGBA set EMUParadise had before they shut down, and the sum matches the known-good dump, so that's not the issue.
What game and its region are you trying to inject btw? Would you like me to try injecting my own copy for comparison?
I was going for mGBA so I could have nice things like custom controls, a restore point (my game won't save with its official VC release so I exit and everything's gone), maybe fast forward, a sprinkling of slowdown, maybe a screenshot button...
mGBA is slow for some GBA titles even on the n(2/3)DS(XL). However, the emulator is a WIP with continual/incremental improvements. It's GB, GBC, and SGB compatibility is neigh perfect.
[Also, I should mention, YES, the 3DS DOES have an ARM7 slaved to the ARM9 to support both DS/DSi titles and GBA titles. I know this.
(Lastly, don't bring the N64 thing into this. I know there's a hardship with the N64 being a different architecture than the host system. Mainly as we're not running on an N64. However, the New models can do PS1, DS, and GBA games via HLE, so why not the N64? It's got the grunt to do the conversions.)
To ensure we're on the same page about the difference between playing games natively and emulation, I brought this point back up as your previous post came across as disparaging real GBA hardware against an emulator that's trying to mimic it. If you left out save states, cheats, and frame skipping, it would be very wrong to say that VBA is better than GBA VC.
Here's that architecture analogy again I talked about last time about those dudes of different languages:
- N64 = Chinese
- Switch = Japanese
- 3DS = German
You have:
- Chinese dude reading at a leisure pace of 30 Chinese words per minute.
- Japanese dude reading at a blistering rate at 60 Japanese words per minute.
- German dude reading at a reasonable 40 German words per a minute.
Yes, you would be correct in stating that the Japanese guy is by far a faster reader than either of his Chinese and German peers in their respective languages. If each were given the exact same news article or book about the same story written in
their native language, that Japanese person would finish first followed by the German guy and finally the Chinese man.
However, some consideration would need to be taken believing that because Japanese dude is a such a fast reader, he could match reading on average 30 Chinese words per minute. Maybe he can if he's good at quickly finding unfamiliar Hanzi/Kanji in his JPN-CHN dictionary and doesn't get tripped too much by the Subject-Verb-Object word order difference. If you're not familiar what sentence syntax order is, think of "Yoda speak".
Which brings back the point about N64 emulation on the 3DS... It wouldn't be reasonable to ask that German dude to read Chinese as fast as his Chinese buddy.
Of course, where this analogy breaks down is that people have the capacity to learn new languages. Instruction sets, the fundamentally most basic language those CPUs understand, are built in at the hardware level. You can program a compatibility layer or emulator that translate between different sets, but this of course introduces
I/O R/W lag. This is why your source system needs be way much faster than the target system it's trying to emulate.