Weird bug in certain fonts on ignition, specifially Rogue Commander font, fusing fett263 button

ProffieOS Fett263 Corner
1

Ok, first my specs:
Proffie 2.2, running 7.14, then 7.15
Fett263 two button setup
SD card sandisk Ultra 16GB HC I
several selectable fonts, including the default free proffie, mouthsaber and Kyberphonic ANH_Graflex.

Problem: after sitting for a bit, I remove kill key, and with RgueCmdr (Rogue Commander) font selected, when I ignite blade, I hear ignite sound but no neopixels light, but once ignite sound has stopped, blade snaps on instantly. possible crackle in amp sounds mixed in. retract blade works as intended. When I ignite again, usually similar behavior. But after a few ignite cycles it behaves as one would expect, blade ignites up in cascade as intended.

This does not happen with Kyberphonic ANH_Graflex font. It may happen with a few of the other free fonts that come with proffie, but to narrow down, I have concentrated on Rogue Commander Vs ANH_Graflex.

It’s not a problem with blade style, as when I reassign the blade style I use for ANH_Graflex to use Rogue Commander font, problem follows the font. So problem follows the font, not the blade style.

As you may know, Rogue Commander font is simple, without folder structure, or additional features of more recent fonts. Perhaps that is the problem? So I reorganized Rogue Commander into sounds organized by sound type, mirroring ANH_Graflex. No change. I added features/sounds not present in stock Rogue C. Still no change. I noticed that Rogue C did not have config.ini file. Perhaps that is the problem. I clone config.ini from ANH_Graflex. Still no change. But problem is something to do with the font, or the font and fett263 setup possibly?

I start swapping out actual sound files in Rogue C with ANH_Graflex. Starting with “hum” and “swingl” and “swingh.” swapping hum does not seem to help, but changing the swingl and swingh to ANH_Graflex makes problem go away. Rogue C has 8 pairs of these sounds. ANH_Graflex has only two. maybe that is the problem. I make a folder in swingh and swingl of Rogue and put swingl and swingh 3-8 in there, so onlys swingl01.wav & swingl02 .wav and corrisponding swingh files are in their root directory folders. Still no change. I confirm they are mono, 44.1 files. I cloned smoothswing.ini from ANH_Graflex also, no change.

Also, side note, when I switch between them, when testing the ANH_Graflex vs Rogue Commander swing files, I keep both pairs of folders in directory, just rename the one I am not testing. So, when testing Rogue Commander, the folders for Rogue Commander are swingl and swingh, and the folders for ANH_Graflex are NEWswingl, NEWswingh. when testing ANH_Graflex, I rename the NEWswingh and NEWswingl to swingh and swingl and the Rogue Commander wav files are OLDswingh and OLDswingl.

One thing I have not tested, is I do not have a folder with just “swing” sounds, as I see in newer fonts. Perhaps that is screwing things up somehow? Yet even further testing is required I guess, although I have no Rogue Commander sounds to put in there, I would have to clone sounds from another font to tell, as Rogue Commander only has swingl and swingh wav files.

So: currently, when I run Rogue Commander with the hum for ANH_Graflex in place of Rogue Commander, but at least two of Rogue Commander swingl and swingh sounds, I have the blade skip ignite sequence during ignite sound, then snap on, but after a few cycles, problem goes away. When I swap out Rogue Commander swingl and swingh wav files with ANH_Graflex, problem goes away, and blade ignites normally. in both cases, using blade style I made for ANH_Graflex.

So far only two further things I can test, is making “swing” folder and stealing another font sound to put in there, or opening the problem swingl and swingh files in Audacity and then re-saving them in hopes that some rogue (no pun intended) metadata that is somehow screwing things up gets scrubbed.

Anyway, thank you for reading this far in my troubleshooting odyssey. Any suggestions as to what to pursue further would be helpful.

2

Could still be the SD card. Not all formatters are great (Mac’s Disk Utility for example).

The visual ignitions could have their timing set to the length of the .wav files, which gives the wonkiness you’ve described.

Have you tried formatting the SD card with this? (with all of your fonts backed up to your hard drive)

1 Like
3

Update: made a “swng” folder and put two swng.wav files from ANH_Graflex in it, still no change.

4

I have not. will do that now, and report back.

5

I would run ‘sdtest’ on the font in question, slow or laggy SD performance can cause all kinds of issues.

6

I copied all the files off, reformatted the card with the SD Association formatter, redeposited all the files on it, and it may have fixed my problem! It is not exhibiting the problem anymore, but to be sure, I am going to leave it with kill key in for half an hour-40 min and try again. (somehow, time with kill key changes behavior.) If it continues to be resolved, then it appears to be formatting. If it starts to happen again, but manifests in a different font instead, I will likely replace the SD card.

Thanks again for the very fast, and apparently on the nose suggestions!

7

One note, just in case, when making changes to your fonts; renaming, moving, deleting, copying over files, etc. I recommend doing everything on your computer, then reformat your card, then copy the changes over to SD. Making a lot of edits on the SD itself can eventually corrupt files or cause issues.

Also, be sure you’re always Ejecting the SD anytime it’s connected to the computer, as failing to properly Eject can also corrupt files over time.

1 Like
8

Well, that certainly was likely how this problem manifested in the first place. It was my first Proffie build, so there was a lot of back and forth on the card as I build out all the profiles. But now I know better. It was such a weirdly specific thing I was baffled as to what was going on. Now I know, clean sd card install is like rebooting your computer, fixes all the weird stuff that shouldn’t be happening.

1 Like