Config code(Third Aux button for dual blade) so both blades have individual effects with clash/blast

[Joseph_Hill]

I wonder if it is at all possible to use the 3rd Aux button for a second main blade, Like for a dual blade setup. I have seen others online using a whole 2 proffie boards in one hilt for dual blades and I am kind of picky when I build my stuff. I have an issue with turning on both boards just to hear either off or not quite synced boot sounds. I would also like if somehow I could just code in the 3rd Auxiliary button like pow and aux are already in the config, To effect just the second blade and not the other. I couldn’t find much information anywhere about this topic.

[Fett263]

Not specific to 3rd button but the abilities needed for controlling 2 blades with one board is in OS7 already via my prop. I’m hoping to get time to set up the interfaces and code in Phase 3 of my Style Library.

"Proof of Concept" Secondary Ignition/Retraction Effect for Staff / Dual Blade Sabers for ProffieOS7

["Proof of Concept" Secondary Ignition/Retraction Effect for Staff / Dual Blade Sabers for ProffieOS7] I have the initial proof of concept built out for handling a secondary blade on a staff saber like Darth Maul or the Inquisitors. If you want to run two physical blades from a single Proffieboard these new Secondary Ignition/Retraction Effects and the new Conditional Effects will allow you to gain independent control over each. To start, in your presets you will set up one blade as the Primary blade (this will work just like a single bladed saber) in the style code, then you will set up the “other” blade as a Secondary blade in the style code. This will allow you to have a separate ignition and retraction for the Secondary blade that you can control in several ways. The way it will work is your Primary blade will control if the saber is ON or OFF through normal button/gesture controls. After igniting the Primary Blade you can then set up the Ignition and Retraction for the Secondary blade, meaning you can ignite and retract the secondary blade as long as the Primary blade is ON. If you retract the Primary Blade through normal controls this will also retract the Secondary blade and turn the saber OFF. The Secondary Retraction only runs while the blade is ON and only retracts the secondary blade. The Secondary Ignition/Retraction use the existing out.wav and in.wav sounds for your font but play them independently from the Primary allowing you to get the sounds to match. There are a few ways the Secondary Ignition/Retraction can be controlled. a 3rd Button (easiest will be addition of a 3rd button to the saber) a new button control for 2 button sabers (1 button may not be possible without someone removing a feature and modding the prop on their own unfortunately) - TBD a separate Conditional Effect - in the demo I set up a Conditional Ignition effect on the Primary Blade, if the blade is held parallel at the moment of Ignition, the Secondary Ignition will trigger once the primary blade finishes igniting we can add a delay to this as well, a la Darth Maul in TPM. We can actually set many different Conditional Effects and have different ones in each preset if we wanted. In addition, for this demo I have set up Conditional Effects for Blast and Clash, this allows us to choose which blade the effects appear on because we don’t want two blades showing the same effect. The Conditional Effects control which blade the effects appear on fro…

[astromech]

I feel like independent blade control is one of the must under-talked-about features from OS7.

[Fett263]

Because I haven’t had time to really roll it out yet and setting it up is a tad complex so the interface needs to take a lot of guesswork out of it for most users. It’s on the list of things to do it’s just got a lot of pieces to make it all work together. Once the library and config helper are able to support it, it will get a lot more attention. The biggest hurdle with OS7 is we added SO MUCH, most users aren’t aware of a fraction of the potential now, hence the work to get it into the library where it’s visible and easier to implement. I feel like I have well over a year’s worth of stuff still waiting to get added, this OS almost feels like 4 full fledged versions released as one with what we fit into it…

[astromech]

You guys are working too hard!

[Joseph_Hill]

Thank you fett263! You are a really big help to the saber community.

Darth Maul is exactly how I would do it. The concept secondary blade igni/retract is perfect, Maybe in the future the 3rd aux button can be just for blast only on secondary blade effect.

[Fett263]

@Joseph_Hill

Maybe in the future the 3rd aux button can be just for blast only on secondary blade effect.

The issue is “secondary” blade isn’t actually something a button can “see”. The buttons (prop) doesn’t know what is wired to the board or what you call your first blade, second blade, crystal, etc. The buttons (prop) just activates effects or functions. How those are translated to what you see and where you see it is handled by the style code. So you couldn’t set a button to do Blast on a specific blade, it would do EFFECT_BLAST and whatever blade has style code for EFFECT_BLAST will show. That’s why we developed the “conditional” effects. The blades all receive EFFECT_BLAST but it only shows on blades that meet the condition, like pointing up. If you really wanted a 3rd button you could write a custom effect but it would be specific to your saber and you’d have to figure out how to style accordingly so that only the blade you want shows it. Its possible but a lot of extra work for no real gain. I developed everything to work on 1 or 2 buttons since that encompasses 99.9% of all builds, a 3rd button is rare so there isn’t a need or much support IMHO.

[Joseph_Hill]

Ok that makes a lot of sense. It does sound like it would be complicated now that you have explained it all. Conditional effects do the job well enough thank you for helping a fellow out.

MTFBWY

[NoSloppy]

@Fett263

setting it up is a tad complex so the interface needs to take a lot of guesswork out of it for most users.

I like guesswork and dabbling.

[Fett263]

@NoSloppy

I like guesswork and dabbling.

You’d be the exception in my experience, this one took a LOT of trial and error, as Yoda would say “failure is the best teacher” there were many failures before I got it working…