These are my findings I've made so far when testing out FFCC:
I decided to stop emulating FFCC to switch the dsp engine to get better speeds without turning off the VBA-M instancess, which is akin to turning the gamecube off and on again without switching off the GBAs. What is suppose to happen is that the GBAs enter a "waiting for connection" state until FFCC loads up. When FFCC loads up they resume connection like nothing happened. However, upon restarting the emulation of the gamecube, all VBA-M instances become completely unresponsive and Dolphin refuses to actually emulate anything. Trying to stop the emulation by hitting the stop button doesn't do anything. Closing the VBA-M instances is the only way to completely stop the emulation process.
Was able to make 3 characters, but player four's character (the yellow gba) was unable to make a character. The character creator would work, but upon finishing it the character slot would read empty but still show the correct character model. Trying to select it would just start the whole creation process over. This is hit and miss, usually more miss than hit. Example Image
I noticed that sometimes while creating characters, an already established character's name will disappear. They're still selected and loaded, their name is just missing. Once actually in game, their name works as normal. I don't know for certain, but I think it primarily affects the first character only. You can see what I'm talking about in the last linked image.
Various visual artifacts when there are multiple VBA-Ms connected, but not all are used.
Loading up the VBA-Ms before loading up FFCC (turning on the GBAs before turning on the gamecube) will cause the VBA-Ms to either crash or hang.
Using savestates to skip the initial loading times works! I do them one at a time. Once blue is loaded and says "Please look at the TV" I make a save state called "blue ffcc". I then do the same for the others. Then when I reload I just load the savestates and bam, done. Funny thing is that you can actually use the colors interchangeably. I one time had two yellow background GBAs when one was suppose to be green. The colors eventually fix themselves.
Input is a little sporadic. I'll select a slot that I wish to create a character in and I'll go into the character creator and then immediately back out. I didn't test this a lot, but I think it has to do with how long I hold the button down.
I decided to stop emulating FFCC to switch the dsp engine to get better speeds without turning off the VBA-M instancess, which is akin to turning the gamecube off and on again without switching off the GBAs. What is suppose to happen is that the GBAs enter a "waiting for connection" state until FFCC loads up. When FFCC loads up they resume connection like nothing happened. However, upon restarting the emulation of the gamecube, all VBA-M instances become completely unresponsive and Dolphin refuses to actually emulate anything. Trying to stop the emulation by hitting the stop button doesn't do anything. Closing the VBA-M instances is the only way to completely stop the emulation process.
Was able to make 3 characters, but player four's character (the yellow gba) was unable to make a character. The character creator would work, but upon finishing it the character slot would read empty but still show the correct character model. Trying to select it would just start the whole creation process over. This is hit and miss, usually more miss than hit. Example Image
I noticed that sometimes while creating characters, an already established character's name will disappear. They're still selected and loaded, their name is just missing. Once actually in game, their name works as normal. I don't know for certain, but I think it primarily affects the first character only. You can see what I'm talking about in the last linked image.
Various visual artifacts when there are multiple VBA-Ms connected, but not all are used.
Loading up the VBA-Ms before loading up FFCC (turning on the GBAs before turning on the gamecube) will cause the VBA-Ms to either crash or hang.
Using savestates to skip the initial loading times works! I do them one at a time. Once blue is loaded and says "Please look at the TV" I make a save state called "blue ffcc". I then do the same for the others. Then when I reload I just load the savestates and bam, done. Funny thing is that you can actually use the colors interchangeably. I one time had two yellow background GBAs when one was suppose to be green. The colors eventually fix themselves.
Input is a little sporadic. I'll select a slot that I wish to create a character in and I'll go into the character creator and then immediately back out. I didn't test this a lot, but I think it has to do with how long I hold the button down.