You’re more than welcome to try to dissect the menu as you want. I have no plans to do so.
The structure has many submenus and features that are inter-related, it would take quite a bit of work to make parts optional and still have it operate as intended.
What command would be helpful right now to diagnose this odd behavior suddenly?
I have my 3rd blade style showing up on my main blade WHILE my main blade is still correct. It’s layered on top of it. And there’s no subBlade wiring in the saber.
I thought I’d try to get some info from its current state before trying a reset and/or power cycle
My guess is that this is somehow caused by the WS2811 optimizations I did a couple of days ago:
So the first step would be to check out the code as it was right before that change and see if that solves the problem. Assuming that is the problem, the next step would be for me to reproduce the problem using your config and see if I can figure out what causes it and how to fix it.
Reverted all of the blades files. ws2811_blade first, then then the next 2 in order of error message repair:
spiled_pin
stm32l4_ws2811
At that point the style for blade 3 was no longer layered on the main (blade 1), but not lighting on actual blade 3 either.
reverted monopodws as well with no change.
I would assume the LEDs are working as they were before but I am going to test them in the meanwhile.
This is the config I’m using
** I used GitHub to go to the files’ history, picked the previous commit, then view at that point in history. Copied all, replaced locally.
- DYNAMIC_BLADE_DIMMING
- DYNAMIC_BLADE_LENGTH
- DYNAMIC_CLASH_THRESHOLD
- SAVE_BLADE_DIMMING
- SAVE_CLASH_THRESHOLD
- FEMALE_TALKIE_VOICE
- DISABLE_BASIC_PARSER_STYLES
- ENABLE_ALL_EDIT_OPTIONS
I’m going to do a video for this test but I believe I tested the FEMALE_TALKIE_VOICE and it worked.
For what it’s worth, I have also confirmed this works well.
hey peeps, i went to the github and tried to find the wiki for some of these but to me it looks like the documentation for version 5.9, is there a specific place in the wiki that is the write up for OS 6?
It’s not been done yet, but in general we’ve just made a header for newer defines and then document the new defines below that header.
If you want to speed up the process, you can always just do the edits yourself.
You know you can just go to to a commit, click “browse code” and then go to “download zip” and you get a zip of the code as it was at that commit, right?
Unfortunately, that config file doesn’t work for me since includes a lot of things that I don’t have.
Is it the NOBLADE case that doesn’t work, or is it when the blade is inserted?
Does it happen with all presets? (I removed all presets except one because they had references to things that I don’t have.)
Sorry.
Slimmed down config using default prop, current master branch.
With this setup, it persists. I also just had a squee-of-death on retraction.
3.7 board.
I have the blade inserted.
It does happen with all presets. (before when there were multiple)
When removed, Blade Detect is not working.
I’m going to investigate hardware further. I just loaded a July archive and no blade detect still, no blade 3 lights.
Trying out OS6 Beta. Not sure if anyone else has ran into this yet. My preons are starting out about 3/4 out of the emitter. Max led strips still set to 144. I also have the shtok v3 installed. All working fine. Set my blade at the bottom to 55 which is my test blade pixel amount. Does it on all presets. Could also be happening with the V3 as well but not sure yet. Otherwise so far so good with menus and tracks…etc. Thanks in advance for any help.
2 Comments
Like
Comment
It’s still Alpha, if you’re using the Edit Mode test styles use Style Settings for Preon Size to adjust. If not then you have to change size in config.
If that doesn’t fix, it could be related to issue Brian noted above, in which case report back for Proffezorn to look into.
Do you have an RGBA blade?
Standard 5050s. 55 pixel count.
Do you have a previous configuration that did work?
Yes. but os 5.9. Before I loaded the beta os 6 all was ok. In some of the styles I was using Flare/emitter and it looks like it’s split in half…half in the emitter and half out riding the blade. when retraction takes places it leaves a black hole between that space. Sometimes on ignition as well. Some preons start out a few inches from the emitter. Just posting what i see. I know it’s still beta…try to test as well. But the rest is working great so far. I did update and install most recent. Even the 3.6 file for proffieboard.
It’s not beta, it’s alpha, which means even more problems.
However, I’d like to see the config file that worked, as that may help me work out what the problem actually is.