It is not, at least not yet.
I’m seeing things like CLASH_THRESHOLD_GAMMA, and wonder if DYNAMIC_CLASH_THRESHOLD, DYNAMIC_BLADE_DIMMING and DYNAMIC_BLADE_LENGTH are still necessary, are now on by default or are deprecated. Ditto for SAVE_BLADE_DIMMING and SAVE_CLASH_THRESHOLD. I’m currently waiting some hardware so I can test the OS on testing station. But can update the documentation if this things have changed. In fact, I could try to go through the defines and add a DEPRECATED (ProffieOS 8+) to this or other defines like ENABLE_MOTION.
They are still there, they are not on by default, but they are included in ENABLE_ALL_EDIT_OPTIONS, which is probably the recommended way to enable these.
CLASH_THRESHOLD_GAMMA has no effect DYNAMIC_CLASH_THRESHOLD is not defined.
The documentation for ENABLE_MOTION and friends has already been updated, but feel free to make improvements. 
1 Like
ProffieOS 8.x status update:
I’ve been meaning to create a ProffieOS 8.1 zip file for a few days, but a bunch of people have been scrambling to add things to ProffieOS 8.x, so there there have been new things to review every day this week, which is both exciting and slightly terrifying since it possibly means lots of new bugs.
We’ve got a few more tests done, but there is still a lot to do.
At the current speed, release would be a year from now. (Which is much better than the previous estimate.)
2 Likes
Hey, I found some time to make an 8.1 zip, which is mostly the same as 8.0, but there is also some new stuff, which have added to the top post:
- fix for sound queue to make it select files at play time instead of at queue time
- tab cleanup in a few files
- bugfix for ENABLE_IDLE_SOUND
- Moved blaster display controllers into prop file.
- Array switching for BC and Sabersense props. (but they work differently, choose wisely)
- MENU_SPEC_TEMPLATE and MOUNT_SD_SETTING support for Fett263 prop
- bladein/bladout support for OLED and color displays.
5 Likes
I don’t know if it is a bug or not… but after much testing with my tester, testing station and such, I’ve discovered that if you set #define NUM_BUTTONS 2 and forget to define your second button, you get no error. I spent two days trying to find the fault on the switch, the cables, the board, and it was some typo when copy and pasting from other config.
Discovered this on 7.15, tested that it did the same on 8.1. So it must have been there for a while. I do remember in 6.x o 5.x times some error when I did this.
It’s always been like this.
NUM_BUTTONS are the number of buttons you actually have are only vaguely connected, and ProffieOS currently does not have a way to actually count the number of buttons you have defined. (If it did, there would be no need for a NUM_BUTTONS define.)
1 Like