I added this to my post above. Happy now ?
Sure, thanks.
I’ll back up @olivierflying747-8 here a little by saying that if what you’re advertising as easy to setup is the barebones version of your prop, you’re not really advertising the advanced features of your prop that would make it interesting.
If someone doesn’t spend the time to read through and watch your videos, they’re left with an experience that’s not unique.
IMO other button mappings are more friendly. You say they can be customized, sure, but that’s not out of the box. That requires reading through and trying to tweak things and that alone is more than a lot of people want to do.
If all they want is a different button layout and/or approach to doing things, other props are a better option, especially at this beginner level.
There’s very little your prop actually offers to them, and it feels equally disingenuous to say you can “only use the fancy features through my prop” (paraphrased) when those aren’t features normal people care about anyways.
It’s, at least as, equally fear-inducing that someone may “miss out” on proffie because they didn’t use your prop, which isn’t true. Certainly not, again, at this entry level situation.
“It’s very easy to get started” and “there’s options for everything to set things up how you want” and “watch all the videos” are mutually exclusive. Even if it was the easiest thing in the world (which I don’t really think they are either, having helped a lot of people myself), that’s still a substantial time sink. That’s more than many if not most people want to invest.
TL;DR I think Olivier is very correct, and I don’t think what he’s saying is anywhere near “misinformation,” or malicious, or misleading. It’s true that your prop and such “advanced features” require more effort, and that there’s little difference between your prop and others for most people, and that other people may prefer other prop setups, and they should be encouraged to try them.
1 Like
Fair enough and noted, from my perspective I’ve modified my prop to make it easier for customization and able to support the needs of all levels of users that I have engaged with or whom have provided feedback in previous OS versions.
In trying to “be all things to all levels of user” while also introducing new features with each OS version I’ve needed to add more defines, which in turn adds more documentation. The users I have heard from and interacted with, by and large, are able to get what they want out of my prop pretty easily either by using my prop page and config tool or asking questions here. I can’t speak to those whom I have no interaction with. Each OS update I’ve addressed all input I’ve received.
I still think telling a user they need to be advanced or an expert is misinforming them. Some reading is required, but assuming “some reading” requires advanced skill feels very misleading. I’d rather leave it to the user to determine than tell them only advanced or experts can undertake my prop because that is counter to all the effort I’ve put in to make it user friendly for all levels (from the actionable feedback I have received).
But I can see there are some who prefer other props, so it’s good there are options.
I think you’re confusing advanced Styles in the library and functionality in my prop. To use my prop a user only needs to read the top of the prop.h or refer to my prop page for set up, controls and defines.
The library and many of the advanced style functions do require more understanding and there are separate videos recommended to help, particularly the OS7 functionality. But that is separate from simply using my prop and fully dependent on if the user wants to implement the advanced features at the preset level. Yes, advanced styles are more in depth but that is independent of simply implementing and using my prop.
I’m not, but I am intentionally conflating them, same as you in your initial message.
Which is what I said.
Not sure I follow, to use and implement my prop on the config the IP originally posted, they’d just need to follow the set up on the prop page I provided:
To enable a prop file you will add the following to your config file (after the first #endif from #CONFIG_TOP). If you're unsure refer to the manual for more information.
#ifdef CONFIG_PROP
#include "../props/saber_fett263_buttons.h"
#endif
And they need the Voice Prompts added per this step:
Set Up for Voice Prompts (Required)
Link to Voice Prompt...
These voice sound files should be included in a "common" folder in the root of your SD card and each preset in your config should be set up with the "font" folder and "common" in font search path like so:
{ "font;common", "font/tracks/track.wav",
StylePtr<...>(),
"name"
},
That would enable the basic controls and features to begin using my prop, I don’t see how any of that is advanced or expert level. If they want to enable features or change controls then they’d add the defines accordingly but those are optional.
Now separately, if a user goes into the library to build a Special Ability or Mini Game or other advanced style, yes there are videos and additional set up needed, but that’s independent of simply enabling and using my prop. First, if the user wants those advanced features many rely on my prop. Second, there’s very specific set up needed, while its documented in the style code the library provides the videos are “Recommended” to help users get started. I don’t know of any other way to make advanced features user friendly, the library is doing 95% of the heavy lifting, if a user wants those advanced features, regardless of skill, they need to handle the last 5% to get it working. But that’s based on the user wanting to use them, not simply implementing my prop.
You’re, intentionally or not, failing to understand the point of what I said.
I didn’t say it was. No one said that was as far as I know.
I’m not going to keep going back and forth about it though. I think this thread has been hijacked enough.
Agreed on back and forth.
My initial reply was because Oliver said my prop requires “advanced or expert skill” to use.
I replied to clear this up as it is misinformation from my POV. You replied defending his POV and our back and forth began. I just want to clarify that just implementing and using my prop doesn’t require anything near advanced or expert skill.
Agree. Sometimes I feel a little paralyzed by too much choice, but that’s not the same as things being difficult.
Also, Fett263 has been cool about bringing over any feature I’ve ever been curious about.
So yeah, original poster, IMO, Fett263’s prop is great as it does things you may want or be curious about, and it runs easy ‘out of the box’
1 Like
Thank you all so much for your help, I think I’ve pretty much got it dialed in, just need to actually solder everything up and figure out how to make a chassis to fit my Vader saber. I decided to go with the Fett Prop just because if I keep it basic, it works for me, but I can also unlock things as I learn more about it. Can anyone direct me to a Vader blade font to add? None of the stock fonts seem to be very Vaderish.
There’s a lot of great options so this is not a full list by any means. I personally use JuanSith, KSith and Kyberphonic’s fonts but there are many others. Just do a Google search “Vader font for Proffie” and you’ll find a plethora of options you can preview yourself depending on the film(s) you’re chasing.
Thank you so much!
You’re welcome
There are quite a few free fonts, but to get one you might consider accurate to the movies will be a paid font.
They aren’t too much, however. (Imo)
So I decided to go with Kyberphonics Father V2. My question now is, how can I upload just this font onto my saber? Using my one button and kill switch set up that I did previously.
1 Like
1 Like
From all the tutorials I can find, most sound fonts come with a sound font code to add into the config file, mine did not. Is that normal?
Yes, its pretty normal to not have a style codes. Especially from the big ones like kyberphonic.
You can generate good codes from @Fett263 library at Fett263's ProffieOS7 Style Library - Public Access
I didn’t make this, I found it and it is an older Vader style (from OS5.9), but it is what I am using for my Vader font:
StylePtr<Layers<
AudioFlicker<RgbArg<BASE_COLOR_ARG,Red>,Rgb<128,0,0>>,
LockupTrL<Layers<
AlphaL<AudioFlickerL<RgbArg<LOCKUP_COLOR_ARG,Rgb<255,240,80>>>,Bump<Scale<BladeAngle<>,Scale<BladeAngle<0,16000>,Int<4000>,Int<26000>>,Int<6000>>,Scale<SwingSpeed<100>,Int<14000>,Int<18000>>>>,
AlphaL<LemonChiffon,Bump<Scale<BladeAngle<>,Scale<BladeAngle<0,16000>,Int<4000>,Int<26000>>,Int<6000>>,Int<10000>>>>,TrConcat<TrInstant,TransitionEffect<Rgb<255,180,50>,LemonChiffon,TrInstant,TrFade<200>,EFFECT_LOCKUP_BEGIN>,TrFade<400>>,TrConcat<TrInstant,TransitionEffect<LemonChiffon,Rgb<255,180,50>,TrInstant,TrFade<200>,EFFECT_LOCKUP_BEGIN>,TrFade<400>>,SaberBase::LOCKUP_NORMAL>,
ResponsiveLightningBlockL<Strobe<RgbArg<LB_COLOR_ARG,White>,AudioFlicker<White,Blue>,50,1>,TrConcat<TrInstant,AlphaL<White,Bump<Int<12000>,Int<18000>>>,TrFade<200>>,TrConcat<TrInstant,HumpFlickerL<AlphaL<White,Int<16000>>,30>,TrSmoothFade<600>>>,
ResponsiveStabL<RgbArg<STAB_COLOR_ARG,Orange>>,
ResponsiveBlastL<TransitionEffect<RgbArg<BLAST_COLOR_ARG,Rgb<255,240,80>>,LemonChiffon,TrInstant,TrFade<50>,EFFECT_BLAST>,Int<400>,Scale<SwingSpeed<200>,Int<100>,Int<400>>>,
ResponsiveClashL<TransitionEffect<RgbArg<CLASH_COLOR_ARG,Rgb<255,240,80>>,LemonChiffon,TrInstant,TrFade<100>,EFFECT_CLASH>,TrInstant,TrFade<400>,Scale<BladeAngle<0,16000>,Int<4000>,Int<26000>>,Int<6000>,Int<20000>>,
LockupTrL<AlphaL<BrownNoiseFlickerL<RgbArg<DRAG_COLOR_ARG,White>,Int<300>>,SmoothStep<Int<30000>,Int<5000>>>,TrWipeIn<400>,TrFade<300>,SaberBase::LOCKUP_DRAG>,
LockupTrL<AlphaL<Mix<TwistAngle<>,Rgb<255,200,0>,DarkOrange>,SmoothStep<Int<28000>,Int<5000>>>,TrWipeIn<600>,TrFade<300>,SaberBase::LOCKUP_MELT>,
InOutTrL<TrWipeSparkTip<White,1000>,TrWipeIn<1060>>>>(),
Feel free to try it to get you going. It is from ESB.
I also have one from ANH (also from OS5.9):
StylePtr<Layers<
AudioFlicker<RgbArg<BASE_COLOR_ARG,Red>,Rgb<128,0,0>>,
LockupTrL<Layers<
AlphaL<AudioFlickerL<RgbArg<LOCKUP_COLOR_ARG,Rgb<255,240,80>>>,Bump<Scale<BladeAngle<>,Scale<BladeAngle<0,16000>,Int<4000>,Int<26000>>,Int<6000>>,Scale<SwingSpeed<100>,Int<14000>,Int<18000>>>>,
AlphaL<LemonChiffon,Bump<Scale<BladeAngle<>,Scale<BladeAngle<0,16000>,Int<4000>,Int<26000>>,Int<6000>>,Int<10000>>>>,TrConcat<TrInstant,TransitionEffect<Rgb<255,180,50>,LemonChiffon,TrInstant,TrFade<200>,EFFECT_LOCKUP_BEGIN>,TrFade<400>>,TrConcat<TrInstant,TransitionEffect<LemonChiffon,Rgb<255,180,50>,TrInstant,TrFade<200>,EFFECT_LOCKUP_BEGIN>,TrFade<400>>,SaberBase::LOCKUP_NORMAL>,
ResponsiveLightningBlockL<Strobe<RgbArg<LB_COLOR_ARG,White>,AudioFlicker<White,Blue>,50,1>,TrConcat<TrInstant,AlphaL<White,Bump<Int<12000>,Int<18000>>>,TrFade<200>>,TrConcat<TrInstant,HumpFlickerL<AlphaL<White,Int<16000>>,30>,TrSmoothFade<600>>>,
ResponsiveStabL<RgbArg<STAB_COLOR_ARG,Orange>>,
ResponsiveBlastL<TransitionEffect<RgbArg<BLAST_COLOR_ARG,Rgb<255,240,80>>,LemonChiffon,TrInstant,TrFade<50>,EFFECT_BLAST>,Int<400>,Scale<SwingSpeed<200>,Int<100>,Int<400>>>,
ResponsiveClashL<TransitionEffect<RgbArg<CLASH_COLOR_ARG,Rgb<255,240,80>>,LemonChiffon,TrInstant,TrFade<100>,EFFECT_CLASH>,TrInstant,TrFade<400>,Scale<BladeAngle<0,16000>,Int<4000>,Int<26000>>,Int<6000>,Int<20000>>,
LockupTrL<AlphaL<BrownNoiseFlickerL<RgbArg<DRAG_COLOR_ARG,White>,Int<300>>,SmoothStep<Int<30000>,Int<5000>>>,TrWipeIn<400>,TrFade<300>,SaberBase::LOCKUP_DRAG>,
LockupTrL<AlphaL<Mix<TwistAngle<>,Rgb<255,200,0>,DarkOrange>,SmoothStep<Int<28000>,Int<5000>>>,TrWipeIn<600>,TrFade<300>,SaberBase::LOCKUP_MELT>,
InOutTrL<TrWipeSparkTip<White,1000>,TrWipeIn<1060>>>>(),