Rikvis, не пугай новичков. Именно так они и делают: не обращают внимания на даты и выражают смайликами эмоции, а не словами мысли.
Rikvis :: 1 февраля 2014, 20:36 ::
Зарегистрироваться ради одного поста в виде смайлика, к комментарию полугодичной давности? Походит на твинка.
Zamochu :: 1 февраля 2014, 20:04 ::
Шемас [ модератор ] :: 3 июня 2013, 18:00 ::
В прошлом году.
dunpil :: 3 июня 2013, 16:05 ::
Segna искал.
Шемас [ модератор ] :: 3 июня 2013, 15:34 ::
Спасибо. И зачем это здесь нужно?
dunpil :: 3 июня 2013, 13:45 ::
Alright.
First of all, make sure you have the proper settings in all the emulators. That means: 1. Putting GBA as your dolphin controllers 2. Setting your bios in VBA-M 3. Unchecking Options -> Emulator -> Pause when Inactive in VBA-M 4. Checking Options -> Speed -> Turbo Mode in VBA-M, because VBA-M needs to go to 1000% speed to run FFCC at full speed
(If there are any other required settings, I've forgotten them, so if it doesn't work, check against one of the more general Dolphin & VBA-M connection tutorials).
Now, make sure you have all your VBA-M instances running (between one and four of them, obviously). Open the GBA bios in each of them, as you would when connecting to any Dolphin game.
To make this work okay, you're going to want to use a savestate from after VBA-M has recognized the game. You can probably make an adequate state yourself if you try hard enough, but I recommend downloading bios_state1.sgm from comment #45 over on the page for issue 3177: http://code.google.com/p/dolphin-emu/iss...d=3177#c45
Load the savestate mentioned above, in EVERY instance of VBA-M which you're using. Then open the Joybus Options dialogue in each of them, but DO NOT press okay yet.
Open dolphin, and run the game. Now, I'm not sure how much leeway you have with the timing here, but what I normally do is this: As soon as I see the game display the first logo, I press OK for the Joybus Options in every VBA-M. If you wait too long, I don't think it's able to connect.
If you did everything correctly, then after this you should be good. In the event that one of the VBA-M instances disconnects during play, I've found that the following will usually - but not always - fix it: Step 1: Make a save state in the disconnected VBA-M Step 2a: If "Waiting for connection is NOT flashing, stop and wait for it to fix itself Step 2b: If "Waiting for connection" IS flashing, load the save state and wait a second Step 3: Go back to Step 2. Гайд запуска мультиплеера через эмулятор
