I haven’t been able to test OS6 yet. I was waiting for the beta and now have had a busy time in the evenings recently. @MegtoothSith does the gesture spam rollback mean less chance of the hum issue in your experience?
1 Like
I havent experienced any hum glitch yet. Not in any font. Either on 1.5 or 3.7.
1 Like
Removing the “spam” delay didn’t seem tied to the hum, although I still have never been able to replicate this hum issue on any saber so if it was tied to gestures then the removal of the “spam” delays should make it more prevalent not less.
In OS5 testing we had odd behavior (including the saber not knowing it if was on or off) when users were just spamming gestures on/off/on/off/on etc so I added 2 second delays between gesture ignitions/retractions to prevent. But with all the updates in OS6 and some testing they didn’t seem necessary any longer so they’ve been removed. If anyone does run into an issue when “spamming” the gestures please provide as much info as possible so we can track down.
They were merged last night so you can go back to the master github version to continue testing, my fork was just a quick “proof of concept” before I submitted since I didn’t have time to fully test myself.
1 Like
You should be able to replicate on 5.9 by igniting and retracting in quick succession. Gestures can compound that.
ok, that worked, kinda? I pull the kill key, blaster makes it all the way through the boot sound. OLED now displays a bullet count (0003), center of the screen and I can see the recticle animation behind it. However, now when I pull the trigger, the blaster reboots itself, as if I just pulled the kill key again. Prop file says “Blaster is always on with power, unless dedicated Power button is installed.” I don’t current have a power button, unless we’re counting the pulling of the kill key as a power button?
Sounds like it’s still crashing somehow. I will investigate.
Stand by, I may have a short causing the reboot. I am able to use the serial monitor, typing “on” gets me past the boot and I can pull the trigger and mode buttons successfully if I hold the board up in the air… yeah definitely a short. However, I was able to confirm that the bullet counter doesn’t move, it just stays at 0003.
Try changing it to:
#ifdef CONFIG_BOTTOM
DisplayHelper<64, uint32_t,
BaseLayerOp<StandardDisplayController>,
ClearRectangleOp<10, 50, 8, 24>,
WriteBulletCountOp<10, 20, 3>
> display_controller;
SSD1306Template<64, uint32_t> display(&display_controller);
#endif
(3 digits instead of 5)
2 questions.
-
This display controller stuff in CONFIG_BOTTOM is only for larger screens, yes?
Standard 128x32 still works fine without this section -
unrelated - does
#define DYNAMIC_BLADE_DIMMINGdefault to 1/2 brightness?
I see in my global.ini it’s at 16384 and I haven’t adjusted anything at all.
Actually, the OLED in my scope is 64x32.
Correct. You also need it if you want bullet counts, or some other kind of dynamic content on your display.
It defaults to 16384, but 16384 = 100% in this case.
Will WavLen<> listen to a lockup wav? Having a hard time with that.
1 Like
lockup isn’t an effect, it’s a state, and the wav file is looped. I think it should work with EFFECT_LOCKUP_BEGIN and bgnlock.wav, but not with lock/lockup.
Ok, bullet count works! It takes up the entire screen, but it works. Two questions then. 1. Is there a way to shrink it into a corner of the screen, allowing the recticle animation to be seen? 2. My build uses a h.u.d. kind of idea, which needs the display to be flipped like a mirror. How would one accomplish this?
Also, how does one turn “on” the blaster in the first place? I’ve been using the serial monitor to actually activate it and unplugging the cable, or kill key to turn it off. Typing “off” just disables the primary and secondary buttons. The OLED remains on. Plugging in the USB cable or kill key merely boots the blaster.
blaster is not functional until I type “on” via the serial monitor.
Making it smaller requires using a smaller font, which means using the fontconvert utility to convert a TTF font to data which can be used by ProffieOS first. Ufortunately I have not created a way to actually select a font for the WriteBulletCountOp yet. Currently it only lets you select position and number of digits.
There is currently no support for mirroring in the ProffieOS config file, but it’s not that difficult to do. It should be a matter of just fiddling with these lines of code a bit:
Like maybe change line 841 to COMSCANINC ?
The blaster prop changes it behavior based whether “poweron” is available in your font. If you font has a “poweron” file, then it won’t turn on automatically. Instead it assumes that you have some way to do that. (Like, a power button.) If you don’t have a power button, then you probably want to make sure to delete the “poweron” sound(s) from your blaster fonts. Or, you could make changes to the prop file itself.
While we’re on OLED… what causes the images to sometimes invert but sometimes not?
Cool, I’ll muck around a bit and see if I can get that to orient the way I want. Consider the bullet count tested and working?
I’ll remove that poweron effect as well!
Absolutely amazing, thanks so much for adding the on-the-fly copy preset! I think that really ties everything together.
I really want to try and buckle down and test a bunch on a bunch of different sabers, 1 and 2 button, so let me know if there’s anything specific that still needs testing! I’ve tested some from the most recent build, including ignition/retraction spamming from the other one you posted, here’s what I’ve found:
Preset scroll increment: Working! Seems a bit finicky though, sometimes while holding power it reverts back to scrolling one at a time. Might just be a crappy button though.
Track player: Working! Using a fonts folder in common, and my presets.ini file set up to assign tracks from that folder to fonts, it plays the correct track while up or on, and the first track when parallel/down
copy preset: Working! However when trying to change the font it says “save” and I think it created a gesture file on my sd card. Maybe I just need to figure out the controls. I haven’t been able to trigger a change preset with the blade on.
ignition/retraction spamming: Working! Using all gestures, buttons, gesture sleep, and multi-phase seems to work perfectly, tested with and without preons
#define FETT263_SAY_BATTERY_PERCENT
#define FETT263_BM_CLASH_DETECT 8
#define NO_REPEAT_RANDOM
#define COLORWHEEL_ZOOM
all seem to be working, I’m gonna try no repeat random with numbered wavs though just to be sure. battery percent and the clash detect during battle mode work perfectly! Colorwheel zoom also works with color change direct and RotateColorsX
I’m going to try and do more testing and really beat the hell out of it but let me know if there’s anything specific I can test, but other than the things I’ve mentioned everything is working great for me!
I will say though for ignition spamming, we can’t really do that Kylo kill with the button, as pressing it that fast ignites the saber muted. Not really sure if anything can or should be done about it (such as a define or a different way to ignite muted), since that’s such a VERY specific use case. But I forgot in my previous comment, here’s how I tested the spamming with gestures, not sure if the preons or battle mode would make a difference or not but so far in my testing they haven’t:
#define FETT263_SWING_ON
#define FETT263_THRUST_ON
#define FETT263_STAB_ON
#define FETT263_STAB_ON_NO_BM
#define FETT263_TWIST_ON
#define FETT263_TWIST_ON_NO_BM
#define FETT263_TWIST_OFF
This is not a thing, where did you find this define?