Use pastebin.com and paste the actual config you uploaded so we’re sure there’s no variances.
Since you’re using my prop, what are the reasons? OS7 with my prop can function the same as OS6 but also incorporates multiple fixes for things making OS7 much better on multiple fronts. My prop in OS7 is also much more customizable allowing for even more personalization. If you explain your reasons I can probably get you set up much better in OS7 
.
I have never heard of or used Pastebin before, so not sure if how i did this will work. If I did wrong, please let me know.
With regards to why I used 6 versus 7…it just feels like it’s way over my head, and way more than I am looking to do. Kinda like buying a Indycar racer when I just need a golf cart to get around the 18 holes. 6 probably is, too, but since that is what is on my last 2 sabers and what I’m familiar with, that is what I opted to stay with. From what I understand, it looks like you can change styles and switch out fonts “on the fly” and without needing to hook up to the PC to do that. Looks very powerful and interesting, but I like to keep it simple. I’m just interested in the movie saber styles, colors, and fonts, and am not interested in changing colors, having styles from all the cartoons/video games, etc. I just like to set them up, and then enjoy my saber as I set it up, and the Easy ProffieOS/Proffie Workbench has been perfect for what I am looking to do. I know it’s limited and going to your site is so much more powerful and offers WAY more options, but I just don’t have that time and, honestly, I’m very happy with setting up individual styles through the Workbench. I get that I’m in the minority, but at the end of the day, I still love my saber and the modifications I was able to add, no matter ow limited they were in the grand scheme of things.
What I’m saying is 7 can be the same as 6 but fixes a few bugs and improves things overall.
Editing on ProffieOS Workbench is fundamentally the same (technically it’s controlled by the styles so if you use those styles that wouldn’t change either, although those are OS5 styles so there’s minimal editing possible. If you use OS6 or 7 styles you could do more editing in Workbench.
Your set up is incorrect for OS6 either way. My prop in OS6 and 7 requires the Voice Packs in the ‘common’ folder, see Set Up Instructions here.
As to the styles you prefer, you can go as simple or complex as you want in OS7, the styles control what is showing. My library does super simple all the way to super complex but includes editing features for Workbench automatically to allow you get even more out of the editing tool, just sayin…
You are missing some important defines, especially for editing and memory optimization in OS6 and 7. I suggest seeing here for Edit Mode, even if you don’t use the Menu, the defines recommended here for editing will help on Workbench as wel.
#define ENABLE_ALL_EDIT_OPTIONS
#define DISABLE_BASIC_PARSER_STYLES
#define DISABLE_DIAGNOSTIC_COMMANDS
If you have specific things you didn’t like when you tried OS7 I can direct you, but nothing here says you’ll see any difference between OS6 and OS7 except for a few bug fixes. Plus, my prop in OS7 can further disable things to really simplify it, whereas OS6 had some features that couldn’t be disabled.
As to the gestures everything appears in order, assuming you successfully uploaded this config they should work, although OS7 fixed a small bug in Force Push. Refer to the Gesture diagram on my prop page to make sure you’re doing the gestures correctly.
Thank you very much for the detailed response and the links!!. I had to step out the rest of the day so i was unable to go through this in detail, but I did catch what you indicated about the extra defines that are missing that will help in Workbench. After reviewing what you said, and after I look through in further detail what you added, I’m leaning to uploading OS 7. Will report back after I do so and report on what happened. Thanks Again!!!
#define ENABLE_ALL_EDIT_OPTIONS
#define DISABLE_BASIC_PARSER_STYLES
#define DISABLE_DIAGNOSTIC_COMMANDS
Getting ready to add OS7 to my saber. You mention adding these to the config. I didn’t see on the link where these defines ( and the #define DISABLE_DIAGNOSTIC_COMMANDS define) go in the config, specifically. Do they go in the same area where the other gesture commands are, and above the #endif line in that section?
All defines go together in the CONFIG_TOP section of your config.
Just FYI, my config helper tool can make this much easier. It handles the formatting for you. Just watch the videos and read the selections.
Following up on this topic…After making some changes to the length of the blade and to the gesture controls, i uploaded the “tweaked” config file onto the board with Arduino. After that, I made numerous changes using the ProffieOS Workbench. I’m assuming those style changes are saved somewhere…do they save to the config on the board? I would like to grab some of the FETT263 pre-made styles and add them to the config and upload that onto my board - will that mesh with the changes and additions i made through the Workbench? Or, are the two methods of programming incompatible with each other?
Edits made in Workbench or Edit Mode will be overwritten if you upload a new config unless you use the define to KEEP_SAVEFILES_WHEN_PROGRAMMING, but there are a lot of caveats when using that define as it overrides expected behavior and often confuses users, before using that define I recommend reading and fully understanding what it means and what it does.
See here:
As an alternative, for style and color edits you can open your presets.ini file and use the Style Arguments that were generated in my config tool. Watch the videos at the top.