I got a solution to my problem stated earlier in this thread (GBA not connecting, everything going slow).
Want to guess?
My processor was too slow. I had a dual core C2D E8400. It didnt really make the Dolphin LLE AND VBA lifting all at once. This is why it slowed down beyond belief!
I now have a i5 2500k @ stock. It barely goes to 30 % CPU use and everything runs smooth. I can even run multiple VBAs and not run out of power!
But now, with the newest versions, the game stopped working. After the NINTENDO screen it just goes black. Settings do nothing.
Sorry for bringing back this thread alive, but...
I need the connection for Pokémon Box. So my question is: has anybody yet found out how to connect VBA-M to Pokémon Box? The problem is I think that there is code supplied by the GameCube into the bootstrapper of the Pokémon ROM, not the GBA Bios. But shouldn't that work exactly the same like on real hardware?
Dolphin recognizes the connection of VBA while the joyplay is activated and it is going to the bootstrapper of the Pokémon Cartrige in VBA. But instead of changing the screen to the Pokémon Box screen - and of course continue working - it just goes on loading the GBA game in VBA and waiting for any signal in Dolphin.
I have found out that it's really the same using either LLE or HLE and I also think today it has no more anything to do with the sound emulation?
Well, I am just asking if it works for somebody, because in another (pretty old) thread
http://forums.dolphin-emu.org/showthread.php?tid=9925 there also was no solution given. Maybe it has something to do with timing problems.
Was trying it with Wind Waker just now. After loading the bios, then fiddling with the "Enable Joybus" option WW finally recognises the link and prompts "would you like to call tingle?" and initiates the connection. The GBA then reloads, but gets real slow at the "GameBoy" screen. Meanwhile, WW has concluded there's something wrong with the connection. And THEN, after a while (without re-activating tingle tuner), VBA actually shows "Calling Tingle" then a red background error message with tingle at the bottom right.
So based on the symptoms, I guess it is a timing issue? Will there be a fix later?
using Windows 7 64bit laptop with i7 Q720, Dolphin 3.0.
Yes, I think it is a timing issue too. I will look into this again when I get some time.
Hello.
I followed this guide and when I'm loading bikos in VBA-M, it freezes. I'm waiting, but still frozen. When I turn of Dolphin emulator, VBA-M unfreezes. I don't know why... I followed instructions.
Hi!
I'm currently playing Zelda Wind Waker on Dolphin, and I'm trying to connect a CBA in order to use the Tingle Tuner. I followed your guide, and it seems that Dolphin do believe that I have a GBA connected (I get asked if I want to call him, instead of just getting a message saying "nothing connected").
Once I click yes, that triggers the bios to boot. Here's where I get a huge problem. VBA-M freezes/get massive lagspikes, and the connection times out. This causes both Dolphin and VBA-M to lag. A lot.
Am I doing something wrong?
Here's how I'm doing it atm:
1. Opened Dolphin, added GBA controller to slot #2.
2. Started my game
3. Opened VBA-M
4. Options -> Link -> Joybus -> Enable (127.0.0.1 - running both on the same computer)
5. Open the bios (File -> Open GBA -> gba_bios.bin)
6. Try to use the tingle tuner in Zelda, clicks "Yes" when asked to connect
7. VBA-M boots up, but lags a lot, and Zelda/Dolphin gives up trying to connect.
Am I doing something wrong here?
I'd highly appreciate any help!
(11-17-2011, 02:34 AM)Ajaco Wrote: [ -> ]Hi!
I'm currently playing Zelda Wind Waker on Dolphin, and I'm trying to connect a CBA in order to use the Tingle Tuner. I followed your guide, and it seems that Dolphin do believe that I have a GBA connected (I get asked if I want to call him, instead of just getting a message saying "nothing connected").
Once I click yes, that triggers the bios to boot. Here's where I get a huge problem. VBA-M freezes/get massive lagspikes, and the connection times out. This causes both Dolphin and VBA-M to lag. A lot.
Am I doing something wrong?
Here's how I'm doing it atm:
1. Opened Dolphin, added GBA controller to slot #2.
2. Started my game
3. Opened VBA-M
4. Options -> Link -> Joybus -> Enable (127.0.0.1 - running both on the same computer)
5. Open the bios (File -> Open GBA -> gba_bios.bin)
6. Try to use the tingle tuner in Zelda, clicks "Yes" when asked to connect
7. VBA-M boots up, but lags a lot, and Zelda/Dolphin gives up trying to connect.
Am I doing something wrong here?
I'd highly appreciate any help!
Specs?
(11-17-2011, 11:08 PM)ExtremeDude2 Wrote: [ -> ] (11-17-2011, 02:34 AM)Ajaco Wrote: [ -> ]Hi!
I'm currently playing Zelda Wind Waker on Dolphin, and I'm trying to connect a CBA in order to use the Tingle Tuner. I followed your guide, and it seems that Dolphin do believe that I have a GBA connected (I get asked if I want to call him, instead of just getting a message saying "nothing connected").
Once I click yes, that triggers the bios to boot. Here's where I get a huge problem. VBA-M freezes/get massive lagspikes, and the connection times out. This causes both Dolphin and VBA-M to lag. A lot.
Am I doing something wrong?
Here's how I'm doing it atm:
1. Opened Dolphin, added GBA controller to slot #2.
2. Started my game
3. Opened VBA-M
4. Options -> Link -> Joybus -> Enable (127.0.0.1 - running both on the same computer)
5. Open the bios (File -> Open GBA -> gba_bios.bin)
6. Try to use the tingle tuner in Zelda, clicks "Yes" when asked to connect
7. VBA-M boots up, but lags a lot, and Zelda/Dolphin gives up trying to connect.
Am I doing something wrong here?
I'd highly appreciate any help!
Specs?
CPU: Intel i7 2600k
GPU: Spahire Radeon 6870
8 gig ram
Any other specs thats important to note? I really don't think it's my computers performance that's lacking.
Thanks for taking the time to reply
(11-18-2011, 04:13 AM)Ajaco Wrote: [ -> ]CPU: Intel i7 2600k
GPU: Spahire Radeon 6870
8 gig ram
Those should be fairly good I dunno what the problem is
I play Zelda Wind Waker have the same problem. I agree that is timing issue too！