I have noticed clash is not at least not playing or being over ridden with another swing when auto blaster block mode is active with a one button prop. Shouldn’t there be a clash?
which prop though?
Its the default from txq. I havent got around to redoing it. I can do download most recent and try all the props with one button mode
I wouldn’t have any idea what that is. What they use and/or modify is anybody’s guess without seeing it.
Have you reached out to them?
I am going just re build everything as I need to update to most current version to rule out that out
Are you allowed to post and share the props under the TXQ terms ?
Edit: under the ProffieOS terms, they should be allowed to be shared. But I don’t want to get you/me/or anybody else, for that matter, in trouble for doing so.
If yes, please do share them. I collect props. Thanks. It’s for my multi_prop.h (aka: one prop to rule them all, and in your config bind them!), I would like to make multi_prop.h compatible with as many props as possible, if I can get my hands on them.
They just use Fett’s. Possibly an older version, but they aren’t making their own, that’s for sure.
1 Like
As Ryan said, all the Chinese manufacturers just use the props that come with the system. Fernando’s Fett263 is probably the most common, but I’ve had hilts in for repair that have used SA22C and NoSloppy’s BC_Buttons in the past.
1 Like
Can you explain this sequence exactly and what you expect vs what’s happening instead?
1 button set up. when you activate auto blaster block it wont do clash, or it will sometimes
I just read did the video ,it didnt have sound.
Sorry you have to look at my ugly mug with no make up and my hair not did
well if it is fett263’s prop, clash should toggle multi-blast mode OFF
Multi-Blast Mode = Hold PWR + Swing
Each Swing in Multi-Blast Mode will deflect Blast effect
To exit, click PWR or do Clash
To change it so that only pressing POW will exit, I suppose you could remove the
swing_blast_ = false;
from the case for
(BUTTON_NONE, EVENT_CLASH, MODE_ON)
No guarantees what else that affects, but I think it looks clear to do.
@fett263 would need to confirm or deny.
Its toggling ok enough but the clash detect over the blaster block detect is terrible. Like I have to hit it hard to some times get the clash instead of an auto block.
How high is your clash threshold?
I think Multi-Blast may be a “red herring”, clash detection accounts for swinging in prop_base automatically, so when swinging it requires more force for a clash.
Have you tested clashing while swinging without Multi-Blast on? Is there really a noticeable difference in clashes?
This is outside Multi-Blast, and Multi-Blast doesn’t have any relationship to clash, in fact a clash will turn Multi-Blast off.
// If we're spinning the saber or if loud sounds are playing,
// require a stronger acceleration to activate the clash.
if (v > (CLASH_THRESHOLD_G * (1
+
Clash detection isn’t controlled by the prop, and all Multi-Blast does is tell the saber to do a blast effect on each swing, so the swing or clash are detected before the prop does anything with the event.
You may want to fine-tune clash detection, there’s a lot of defines in OS7 that can be used to improve how clashes are detected.
See here:
1 Like
well I havnt had time to update… because I need to update to v7. But I shall report back.
I doubt much will change. in multi block its difficult to get a clash over the block. well its not turning off multi block
When you update, test clash while swinging with Multi-Blast on and off and see if there’s a difference. My guess is no, as Multi-Blast comes into play after the clash is detected. In which case, you probably need to fine tune your clash threshold and/or other defines for clash detection as noted above.