that was it haha. ty. should have checked the font first…there were a ton of weird named wav files in each folder. ty for the push in the right direction.
This sounds exactly how my lockups are represented from a clash that happens but the blade continues to move. Ill check this out once im done with my run. Im confident this will fix it. Thanks for your work.
havent had a chance to test stilll been busy i will confirm as soon as i can
I’m having an issue uploading new presets. After i write the preset in config and upload, i test it… and it’s not there. All audio is present. I removed all saved state, global, and preset items written to sd card, and only then seemed to accept the new preset in the config. It was written to the board but not seen by something. Maybe i missed a step?
- Please read the rules about screenshots. I don’t like screenshots and your screenshots serves no purpose whatsoever.
- do you have
KEEP_SAVEFILES_WHEN_PROGRAMMINGin the CONFIG_TOP section of your config file? If so, this would be expected behavior.
Is KEEP_SAVE_FILES_WHEN_PROGRAMMING an update to the SAVE_STATE define to allow edits in the saber or via webUSB to carry over when reprogramming? I noticed the SAVE_STATE define is not recommended in FETT263’s primer (love the new website!) and am trying to get a basic understanding of how it may have evolved.
If I don’t mind my changes being wiped when I reprogram, should I still use SAVE_STATE to keep my changes until reprogramming?
SAVE_STATE saves the preset that was active when you power off saber, I prefer my saber always starting on first preset when it boots so I never use.
KEEP_SAVEFILES_WHEN_PROGRAMMING saves all edits even when you re-upload, there’s more info here:
1 Like
Thank you.
Any chance to test?
I gave it a test since my Jedi Killer was having that same issue. Originally had my clash sensitivity at about 15, I was able to drop it down to 8 which was a big improvement. I lowered my volume maybe two clicks from the original 2000 as well and that seems to have fixed it for me. I think my fonts are just a little too bassy.
Yessir i tested it last night around 1pm ET and another this morning. I just got home but i can say that i have had no reoccurances of lockup occuring outside of battle mode. I think i may have triggered a clash one time but my volume is at 2500 and my clash is at 12 so i guess os6.5 is just more sensitive. If i somehow get some random lockup i will let you know but im confident that we are good now.
Update on an older reply I had. This week I got things working clean w the modded prop-file. Custom menu sound options, etc all work as needed. Speed and performance is where it would’ve/should’ve been had I not missed a simple thing I didn’t think of cross-checking.
EditMode on the other saber is also still good. Having way too much fun going snow-blind making new bladestyles happen.
Okay here with another inquiry. This issue is inconsistent and has occured in two sabers running 6.5. Sometimes maybe 10 percent od the time my sound will cut out (blade will still be working fine) when swinging and i will just turn the saber off and back on again. Nothing from serial monitor. i checked the battery connection amd speaker connections…i dont see anything. Im running the same config that i ran when i posted about my last issue a few weeks ago. I have VERY clean soldering but its also happened in a Bendu build as well. its almost like its muting itself while on sometimes. maybe something sneaky in the prop file? sorry and thanks for amy help.
sorry running FETT263 prop
If it is muting itself, you can use get_volume in the serial monitor to check what the current volume is. If it is muted, the volume will be zero.
im sorry im confused should i use serial monitor and try and replicate the problem again…ive been unable to replicate this in SM. volume comes back when i turn it off and on again…
I don’t see anything in the prop that would cause this unless your power button is somehow sticking or has a short. How long after ignition does this occur? Is it possible the button legs are making contact with the inside of the hilt and shorting against it with movement? The “inconsistent” part makes me think it’s something outside the software.
This sometimes wont happen until like 8 minutes of use…this happens now in all three sabers of mine running 6.5 and FETT prop…the one from bendu armory and the two i installed myself…i also shrink wrap the buttons always…i dont see how they would touch any metal…theyre short buttons and very secure…
Then I don’t think it’s related SetMute(true), so it doesn’t seem like it’s actually prop to me (could be wrong) but nothing else in the prop affects volume especially not after the saber has been on for more than a few seconds. When it occurs if you do a Blast or Clash do those sounds and/or effects still work? Trying to figure if maybe it’s tied to motion detection, I have not encountered on any of my sabers in any testing. There’s a few other threads with odd motion behavior maybe everything is somehow related and/or specific to fonts or SD cards or maybe specific components on certain boards, I don’t see anything in the prop and I haven’t ever replicated on any of my sabers, so it still seems like there’s an outside variable to the OS itself involved. I’ll defer to profezzorn, he’s been looking into the motion detection issues reported maybe this ties into that?
Well all the boards are for shre brand new, and i have had the issue occur on whatever font i was using at tge time…sometimes is wont even happen for 15 minutes…when it occurs, all motion related sound including blast, lighting will be “muted”…the blade LEDs will function as normal. I will switch one saber back to 5.9 and see if i can replicate but ove never encountered in 5.9 and ill switch a different saber to a differemt prop to see if the problem occurs their. Ive noticed the issue occur when im in auto blaster block mode…it usually occurs as soon as i go to swing so not usually if its idle.