haha. you’re the best. can’t tell you how much I appreciate it. I didn’t make a test preset. the blade just
doesn’t light up at all. I took one of the presets and rearranged it with no luck. also, the one with three identical blade styles doesn’t work. I uploaded the old config to make sure I didn’t short something out or get a loose wire while messing with it. I didn’t. the blade still lights up with the old config.
what do you mean with the the old config?
What’s the difference between old and current then? Because that’s how deduction works.
I meant the original. before we altered it.
I just added a “test preset”. looks like this:
StylePtr<Red>(),
StylePtr<Green>(),
StylePtr<Blue>(),
"test"},
crystal and blaster both blue. blaster lights up blue in blade mode. how does that make any sense?
Bizarre.
It doesn’t make sense at the moment.
Try 3 presets and move just Blue in each spot?
Blue
Black
Black
Black
Blue
Black
Black
Black
Blue
Also try them in both preset arrays (one copy in saber and same in blaster.)
so, I figured out that the blade must be the third one. for all the presets that I don’t have a third blade indicated, the blaster doesn’t light up. but with the third blade, it still lights up the blaster and not the blade , even when in blade mode.
I just need to figure out how to move it from the blaster to the blade.
uploading the blue/black presets now
okay, three different results this time.
the blade is definitely being lit up by the second preset array. I got no light in the blade until I added those test presets in the second half of the config. now, the blade turns on when I enter blaster mode and plays the font of the blade, not the blaster. so, now, every preset has the same blaster font (which sounds like a blade), and they all light the blade up blue when I enter blaster mode. also, the button does nothing in blaster mode now.
Sorry, not trying to be picky, but troubleshooting requires clarity. One long sentence of what’s happening is hard to follow. Maybe you could answer the following questions inline by quoting them and replying.
So do you mean that when you cycle between 3 presets that look like this:
{ "AnyFontNameHere", "",
StylePtr<Blue>(),
StylePtr<Black>(),
StylePtr<Black>(),
"test 1"},
{ "AnyFontNameHere", "",
StylePtr<Black>(),
StylePtr<Blue>(),
StylePtr<Black>(),
"test 2"},
{ "AnyFontNameHere", "",
StylePtr<Black>(),
StylePtr<Black>(),
StylePtr<Blue>(),
"test 3"},
that the main blade only lights up blue when you’re on test 2?
Does this mean that the above 3 presets in the saber presets section don’t actually light the main blade at all? And that test 2 only lights the main blade when these presets are used in the blaster presets section?
The font that’s listed in the preset is going to play reagrdless of which prop is active; blaster or saber. So if you use a saber font iin a blaster preset, you’ll have no sound with button presses because it’s looking for “blast.wav” files when you press the Fire button. Saber fonts use “blst.wav” files for baster bolt deflection. So since there’s no sounds to play for your shots, you get duds. Understand?
To properly test, you should just use “b;aster1” for all 3 of the test presets in the blaster section, and like “Blue” for all 3 test presets in the saber presets section.
See previous answer/explanation.
I think it would be best to work with just one thing at a time. Let’s get the saber stuff working first, make sure that’s right, because then the blaster stuff should sort of automatically just work.
sounds good. here’s what I have for the first 4 presets in both sections:
StylePtr<Blue>(),
StylePtr<Black>(),
StylePtr<Black>(),
"test"},
{ "Staplegun", "tracks/bgm1.wav",
StylePtr<Black>(),
StylePtr<Blue>(),
StylePtr<Black>(),
"test"},
{ "Staplegun", "tracks/bgm1.wav",
StylePtr<Black>(),
StylePtr<Black>(),
StylePtr<Blue>(),
"test"},
{ "Staplegun", "tracks/bgm1.wav",
StylePtr<Red>(),
StylePtr<Green>(),
StylePtr<Blue>(),
"test"},
now, the button works correctly with the correct sound fonts on all the presets, but they all light the blade up when switched to blaster mode. all of them, not just the test presets.
the blade lights up in every preset now, but only in blaster mode. I think the actual blade has to be indicated in the 2nd section the way it is set up for some reason.
nothing in the first section appears to light up the blade. it seems to only light up when I added the config to the bottom section.
the only difference I see in the first four “test” fonts is that the blaster stays lit up when the third blade style is indicated as blue, even when the saber is deactivated.
wait! maybe I figured it out! I hope you didn’t already say this. do I need to switch these two sections:
{ NO_BLADE, WS281XBladePtr<133, bladePin, Color8::GRB, PowerPINS<bladePowerPin2, bladePowerPin3>>(),
WS281XBladePtr<1, blade2Pin, Color8::GRB, PowerPINS<bladePowerPin4> >(),
WS281XBladePtr<1, blade3Pin, Color8::GRB, PowerPINS<bladePowerPin5> >(),
CONFIGARRAY(blaster),
"01_BlasterSave"},
{ 0,WS281XBladePtr<133, bladePin, Color8::GRB, PowerPINS<bladePowerPin6> >(),
WS281XBladePtr<1, blade2Pin, Color8::GRB, PowerPINS<bladePowerPin4> >(),
WS281XBladePtr<1, blade3Pin, Color8::GRB, PowerPINS<bladePowerPin5> >(),
CONFIGARRAY(saber),
"00_SaberSave"},
should the “no_blade” identification be on the second set of identifiers, or should the whole sections be switched? would that do anything?
I don’t know why or how this worked, but I got it going! at least for now. I changed the “no blade” indicator and then had to re-flip flop all of the blade settings and blaster setting, and for some reason, it works now! I still need to mess with it a bit to make sure, but for now, everything is working! can’t thank you enough for all your help. thanks a ton. it’s a Christmas gift for my son to go with a kanan for me, but I want to give it to him early for a trip we’re going on. so happy I got it working. it’ll mean a lot to us both, thanks.
NO_BLADE should have CONFIGARRAY(blaster)
The other should have CONFIGARRAY(saber)
Everything else that matters is identical, so shouldn’t be any different, which is why I’m finding this strange.
If you have a blade style for the main blade in the blaster section (or anywhere ever) that is just StylePtr<Black>(), it should never light. Yet that’s what you are apparently having happen?
PLease post what it used to look like and what it is now. I need to sleep tonight 
haha. yeah, me, too. I was able to get a couple hours of sleep before the kids woke up, 
. just in time, too. my brain was completely fried by the time we finished! here’s what I ended up with that worked.
at least I now have a baseline that I can go back to in case other things fail. I’m still hoping to switch it to Fett’s controls with edit mode and voice menus and such.
thanks again for all your help last night.
I didn’t read the whole thread, just looked at the paste bins.
I think I might have spotted a problem:
#define PROP_TYPE SaberBlasterProp<Blaster,SaberFett263Buttons>
should be:
#define PROP_TYPE SaberBlasterProp<SaberFett263Buttons,Blaster>
It is a saber-blaster-prop and not a blaster-saber-prop. That is why your buttons might be acting wrong. In the blaster mode, the buttons are “internally changed” to mimic the blaster but if the mimic is applied to the saber, idk what would happen.
thanks. NoSloppy found that, too, at one point. that was definitely part of the problem.
You can also
#define BLASTER_SHOTS_UNTIL_EMPTY //Not defined = unlimited shots.
I have been told but I never tested it.
if you want fett263, you can change this:
#ifdef CONFIG_PROP
#include "../props/dual_prop.h"
#include "../props/saber_sa22C_buttons.h"
#undef PROP_TYPE
#include "../props/blaster.h"
#undef PROP_TYPE
#define PROP_TYPE SaberBlasterProp<SaberSA22CButtons, Blaster>
#endif
to this:
#ifdef CONFIG_PROP
#include "../props/dual_prop.h"
#include "../props/saber_fett263_buttons.h"
#undef PROP_TYPE
#include "../props/blaster.h"
#undef PROP_TYPE
#define PROP_TYPE SaberBlasterProp<SaberFett263Buttons, Blaster>
#endif
thanks, this is what I will be trying next. I just looked at the config I ended up using again, though. it works, but it’s definitely not the correct way to do it. I have blade presets in both the blade and the blaster presets. I don’t think they need to be in the first session. I don’t really know. my first time with a blaster config, and hopefully my last !