Jump to content
Dustloop Forums

Recommended Posts

Posted

Metal bitches are just plain attracted to Tager. Get it? With the magnets and the whatnot...

I think it's intended, they changed something around with how special inputs are detected. I'd really love for it to be returned to normal, though. I'm suffering as a pad warrior trying to 623C and accidentally tapping 6 at the end of the move and getting 236C instead about 40% of the time.

How bad is it? I use the 'Hori fighting commander 3 pro' pad and all these comments are starting to get me worried. Also someone mentioned that OD's register as RC's sometimes. All my hype is starting to turn into fear. Can anyone explain/compare it to another game (AH3 comes to mind)?

  • Replies 4.5k
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Posted Images

Posted
How bad is it? I use the 'Hori fighting commander 3 pro' pad and all these comments are starting to get me worried. Also someone mentioned that OD's register as RC's sometimes. All my hype is starting to turn into fear. Can anyone explain/compare it to another game (AH3 comes to mind)?

I've experienced the RC instead of Overdrive input several times. I can't remember if I checked the input display to see how dead on my inputs were but they sure felt adequately simultaneous. Is there a restriction that anyone is aware of on OD cancels? RC's can be used pretty much whenever but it got me thinking if OD cancels could only be used after the active frames have passed or something. If that's not the case and the inputs are just that strict, I may need to break down and map the A+B+C+D macro. :v:

And that's using an arcade stick...

Posted
I've experienced the RC instead of Overdrive input several times. I can't remember if I checked the input display to see how dead on my inputs were but they sure felt adequately simultaneous. Is there a restriction that anyone is aware of on OD cancels? RC's can be used pretty much whenever but it got me thinking if OD cancels could only be used after the active frames have passed or something. If that's not the case and the inputs are just that strict, I may need to break down and map the A+B+C+D macro. :v:

And that's using an arcade stick...

I might be wrong, but if i remember it right, OD Cancels can only be used whenever you can use a special cancel.

Is the DP motion "glitch" as bad as trying to do DP's in UMVC3?

Posted

You can only OD Cancel out of normals, AFAIK. If you're getting a Rapid Cancel instead, you might be trying to do it on a special.

Posted
You can only OD Cancel out of normals, AFAIK. If you're getting a Rapid Cancel instead, you might be trying to do it on a special.

It is out of any normal.

I have OD set to a shoulder button so I've never had a problem with accidentally doing a RC. But, they really messed with how you input stuff in this game. :vbang:

Posted
I might be wrong, but if i remember it right, OD Cancels can only be used whenever you can use a special cancel.

Is the DP motion "glitch" as bad as trying to do DP's in UMVC3?

6236 is still read as a DP in MVC3. MVC3 might be more strict in what it considers a DP, though. The problem in BBCP is that quarter circle motions take priority over DP's with most characters when you do a 6236 motion. It's apples and oranges.

It is out of any normal.

I have OD set to a shoulder button so I've never had a problem with accidentally doing a RC. But, they really messed with how you input stuff in this game. :vbang:

Make sure it's a normal that can be special-canceled. Certain normals like Bang's 3C can't be canceled directly into overdrive.

Posted (edited)
There are normals that you can't OD cancel like Nu's 4B.

I think normals that can't be special cancelled can't also be OD cancelled.

Makes sense I guess.

Edited by Boodendorf
Posted

If you guys read the wiki...

"You can cancel into Overdrive almost anytime you could cancel into a Special Move."

Posted
6236 is still read as a DP in MVC3. MVC3 might be more strict in what it considers a DP, though. The problem in BBCP is that quarter circle motions take priority over DP's with most characters when you do a 6236 motion. It's apples and oranges.

Make sure it's a normal that can be special-canceled. Certain normals like Bang's 3C can't be canceled directly into overdrive.

Some motions seem to prioritize DPs over QCFs and vice versa. I'm not really sure what causes it. Try doing Ragna's 623d versus Hazama's for example. Doing 6236d on both gets you dead spike for Ragna and jakou for Hazama. Very weird.

Sent from my SAMSUNG-SGH-I747 using Tapatalk

Posted

Made a quick video showing the "bug":

You can see the inputs are almost identical and yet I get DP for Jin and Tiger Magnum(236C) for Azrael. And even some of the time I get Sentinel Dump (623C) even when the input is still the same, which is even more weird.

Posted

Input priority is not a universal mechanic in a lot of games, and works on a character by character basis, I don't see any problem here.

The reason you are getting different results with the "same" input is BB's way of buffering and holding onto the button input. If you do 623+Button6 then you will still get the 236 as it cancels the 623+Button in the early frames into 236, it's easy to tell this as if you do 623+Button without the 6 you'll never get the 236 input. It doesn't seem like a glitch to me at all, just their decisions on what moves take priority on what characters. If it's the same in arcade, there's no patch coming and it's time to learn how to be accurate with your execution rather than blaming devs for a change.

Posted
Input priority is not a universal mechanic in a lot of games, and works on a character by character basis, I don't see any problem here.

The reason you are getting different results with the "same" input is BB's way of buffering and holding onto the button input. If you do 623+Button6 then you will still get the 236 as it cancels the 623+Button in the early frames into 236, it's easy to tell this as if you do 623+Button without the 6 you'll never get the 236 input. It doesn't seem like a glitch to me at all, just their decisions on what moves take priority on what characters. If it's the same in arcade, there's no patch coming and it's time to learn how to be accurate with your execution rather than blaming devs for a change.

To me it isn't about execution and more about why is it like that for some characters and not the others. If it is on purpose and specific between characters then it IS on devs which means they thought about the EXECUTION of the characters and what they are doing in their decision making. To me I see no reason why the input priority should be different between characters, more so if you're trying to be "hardcore" about execution requirements. If that's what you expect then all characters should require 623 DP inputs exactly, which is clearly not the case. So yea, it kinda is on the devs to make that kind of decision.

Posted (edited)
To me it isn't about execution and more about why is it like that for some characters and not the others. If it is on purpose and specific between characters then it IS on devs which means they thought about the EXECUTION of the characters and what they are doing in their decision making. To me I see no reason why the input priority should be different between characters, more so if you're trying to be "hardcore" about execution requirements. If that's what you expect then all characters should require 623 DP inputs exactly, which is clearly not the case. So yea, it kinda is on the devs to make that kind of decision.

I never said it wasn't their decision, but they're forcing you to be accurate with your inputs as they are not going to "fix" it if it's intentional, and there's nothing you can do to stop that. There are multiple reasons why they could decide to make it prioritise for some characters over others. For Azrael does it not help him get 236 after forward dash opposed to DP? Where as Jin he would be more likely to want the DP over the ice sword. There are potential reasons for it to be put in place like that, it might be without explanation to some but for the devs it might have been a good reason in their minds.

EDIT: Since I didn't see it the first time round, even though I understand that the problem exists, your final test with Jin doesn't work as Jin does not have a move that is 236C. Just saying.

Edited by TSS Atma
Posted (edited)
I never said it wasn't their decision, but they're forcing you to be accurate with your inputs as they are not going to "fix" it if it's intentional, and there's nothing you can do to stop that. There are multiple reasons why they could decide to make it prioritise for some characters over others. For Azrael does it not help him get 236 after forward dash opposed to DP? Where as Jin he would be more likely to want the DP over the ice sword. There are potential reasons for it to be put in place like that, it might be without explanation to some but for the devs it might have been a good reason in their minds.

EDIT: Since I didn't see it the first time round, even though I understand that the problem exists, your final test with Jin doesn't work as Jin does not have a move that is 236C. Just saying.

No, anything involving 236 after a forward dash needs to be TK'd so it should never be a problem of messed up inputs between moves. For the same reason I never had a problem with Bang's inputs overlapping since his nails had to be TK'd.

And for the other "test", the input would be the same regardless as shown in the previous examples. Not once did you see me get D Ice Sword when doing his D DP. So seeing Jin do C DP when I got Tiger Magnum instead for Azrael proves there is a difference. I'm sure there's some characters who have exact overlaps to test it properly with record but it obviously isn't needed.

The video was more for any kind of "proof" that there was a difference since people were talking about it. The question of whether or not it is intentional will probably never be answered but it won't happen at all if it is never brought up.

EDIT: Ragna and Jin have overlapping inputs across both 236D and 623D. I recorded Jin doing D DP, play it back with Ragna and get Dead Spike. So there you go if you wanted a different example.

Edited by zeth07
Posted (edited)
No, anything involving 236 after a forward dash needs to be TK'd so it should never be a problem of messed up inputs between moves. For the same reason I never had a problem with Bang's inputs overlapping since his nails had to be TK'd.

And for the other "test", the input would be the same regardless as shown in the previous examples. Not once did you see me get D Ice Sword when doing his D DP. So seeing Jin do C DP when I got Tiger Magnum instead for Azrael proves there is a difference. I'm sure there's some characters who have exact overlaps to test it properly with record but it obviously isn't needed.

The video was more for any kind of "proof" that there was a difference since people were talking about it. The question of whether or not it is intentional will probably never be answered but it won't happen at all if it is never brought up.

I meant after the forward dash, as in, not cancelling it. I wouldn't exactly see why you would but it's a possibility. There could be other reasons it happens and I'll do some testing in my own time tomorrow, I have a few ideas as to why it might be that way for some characters but not others. I'll post my findings in here.

The final test also isn't a good test as it does not cover all the possibilities as to why this is happening, such as say Jin's DP D not being a move where it could be cancelled in the early frames to go to something else. Your inputs at no point with Jin show 6236D and always show 623D6, if you want to tell me this test is fool proof you'll have to do it right by testing on multiple moves, the video doesn't prove the priorities are actually all that different if it is true that Jin's DP D cannot be cancelled out of the early start up frames and Azrael's DP C can.

EDIT:

Ok so I did some testing with Amane, Azrael, Ragna, Jin, Hazama, Hakumen and Nu

Doing 623(Button) produced a DP motion with every character.

Doing 6236(Button) produced a QCF motion with every character.

Doing 623(Button)6 more often than not produced a QCF with every character EXCEPT Hakumen and Jin, the only two characters that happen to use meter for their overlapping specials.

Take from that what you guys want, but it looks to me like the priority is in fact not different, and rather than doing extensive testing people jumped to conclusions that this was some kind of bug.

Edited by TSS Atma
Posted

So uh, anyone know what the coloured squares next to people's names are on netplay? I believe mine was green on day 1, yellow on day 2 and today it's red. But it started out at white each time.

Posted
lol ok

If you cannot face the fact that they are exceptions due to the metered mechanics which do not let them cancel the start up of their specials into other specials, and thus not the input system, you need to seriously let your ego go. 6236(Button) produced a 236 motion, which means that the 236 took priority over the DP.

Posted
If you cannot face the fact that they are exceptions due to the metered mechanics which do not let them cancel the start up of their specials into other specials, and thus not the input system, you need to seriously let your ego go. 6236(Button) produced a 236 motion, which means that the 236 took priority over the DP.

The whole start of this discussion was that people thought there was a difference of inputs between characters. You can't say the "priority is in fact not different", then literally say 2 characters have different priority than the others. Why they have different priority was the bigger question which is the result of there being a difference, it doesn't change the fact that it is true. Chill out.

Posted
I did the same testing you did and had different results, particularly with what 6236(Button) produced with different characters.

As far as the different results, I originally tested it as if I was doing it in a combo so 6236(Button) produced 236 at a steady pace, but if you go really fast with some characters it produces the DP. So far it still produces 236 on Nu, Ragna, Azrael, but produces a DP with Jin. I'm off to bed now as it's about 1am and I have work in the morning, I'll test it properly tomorrow but I can only see Jin as the exception and another person who was testing said Izayoi did the same thing(Though she has a charging mechanic on her specials? Might effect it).

The whole start of this discussion was that people thought there was a difference of inputs between characters. You can't say the "priority is in fact not different", then literally say 2 characters have different priority than the others. Why they have different priority was the bigger question which is the result of there being a difference, it doesn't change the fact that it is true. Chill out.

You disregarded my argument and time spent testing with your post, it seemed hostile, if you expected me to react in any other way then you are mistaken.

I'd also like to point out that Hakumen has no overlapping moves, I originally put that in to test something out, and it has given me my answer. Please test thoroughly the next time you guys want to make these kind of claims and discuss the results opposed to shouting "glitch! glitch!"

Posted

I put this in the Q&A thread, but I figured I'd put it here too. Mods if this is against the rules I'm sorry please delete this post.

Every time I go into online lobbies (where you control the pixel avatar) my PS3 console freezes in 5-10 seconds after being in the lobby. It crashes my console so hard that I have to unplug it from the wall because it won't turn off by itself. Player matches work just fine. Does anyone have any idea why this is happening?

Posted
I put this in the Q&A thread, but I figured I'd put it here too. Mods if this is against the rules I'm sorry please delete this post.

Every time I go into online lobbies (where you control the pixel avatar) my PS3 console freezes in 5-10 seconds after being in the lobby. It crashes my console so hard that I have to unplug it from the wall because it won't turn off by itself. Player matches work just fine. Does anyone have any idea why this is happening?

I have no idea, especially since I don't have the game. But something like that happened to me once in another game. Have you tried to re-install the game just to make sure?

Guest
This topic is now closed to further replies.

  • Upcoming Events

    No upcoming events found
×
×
  • Create New...