E3 Demo Bug/Glitch Reports

Hey, all. Thanks to the email-slash-survey issues a lot of people were having as evidenced by half of update 41 being devoted to them, I only just got the demo today.  I took a little time to slap together a video showcasing the bugs I've found.  Half of the things I discovered were of course already mentioned here over the last week, so I've limited the video to the bugs which don't seem to have been covered, and which I know can be reproduced by anyone with no difficulty.  Here is some elaboration:

• Backstep bug 1:  Backstepping has a sequence of three animation phases: 1) Jumping backwards. 2) Landing. 3) Transitioning to neutral pose.  Interrupting the backstep with an attack (weapon or magic) is supposed to permanently interrupt the animation sequence, but instead it only delays it; once the attack animation sequence is complete, the remaining backstep animation phases play out, assuming no further input from the player.   For example, interrupting backstep with an attack during phase 1 (jumping backwards) will result in phases 2 (landing) and 3 (transitioning to neutral pose) playing out once the attack animation sequence completes.
  

• Backstep bug 2:  Furthermore, after interrupting a backstep with an attack, if the next action is another backstep, and it is done before the full sequence of animations (attack and backstep) has been allowed to play out, then the first animation phase of the backstep (jumping backwards) gets interrupted partway through, resulting in a visible pause in the animation.  This phenomenon can be readily reproduced by backing yourself against a wall and spam alternating attack/backdash.

• Backstep bug 3:  The backdash cannot be interrupted by moving left or right on the control pad.   This in turn prevents the player from attacking in the direction of the dash, which is a significant gameplay oversight.   In Symphony of the Night, which Bloodstained very obviously seeks to imitate, literally the only thing that doesn't instantly interrupt the backslide is attempting to move Alucard in the opposite direction from the slide (the direction he's facing), and even this does interrupt it after a quarter of a second.  While this oversight is not technically a bug, it is a significant enough detriment to the gameplay and the obvious intent of the game that I consider it to be a bug.  It certainly deserves just as much developer focus as a proper bug.

• Jumping bug: Jumping and attacking (with the sword) at the same time causes the weapon to appear in Miriam's hand for a couple of seconds, but with no attack.
  

• Terrain bug: Jumping down into an area where the first platform is high on the screen, such as the middle vertical portion of the map with the Amy enemies, can result in Miriam arbitrarily falling through / missing said platform on her way down.  This phenomenon is likely tied to the swaying of the playfield.
  

Other observations:

• Attacking while on the ground (or during a backstep) has four animation phases: 1) Attacking. 2) Transitioning to en garde pose. 3) En garde pose. 4) Transitioning to neutral pose.   If the weapon is changed during phase 1 or 2, the remaining animation phases will continue to reflect the original weapon, meaning for example that swapping from sword to boots during an attack will result in Miriam assuming the sword's en garde pose, but with no sword in her hand.
• Changing weapon (mundane or shard) immediately before an attack with said weapon lands causes the attack to pass right through the enemy.

I have other observations and comments to offer that aren't bug-related.  I'll save that for tomorrow and a different thread.

I've noticed a funky little bug with hitboxes, one with dropped items, another with the "Amy" enemy. When I was fighting a pair of Amys in the vertical area with only two Amys, I slashed at the wall while one of the Amys was deep in the floor, and managed to kill it somehow. The dropped item glitch happened in the same room, the dropped item (an ether) was on a platform above me, I slid, and I grabbed it while it was above me. I wish I had video proof, but I couldn't recreate it, sadly.

So I'm unable to get Bloodstain to work. I  keep getting a message saying that I need to install Microsoft Visual C++ 2015 Runtime and I already install it several times already, but I keep getting that message.

The boss tentacles have tricky hit area. sometime, it suddenly hits you from a safe spot. It's like there is a short invisible range attack.

Sometime, the hit area become suddenly smaller and you can't damage anymore.

Also to what @zankoukanshokai found. I too found this to be a problem especially in this room during speedrunning. Its most noticeable here.

 I don't know if this specific bug is reported, but I have seen similar bugs for the cutscene.

It's definitely a good thing and should not be changed. It's more real and authentic that you used the ability and you'd still see it. Compared to using it and it magically vanishes.

 

I am on a roll with the bugs today. I found this one when I was killing Amy's for the Amy shard. It originally happened when I wasn't recording, but I recreated the situation, so I got up on the ledge and normally you will just see Miriam's legs with her standing there and nothing happening. But if you hold down the down direction, you get that black screen and sound until you spawn on the floor. So you get two bugs in this video. One with a ledge you are not suppose to be on and the second the black screen from pressing down while on that ledge. 

This bug is really alike the one I found earlier, but I found out if you just press down  once instead of holding it, there is a really good chance for you to glitch out of the map and land on a grid map. I haven't tried this on other parts of the map yet, but I will see if it's possible there as well. If the gridmap wasn't there I would just be falling until the game crashes.




Added: I tried to see if there was anywhere else on the map that had this similar problem but it doesn't seem like it. But I tried the glitch many more times and got different results. 

I Glitched down one floor.

This one is just Miriam falling for a long time before crashing. On the other one it crashed a lot sooner, so you didn't get to see what happens after a Miriam falls for a long time, nothing really new just additional info on what happends the longer you fall.


Second Addition: This is a really long video that shows what I was able to do with the glitch, nothing super interesting, but I tried to keep myself in the ship, to see if it was possible to drop down to the bottom of the ship, as a speedrun tactic, but it's down one floor, or fall out of the map, or screen confusion. It's a boring video but it shows some glitches and bugs here and there that I haven't mentioned or don't really think is worth mentioning. All of these glitches comes from a hidden platform, so most if not all can be fixed by just removing it.


Since I expect most to just skip most if not all of the long video, I noticed a big drop in quality from all the glitching, don't know if it would happen to anybody, or if my computer is just bad. Pictures in the link below for a comparison.

imgur.com/a/f6JTr