FrostedGeulleisia
commented
3 years ago Possible factors:
- Blue's Pokémon faints by an attack, Red's Pokémon faints from status or recoil damage (I only remember an example with burn or Brave Bird recoil) the same turn, but after Blue's Pokémon has fainted.
- the Pokémon that faint are Blue's bottom active Pokémon followed by Red's top active Pokémon
- the game tries to shift in Red's new Pokémon in first, then Blue's, which is when the softlock happens, it's also the opposite of the fainting order.
This would first require replicating in a vanilla game, though I do not have the setup to be able to do so. Here's another, more recent example of this happening: https://clips.twitch.tv/DoubtfulJoyousPelicanPupper-5AmwtEcu2wVaOybE (or a video link if you want to suffer with the VOD player https://www.twitch.tv/videos/953607345?t=04h56m22s )
aaaaaa123456789
ghost
Example: https://www.twitch.tv/videos/524244779?t=17h20m18s Possibly a vanilla ROM issue considering all pbrEngine does is press the wiimote button for the next Pokemon. Usually occurs when at least one pokemon from each team faints. As this causes a softlock, more examples can be found by searching "dolphin soft freeze" or "manually hard-cancelled" in tpp.chat.
One theory was that one or both button presses are made too quickly for the game to handle, and delaying them by a half second would fix it. It's purely speculative, but wouldn't really hurt to try.