Dolphin, the GameCube and Wii emulator - Forums

It does. You can get another serial for cheap by buying a copy of Episode III, as nobody likes that game, so it's much cheaper. The serials will work with Episode I & II, as well.

Quick question, me and a friend were playing via netplay yesterday, and now today none of the data was saved? We check the memcard manager and it shows data, however in game no characters come up.
Any clue?
Also is it possible to play via hamachi that way we can play singleplayer too without desycning constantly when trying to play multiplayer afterwards?

Why are you using splitscreen over netplay when you can just play online to get full functionality and none of the bugs? There is no reason to use Dolphin's internal netplay or Hamachi when PSO has native online multiplayer support.

So Aleron Ives it appears I have had an account on sylverant for a long time and didnt remember it lol

Ah, so it was you I saw this afternoon.

lol guess so Now I just need to get my friend to register!

If anybody out there who is better able to give useful bug reports to the developers than I am (JMC?) would like to diagnose the quest loading crash with this game, I've found a pretty easy way to trigger it: connect to Sylverant, select the Download Quest option, and then "Seat of the Heart". This is the biggest quest by far, so it's the most likely to cause a crash. If the download succeeds, back out of the menu for saving it to the memory card, select Download Quest again, and redownload "Seat of the Heart". Unless this is caused by a problem with my configuration, I'm pretty sure anybody can replicate the crash with under half a dozen tries at downloading this quest, because Dolphin really hates trying to load a file this big. (I was able to crash 5.0-383 on my second try of loading this quest.)

It took me four tries today to download all eight downloadable quests in one go without crashing, so sadly the new BBA code isn't completely able to cope with loading large quests. Sometimes the game crashes (frozen screen with buzzing), and sometimes Dolphin crashes (frozen screen with no buzzing), but either way you'll get the prompt saying that Dolphin.exe has stopped working and must close. The new BBA code makes this far less likely to happen when you're loading an online quest in a game with other players (mainly because most quests are much smaller than this one), but crashing can still happen. I'm hoping that since the downloadable quest crash is so easy to reproduce that somebody can figure out what the problem is for a future PR.

Aleron, may I ask what is the new BBA code you are referring to?

I have been seeing a white box behind the text of my start menu (z/start/pause) where it lists items, settings and sub menus. Is there a setting that needs to be adjusted to remedy this white box? If not, I could live with it, but just wonder if it's even normal... Thank you.

Stenzek rewrote the Windows BBA code in PR 3432, which was merged in 4.0-9017. The old BBA code was far more prone to crashing, and I would crash at least once a week just from loading quests in the course of standard online play. The new BBA code included in every Dolphin release since then is far more stable than the old BBA code, but it can still crash, particularly if you load large quests frequently, e.g. Seat of the Heart, which is by far the most crash-prone quest. I also crash occasionally when joining a team hosted by a modem user, presumably because the time it takes a modem to transmit the join packet reveals some bug in Dolphin that doesn't occur when the join packet is sent instantly, as is the case when joining a team hosted by a BBA user.

When you join a team hosted by a BBA user, you'll see the saving icon appear twice on a black screen, and then you'll appear in the guild. If you join a team hosted by a modem user (or someone who's just laggy), you'll see the first save icon, and then you'll get a camera view overlooking Pioneer 2. Most of the time the camera will suddenly move to the guild, the game will save again, and you'll be on your way. Sometimes, however, Dolphin will just crash while you're staring at that overhead view, and this is particularly dangerous, because Dolphin doesn't write data to the memory card file at the exact moment you see the saving icon. As such, if Dolphin crashes while it's writing to the memory card file, your memory card corrupts, and you lose all four charactes on it. As such, be sure to make regular memory card backups if you play online and not just weapon backups. Even so, one crash per month is a lot better than one crash per week (or several crashes in a single day of quest testing).

Sadly, PSO isn't in the top tier of popular GC games, and the BBA isn't an important peripheral, due to the exceptionally small number of games that can use it, so there isn't a whole lot of developer interest in working on BBA-related bugs. Even so, I keep an eye on the recent development versions to see if any PRs of interest have been merged.

I don't think I've ever seen the bug you describe, but have you tried the other backends? D3D used to have a major bug with a giant white box covering the entire screen, and while that was fixed some time ago, perhaps you've discovered some remnant of it. I don't encounter graphical problems anymore when using OGL, thanks to all of the improvements since 4.0.

Thanks for that explanation! I wanted to make sure the BBA you were referring to was not something I needed to update individually, glad it's part of the emulator.

I am running on dolphin 5.0 with OGL. On my way to work, but I'll post back tomorrow with a picture as well as well as my configuration to see if we can iron it out. Off to work!

Side question, can you corrupt while on Dolphin? I haven't had seen any crazy double save FSOD at all.