PlayableShow Details
Unknown
Just bought the game to support developers. Community edition is way much better to play online.
No audio on VS screen, nothing that could break the gameplay.
Turn off Steam Input to fix your control not working.
The game has an awful input delay netcode. The community edition works like a charm in Lutris using CCcaster with rollback.
I had to use Proton 7.0.5 because experimental dropped support for my GTX750ti. But I guess the game works fine on Experimental too.
RADV_DEBUG=nodcc %command%
Constant crashes
Used Community Edition instead of the Steam Version.
Works perfectly even online. It used to crash in between battles with previous Proton versions but not anymore. I used Proton 7.0-5 Flatpak community build.
Install LAV Filters for opening & fight entrance cutscenes, prevent freeze on loading into fights: protontricks 411370 lavfilters
- Opening cutscene doesn't play (black screen). Fixed with protontricks
- After game was launched several times (at ~3 hrs playtime for me), I couldn't load into fights anymore -- game freezes (white screen) after selecting characters in any mode, needs to be terminated externally. Fixed with protontricks
Head to play.meltyblood.club for online multiplayer - playerbase mostly uses the 'Community Edition' of this game with an external program for rollback-based netplay, as well as a Discord server to arrange matches.
Found launch option to fix graphical corruption issues, runs more or less perfectly now once set
RADV_DEBUG=nodcc %command%
The game hard-binds itself to the first two Xinput devices it finds, so if you want to play docked with two people on two different pads/sticks/etc., you need to use the quick menu options to change the controller order as the game does not allow you to assign players to controllers normally.
I reported the sprite corruption issue to the Proton Github a while back and they were able to provide a workaround for the issue (see https://github.com/ValveSoftware/Proton/issues/271#issuecomment-1173899741). They also have made a change to the Mesa drivers to apply this fix automatically with the next release (22.1.3 is the current Mesa version and the fix was merged in about a week after this came out, so hopefully it'll Just Work on the next stable release).
You will 100% want to turn the frame limiter off for this game, it caps itself to 60fps naturally and having the limiter enabled adds a significant amount of lag (about 3 frames/50ms of added delay).
If you can deal with the weird blockstun and wallslam visual bugs, the game runs fine. Great way to play it anywhere (except the bathroom).
Graphical corruption and artificating can occur from the following:
- Blocking (minor artifacting... but anyone who plays this game knows that nobody blocks)
- Wall slams (minor artifacting)
- Activating Heat or Blood Heat (heavy artifacting, can be mitigated by adjusting options)
(Basically, anything that uses the ripple/screen distortion effect the game has.)
The visual effect on blocking will cause a small, short distortion to occur on the blocking character (and any UI elements it overlays). The wall slam visual effect is a quick ripple from the point of impact that has corruption but quickly passes. The heat activiation effect will cover the entire screen and corrupt pretty much the entire background and HUD for its duration (up to 10 seconds).
There is a workaround for the Heat activiation corruption: if you go into the Options and set the Stage Animation option to Off, this will disable the full screen effect and the full screen corruption will no longer occur.
The one thing to keep in mind is that the game has no internal support for controller/player assignment whatsoever (unlike most modern fighting games), so you will need to use Steam Input's options to change the controller order. The built-in Steam Deck controls will always default to being player 1 until you change it.
If you're playing in a more competetive environment, you'll want to disable the frame limiter within Gamescope, due to the additional input latency it can introduce.
The game boots fine in both the current stable version of Proton and Proton Experimental but not Proton-GE.
The game on the Steam Deck only draws 1 watt (!!) from the APU at 60fps, so you could play this for 6+ hours on the battery if you turn the screen brightness and volume down.
The most consistent frame timing (at least based on the Gamescope graph) seems to come from turning off Gamescope's frame limiter and using the in-game Vsync option. Turning both off reduces input latency but can result in very sporadic frame timing issues (but this has not been rigiously tested by me, so take with a heap of salt).
Runs almost well on Steam Deck, let down by bugged visual effect that happens very frequently and becomes distracting.
Wall-slam distortion effects are instead displayed as black circles that have distortive effects on HUD elements and sprites they come in contact with. Very distracting and also present on other AMD graphics.
You must enable steam input or else your controller will either (not respond/have a input glitch i.e one up input could cause the main menu pointer to go haywire, or not detect the controller fully)
I have to disable the steam overlay cause it makes the game freeze (others may vary but for me its the fix that i have)
i mean its not the steam's fault its the dev itself (they used delay-based instead of rollback)
Nyaaa~~~
Game does not start
Non-steam Community Edition does start, but has glitched visual effects on AMD graphics.
Game crashes at intro video
The logos show, but after that it crashes instantly, no error. Tested on Proton 6.19-GE-2, 5.13-6, and current Experimental. Steam FPS counter shows it at 144fps instead of the only framerate this game allows, 60. Used DXVK_FRAME_RATE=60 to limit it to 60 frames, but still crashes.
Controller Detection
Makes P1 Controller both P1 and P2
The game itself works fine, opening AMV plays correctly.
Online multiplayer is NOT stable:
- Multiplayer in a private lobby worked fine for 1 or 2 matches, then disconnected. This persisted over multiple attempts.
- Playing in a private lobby on Windows with the same person worked fine. The issue is specific to playing under Proton.
Set Proton version to 5.0-10 and the game plays fine. The game auto-closes when set to the latest Proton version.
While having a few bugs, it still remains solid, I would direct players toward the Community Edition, which can be installed with Lutris.
Audio is of lower quality than Community Edition
There are artefacts on block, wave animation on block is corrupted.
Community Edition shares the same blocking artefacts.
protontricks 411370 lavfilters
Run protontricks tweak to install missing video codecs.
missing intro video, titlescren video and any other video this game might have
missing introduction introduction video, title screen video and any other video that this game might have.
missing introduction introduction video, title screen video and any other video that this game might have.
The game crashed on start up using Proton 5.13-4. Using Proton 5.0-10 it loaded and ran fine.
I had to disable Steam input in the game properties.
Intro video doesn't play. Audio works perfectly out of the box.
Intro video doesn't play
Proton-5.6-GE-2 GloriousEggroll
Installed 'xact' using protontricks Using ver 5.6 of proton by GloriousEggroll
Music playback was slow before installing 'xact' via protontricks. No audio in pre-fight cutscene.
Playable, could use a few fixes
Videos do not play, such as the intro
Gameplay worked fine, alt tab behaviour worked better than on windows, where it crashed the game there it runs fine here.
As other reports note, intro video does not play.
Unknown(> 10 hours with Proton)Like people have said, some video stuff isn't working. The game itself runs fantastic though
Unknown(> 10 hours with Proton)
No issues (someone mentioned the intro video didn't show up, I've never played the game before so I don't know which video they are talking about, so maybe that's not working)
Game works perfectly except that intro video is skipped.
No issues whatsoever, everything just works.
Runs perfectly.
MPEG videos (Opening, effects while loading matches) aren't playing at all, gameplay itself is, however, flawless. Works with controller (after disabling global settings use). Online multiplayer not tested.
Ran like a native title without much issues. At first there was a small controller issue where inputs from two different controllers was read simultaneously as if it was the only input from gamepad #1 but restarting the Steam with controllers hooked in fixed that problem.
UnknownRuns like a charm, I didn't tweak a single thing.
UnknownUnknownAll scenes play and gameplay is identical to native windows out of the box
UnknownUnknownFMVs do not play (Game's Opening and Background in VS screens). Game might crash upon changing resolution. Online not tested.
Unknown
