will keep this in mind from now on, sorry about that. Side note- now that everything works, I wanted to thank you all who have worked on OS6 as it is a really big step forward and Iâve really been enjoying it. Thanks again!
1 Like
No worries. I just want to make sure that people know how to write up their questions well, because it means that they get better help faster. 
4 Likes
@profezzorn Just for troubleshooting, in my prop if the user gets âError in Font Directoryâ prompt when they are trying to go into Edit Mode it means the voice prompts were not found. I used this error message to signify that you cannot enter Edit Mode.
The fix is to include the âcommonâ folder and voice prompts to the SD -AND- update the presets to include â;commonâ in the font search path.
2 Likes
I see, that makes sense.
1 Like
RE blade length edit: is it worth adding some logic for whether blades are pixel or standard LED? I have a hilt with the main blade as pixel, and one plain accent LED but the edit mode treats that as pixels still. It could remove any non-pixel blades from the option menu to make it more efficient?
I could whip up a hex version of âedit mode not availableâ⌠âcommon folder missingâ or whatever the general consensus that the message should say? @profezzorn ?
Or maybe use existing things and just have it trigger âfont directory not foundâ instead?
Not worth the extra memory in my opinion, itâs technically an error in the font directory that is causing the feature not to work.
1 Like
We could just add the hex for âcommonâ.
Then we could string it together like: âcommonâ+âfont directoryâ+ânot foundâ.
Just knowing that âerror in font directoryâ can mean two things is probably enough though.
1 Like
if itâs enough thatâs good. Getting the âCâ to be clear is not working well.
1 Like
Ok, so now that the new OS has been released, the question has arisen as to how all of the âhow-to use itâ documentation/examples are going to manifest.
Is it all on Fett263âs plate?
Can we help?
Should we have like a distribution of chunks of different things for volunteers to focus on so that cumulatively it all gets disseminated?
Many new blade style transitions and effect options are still not clearly explained anywhere, so figuring anything out unguided is pretty rough for most.
Features that are not specifically Edit Mode centric for example, like the list of transitions and functions in the top post.
And Fett263 likely has his hands overflowing with to-do lists, making a Library of styles for people to just download and copy/paste etc⌠which is amazing of course, but not instructional per se. There are those who can make custom styles from scratch who could benefit from the new available features as well, and then take some hints and parts from Library styles and expand/customize from there.
So yeahâŚhow can we help out?
2 Likes
Nearly everything will be represented in the library but thereâs obviously even more possible uses for stuff. Read the top portion of the transitions, etc and then trial and error is the best teacher for those who want to get a headstart building from scratch. Then if you want to improve the usage explanations just suggest.
1 Like
Hey @Fett263
I have proffieOS 6.3 on my saber but I get the dreaded âError in font directoryâ message.
My âcommonâ folder is in the root of the SDcard. What am I screwing up?
but is it in your font search path in the preset?
{ "Font;common", .........
1 Like
When are you getting âError in font directoryâ? Why is it âdreadedâ? It just means you need to fix something, itâs not like the board set on fire 
1 Like
Indeed, @NoSloppy that was the issue⌠Think of me as your documentation beta tester
I bought a Korbanth saber and now I want to update to ProffieOS 6 in order to get all the goodies⌠these are the questions that will be coming.
1 Like
I ran into a glitch when retracting my saber in OS6.3 via a twist off, I got an immediate ignition before it retracted fully several times. I am running a Proffie V2.2 here. Below is serial monitor readout:
unit = 0 vol = 0.00, Playing anhtrain/hum/hum01.wav
channels: 1 rate: 44100 bits: 16
unit = 1 vol = 0.50, Playing anhtrain/out/out03.wav
channels: 1 rate: 44100 bits: 16
humstart: 1800
unit = 2 vol = 0.00, Playing anhtrain/swingl/swingl02.wav
channels: 1 rate: 44100 bits: 16
unit = 3 vol = 0.00, Playing anhtrain/swingh/swingh02.wav
channels: 1 rate: 44100 bits: 16
Playing anhtrain/swingl/swingl02.wav
channels: 1 rate: 44100 bits: 16
Playing anhtrain/swingh/swingh02.wav
channels: 1 rate: 44100 bits: 16
unit = 3 vol = 0.00, Playing anhtrain/swingl/swingl02.wav
channels: 1 rate: 44100 bits: 16
unit = 2 vol = 0.00, Playing anhtrain/swingh/swingh02.wav
channels: 1 rate: 44100 bits: 16
TWIST
EVENT: Twist ON millis=26974
unit = 1 vol = 0.50, Playing anhtrain/in/in01.wav
channels: 1 rate: 44100 bits: 16
EVENT: Clash millis=27525
EVENT: Thrust millis=27962
Ignition.
unit = 0 vol = 0.00, Playing anhtrain/hum/hum01.wav
channels: 1 rate: 44100 bits: 16
unit = 4 vol = 0.50, Playing anhtrain/out/out01.wav
channels: 1 rate: 44100 bits: 16
humstart: 1800
unit = 2 vol = 0.00, Playing anhtrain/swingl/swingl02.wav
channels: 1 rate: 44100 bits: 16
unit = 3 vol = 0.00, Playing anhtrain/swingh/swingh02.wav
channels: 1 rate: 44100 bits: 16
No sounds found: pstoff
Playing anhtrain/swingl/swingl02.wav
channels: 1 rate: 44100 bits: 16
Playing anhtrain/swingh/swingh02.wav
channels: 1 rate: 44100 bits: 16
Battery voltage: 4.00
Playing anhtrain/hum/hum01.wav
channels: 1 rate: 44100 bits: 16
EVENT: Power-Pressed#1 ON millis=43789
EVENT: Power-Pressed ON millis=43789
EVENT: Power-Held#1 ON millis=44102
EVENT: Power-Held ON millis=44103
EVENT: Power-HeldMedium#1 ON millis=44609
EVENT: Power-HeldMedium ON millis=44609
EVENT: Power-HeldLong#1 ON millis=45790
EVENT: Power-HeldLong ON millis=45790
unit = 1 vol = 0.50, Playing anhtrain/in/in01.wav
channels: 1 rate: 44100 bits: 16
EVENT: Clash millis=46337
EVENT: Power-Released#1 millis=46552
EVENT: Power-Released millis=46552
EVENT: Thrust millis=46993
Ignition.
unit = 0 vol = 0.00, Playing anhtrain/hum/hum01.wav
channels: 1 rate: 44100 bits: 16
unit = 4 vol = 0.50, Playing anhtrain/out/out01.wav
channels: 1 rate: 44100 bits: 16
humstart: 1800
unit = 3 vol = 0.00, Playing anhtrain/swingl/swingl02.wav
channels: 1 rate: 44100 bits: 16
unit = 2 vol = 0.00, Playing anhtrain/swingh/swingh02.wav
channels: 1 rate: 44100 bits: 16
No sounds found: pstoff
EVENT: Power-Pressed#1 ON millis=50814
EVENT: Power-Pressed ON millis=50814
EVENT: Power-Held#1 ON millis=51128
EVENT: Power-Held ON millis=51128
EVENT: Power-HeldMedium#1 ON millis=51636
EVENT: Power-HeldMedium ON millis=51636
Playing anhtrain/swingl/swingl02.wav
channels: 1 rate: 44100 bits: 16
Playing anhtrain/swingh/swingh02.wav
channels: 1 rate: 44100 bits: 16
EVENT: Power-HeldLong#1 ON millis=52815
EVENT: Power-HeldLong ON millis=52815
unit = 1 vol = 0.50, Playing anhtrain/in/in01.wav
channels: 1 rate: 44100 bits: 16
EVENT: Power-Released#1 millis=53235
EVENT: Power-Released millis=53235
EVENT: Clash millis=53358
EVENT: Stab millis=54138
No sounds found: pstoff
Amplifier off.
Unmounting SD Card.
Battery voltage: 4.03
Battery voltage: 4.03
Battery voltage: 4.03
Battery voltage: 4.03
Battery voltage: 4.03
Battery voltage: 4.03
Battery voltage: 4.03
Battery voltage: 4.03
Battery voltage: 4.03
Itâs reading a clash and thrust when you retract.
Do you get different results when muted? :hint:
Iâll try it muted when I get done with work. I saw that too, but why would you get a speaker induced thrust? I didnât think that was possible.
Depends on proximity of board to speaker, a big enough linear vibration could possibly be detected as a thrust or it could be a movement youâre doing after the twist? In some of your videos Iâve noticed you sometimes pull the saber towards you as youâre twisting, itâs possible thatâs causing, although the clash/stab detection seem like it could be speaker vibration.
I think it was the clash threshhold. I increased from 2.4 to 2.65, and that seems to have resolved the issue for now. This saber has a unique home made chassis, I had to use a piece of 7/8 blade stock. The chassis I ordered with the hilt didnât work at all, and there was time pressure to finish the saber. Its for a kid with cancer. Its done, and it was also the saber I updated to OS 6 on my latest video. It worked out great. Thanks for the help. I can now tick in serial monitor feedback. I donât think that quite ranks me as a coder yet thoughâŚ