Yes indeed you will. There won’t be any sort of line at Revelations, if you show up with money you get a Hit Box.
ToXY flew in the day before and was still kind of jetlagged, he wasn’t very confident about his Hit Box abilities yet. Rest assured he has started his Hit Box training with Dustin and next week I would not doubt he picks up Hit Box for WNF.
Im sorry if this has been asked before but what kind of pcb’s do you guys use in the hitbox and what about ps360 boards?
We also use the Cthulu board.
How long is the line to get one of these? I’m definitely interested.
thanks for the quick reply guys…
We’re not filling orders right now since we’re taking everything with us to Revelations, so the line is fairly long and won’t see any movement until after Revelations, sadly.
i’ve been playing on hitbox for about 3 months now, and the only issue i’m still having is half-circle motions. (only in marvel, not super because the inputs work as a shortcut in super)
The way my inputs look, the down input never comes out. I just get:
:db::df::f:
It’s especially tough when I’m trying to tron lvl 3.
Any tips?
I don’t think there’s a trick to it, just gotta hit that ‘2’ in numpad notation
have you done a 720? not sure the best way to do that
The best way to get a perfect half circle is going to take some mental gymnastics. You have the finger dexterity to get it, now you just need the proper roll technique. Here’s what I want you to practice, go to training mode and think of the motion as: Back, quarter circle forward. Do the quarter circle as fast as possible after hitting back.
The way I used to do it on keyboard was to split the half-circle motion into two quarter-circle motions. HCB would be QCF, QCB.
Sounds cool…
This thing seems like it would make execution heavy games a joke(esp. from a lefty like myself) but seems less fun to have all buttons…
Winning is more important but whatever… good shit… whoever put the input for jump at the bottom is a genius… until I saw it action, I thought otherwise…
This. The reasoning is that you aren’t ever hitting just the down. You are going from downback to downforward because as you left of the back you are hitting the forward at the same time. If you delay pressing the forward a little bit so that you are fully releasing the back it will give you a singular down input. The reason kashkabald’s strategy works is because by splitting in to two motions he is completely releasing the buttons inbetween allowing for a clean down at the end of the first qcf and at the beginning of the qcb.
You guys should just set up the electronics to register back+down+forward as down, there isn’t any other input you’d ever want it to be, and it’s intuitive (the forward and back “cancel”) and it makes a faster and more reliable input when you don’t have to program yourself to lift your back button a frame before you hit the forward to give a frame for down. 360s/720s would benefit a lot from doing that with the other cardinal half-circles too (i.e. make down+forward+up register as forward, and so on). It would give me an excuse to buy from you instead of screwing around soldering with off the shelf pcbs that will have unpredictable simultaneous directional input results.
The problem with half circles isn’t that people are hitting left, down, and right at the same time, it’s that they’re straight up skipping the down input all together and going from down back to down forward. There’s no way to fix that from the board without programming a macro that does the motion for you, the only answer is to go into practice and fix it yourself, because the board isn’t the one making the mistake.
As for the SOCD issue, none of our boards have that problem. Our Cthulu board cancels all SOCD’s to neutral and our PS360 board sends all left+right inputs as left and all up+down as up forward.
Well just take it as an anecdotal data point from me, the problem with missing the down in half circles is having B+D+F simultaneously activated for just a couple of ms during the motion, not from moving from D+B to D+F without any solo D. Describing the bad motion is, sequentially, “B finger down, D finger down, F finger down, B finger up, D finger up”, the good motion being “B finger down, D finger down, B finger up, F finger down, D finger up”. The difference is extremely small when you are trying to get the fastest version of the motion down, and if it was solved like I suggested, which is really nothing like a macro, the hit box type of control would be as unambiguously fantastic for HCB/HCF as it is for DP and QCF/B
I haven’t heard of anyone hitting back and forward at the same time when doing a half circle. I’d say it’s improper technique and even if our board allowed such inputs there wouldn’t be any advantage to it over rolling in a more traditional way. All it takes is practice.
I think in one of toodles’ threads, he said something about one of his PCBs neutralising SOCDs, so B+D+F = D. If this is true, isn’t a firmware flash all that’s needed for this to make everyone happy?
Honestly I haven’t been keeping up with Toodles’ firmwares. Hell, I don’t even know anything about half of his boards. He’s helped us get rid of the SOCD problem, so I suppose he could make that happen, but at the moment and in the foreseeable future there is no reason to do so.
I guess I should drop this bit of minutia, but one more point. I wasn’t arguing for the “bad” HC motion, but rather just for relaxing the conditions for a HC so that it encompasses one more input - at zero cost in terms of freedom or precision if you would otherwise turn B+D+F into a neutral or DB/DF. On a HCF the B+D+F = D sub makes it so you can pick up your B finger either before or after you depress F instead of only before. It is a judgement call on my part how much that dual availability helps the fastest HCs, but analytically it can only help, not hurt.
I’d love to hear from Toodles whether that can be done in firmware.