(04-25-2021, 07:19 AM)Scary_Monsters Wrote: [ -> ]I'm getting this very annoying sound bug with Revision 1.02 of the game and only that version. This used to happen only sometimes on older versions of 5.0 and I forget how it was fixed then but now it happens 100% of the time with this version of the game. v1.00 works perfectly fine. I'm currently on 5.0-14051
https://www.youtube.com/watch?v=elMBpZE36B4
Have you verified your game dump? Maybe also try changing audio backends.
(04-25-2021, 07:55 AM)ExtremeDude2 Wrote: [ -> ]Have you verified your game dump? Maybe also try changing audio backends.
Yes I have and it said it was a-okay. Changing from Cubeb to WASAPI has zero affect.
It seems I somehow fixed the sound bug by replacing my years-old config files. What's weird though is that after actually putting the originals back, it was still perfectly fine.
Hi all. I'm working on a project to define a rule set for a Melee speedrunning leaderboard, and trying to collect information about Melee's compatibility on Dolphin. I'm a bit confused by what the game's
Wiki page indicates. The "Compatibility" widget on the right side shows 4/5, but the "Version Compatibility" section at the bottom seems to suggest a 5/5 rating since Dolphin version 4.0-5445.
Can someone help me understand the discrepancy? Is the actual compatibility 4 or 5? And if it's 4, where can I read about what's holding it back from a 5 rating?
Thanks.
The difference between 4 stars and 5 stars is pretty arbitrary. I'm not aware of any issues that would be stopping Melee from getting 5 stars, and whoever last changed the rating both wasn't logged in and provided no explanation.
Either way, Dolphin's emulation of Melee is very solid (even back when the version compatibility was at a 4 it was just because of some minor graphics inaccuracies), and I don't believe there are any regressions that would give you any reason to want to use an older version of Dolphin.
If you want to know if a game has any compatibility problems in Dolphin, the Problems list will almost always give you a more accurate picture than looking at the rating.
Thanks JosJuice, that's helpful. Another question:
The
Hybrid XFB blog post (from November 2017) mentions a setting specific to Melee:
Quote:While it may sound enticing to simply turn on Immediately Present XFB to get even lower latency, we do not recommend this outside of extreme cases where latency would matter, such as competitive netplay. Many games use the frame-out process for pacing, so, you'll very often get a smoother, more enjoyable experience by leaving Immediately Present XFB off. Super Smash Bros. Melee, Super Smash Bros. Brawl, and other latency intensive competitive titles that do not require special XFB emulation have Immediately Present XFB enabled by default for convenience.
This "convenience" sounds potentially problematic for Melee speedrunning, because input lag lower than what's achievable on a console+CRT setup could be considered an unfair advantage (especially on leaderboards where most scores predate the emulator era). So I'd like to understand this better.
I would have thought that having "Immediately Present XFB enabled by default" would have referred to a setting in a game-specific ini file. However, I don't see any XFB settings in any of the Melee ini files (e.g. GAL.ini or GALE01r2.ini). I checked in both a recent version (5.0-15993) and versions from around when this blog was published (5.0-5684 and 5.0-6060).
So is the statement in the blog true? If so, for which versions of Dolphin? And is it somehow able to be overridden? Thanks.
It was added to the game-specific INI file for Melee in
5.0-5874 and then removed in
5.0-5951.
Like with all settings that we set by default in game-specific INI files, it can be overridden if the user sets up their own game-specific INI file. Not that I think you want to use those old versions
I keep getting this error: Invalid read from 0x00000007, PC = 0x80343f0c
It occurs when I start 100 Man Melee & start spamming DK's ground slap (Down+B). However, if I only use it once or twice in succession, it doesn't freeze, only if I start spamming it.
Never mind, found the problem & fixed it.