Force Push tied to clash detection?

I got an install request for a “no-button” saber. There are no external buttons, but on the chassis there are. So the majority of the experience will be with battlemode and/or gesture controls. I’ve also included Bluetooth for ease of other functions while operating with the chassis in place.

I’m struggling with Force Push. I’ve mastered the gesture at a certain Push Length setting, but it seems only to trigger with a clash. I tried to employ BM_CLASH_DETECT, but that seems to make the Force Push occur even less…so, I had to wonder, “is the function tied to a clash detection?” I’ve been tweaking my overall clash detection, my battle mode clash detection, the force push length, and I cannot seem to find a sweet spot to make the saber fun to use without a lot of false behaviors.

Can anyone provide some insight into how I should approach my testing of these features? Or, is there another define I should consider?

Edit: I should mention I’m obvs. running fett263 prop file, and OS6.7

I have to point out, my prop is not intended for use with no buttons.

That said, Force Push Length is the only setting tied to Force Push.

OS6 does do a “check” to confirm the Push didn’t end in a Clash, so if you have a clash or a hard enough stop to detect a clash at the end of the movement it will nullify the Force Push. This is because certain actual clashes at specific angles were triggering “false” push effects in OS5.

Of all of the gestures, Force Push is the most difficult and requires the most “practice” as you want a smooth movement perpendicular to the blade, if you have any tilt during the movement it will see it as a “swing” instead of a push AND as noted, if you stop the movement or “jerk” hard enough to have a clash detected the push will not trigger. It should be a “flow” movement for best results.

“Using the force takes patience and practice…” :wink:

1 Like

I may have misspoke. Each time I’ve successfully performed the Force Push it is preceded by a clash. In fact, when I was first testing what setting would be good for the BM_CLASH_DETECT, I was holding the saber still and lightly tapping my hilt-holding hand to see how hard I would need to engage lockup. I could easily trigger a Force Push at lower length settings in some of those taps.

I believe I have struck a “balance in the Force” at a bm clash detect of 7 and a force push length of 2 or 3.

Again, it’s not a no-button at all setup…more of a battle mode all the time setup. It’s actually quite fun when all the features are working well in tandem. But this is definitely going to be a gimmicky saber for a select kind of buyer. Mini tactiles are on the fully removable chassis for color change, font select, music, etc. But the Bluetooth connectivity is its saving grace.

Thanks for the insight, Fernando. Also, I was late, but I watched the OS7 stream after you ended last night. I’m not confident enough (or have enough spare time) to offer any alpha testing help. But I’m interested in the updates. Thanks again.

Okay…followup…the lower setting was the reason the clashes preceded the force and was triggering forces in the tap tests…this is solely about mastering the gesture. So, you’re right…just takes patience.

This define just sets the clash strength that differentiates a regular clash versus a lockup in Battle Mode 2.0, I can’t think of how this would affect Force Push in either way. A longer FORCE_PUSH_LENGTH means the “push” movement has to continue uninterrupted for longer to be detected, if you’re getting “false” clashes at 2 or 3 maybe up it a little and try to make the movement “smoother” instead of a jerking movement.

That’s essentially where I just landed. I bumped it up to 7 just to see, because I hadn’t yet gone above your default setting. I noticed it was all in the gesture…not the setting per se. I was able to trigger Force just as frequently (which is to say, not every time) when it was high as it was to low.