ProffieOS v6.3 BETA testing

ProffieOS
343

Ah dang it my fault, I’ll download and re-test. Zoom sound was working on my two button for some reason though with this one.

And thanks for the info! Maybe I’ll try to come up with something. Correct me if I’m wrong but gesture sleep doesn’t affect the battery drain from the gyro right? Because it’s still on and waiting for motion, even if it’s only the “gestures on” motion? I’m just thinking maybe there can be a quick button combo which functions as a “wake up” or something, I like motion timeout but want to also be able to activate the saber with gestures without first having to trigger something else

344

Gesture Sleep just prevents gesture ignitions while it’s enabled, it is unrelated to MOTION_TIMEOUT. The gestures are still detected as long as motion didn’t timeout, the ignitions just aren’t triggered.

345

Ok I thought so, I’ll see if I can’t mess with it, thanks again!

346

Sorry about that, working great! I noticed the prop does still say to hold PWR for ColorWheel instead of double click and hold though, and I’m using the test rotoscope style which I think uses the ColorList but that is also a double click and hold for one button.

I also noticed when changing the color on the rotoscope style sometimes with a starting color of red, it immediately switches to blue. This preset was copied from another blue one using the on-the-fly copy and change so not sure if that’s the cause or not, I don’t have edit mode defined on this one. Not a huge issue because you can just scroll all the way back, but might be annoying if you’re just wanting to make a small change

347

This will depend on the Style Option, styles with multiple style options that change the use of BASE and ALT colors, some options use the ALT color as primary but the on-the-fly CC only affects BASE color, that’s where the comment section of the style code in your config becomes important.

348

I guess I should call it “discount rotoscope” lol I grabbed just one of the options and the intensity melt for this particular style and kinda combined it with an existing 5.9 style, so I don’t think it’s using Style Option? I could be wrong though, still getting used to all this. I think it’s also just the randomflicker stripes so I don’t believe I’ve got the hyper responsive swing effects but I’m just mixing and matching to test things out. But I used the style below and set it to blue, then used the on-the-fly copy preset to have two blue “discount rotoscope” presets, then used the on-the-fly font change and color change to set it to a red vader. The red vader preset is the one that sometimes immediately switches to blue on color change. I do have a two button build that has edit mode and a config with all of the os6 test styles but haven’t ran into this issue so it might just be incredibly situational for me, but I can try this exact sequence of events on it and see if it does the same thing

StylePtr<Layers<
	RandomFlicker<Stripes<10000,-2600,RgbArg<BASE_COLOR_ARG,Rgb<255,0,0>>,RgbArg<BASE_COLOR_ARG,Rgb<255,0,0>>,Mix<Int<7710>,Black,RgbArg<BASE_COLOR_ARG,Rgb<255,0,0>>>,RgbArg<BASE_COLOR_ARG,Rgb<255,0,0>>,Mix<Int<16448>,Black,RgbArg<BASE_COLOR_ARG,Rgb<255,0,0>>>>,RgbArg<BASE_COLOR_ARG,Rgb<255,0,0>>>,
	LockupTrL<Layers<AlphaL<AudioFlickerL<Rgb<255,225,0>>,Bump<Scale<BladeAngle<>,Scale<BladeAngle<0,16000>,Int<4000>,Int<26000>>,Int<6000>>,Scale<SwingSpeed<100>,Int<14000>,Int<18000>>>>,AlphaL<NavajoWhite,Bump<Scale<BladeAngle<>,Scale<BladeAngle<0,16000>,Int<4000>,Int<26000>>,Int<6000>>,Int<10000>>>>,TrConcat<TrInstant,White,TrFade<400>>,TrConcat<TrInstant,AlphaL<White,Int<0>>,TrWaveX<TransitionEffect<NavajoWhite,Rgb<255,225,0>,TrInstant,TrFade<200>,EFFECT_LOCKUP_BEGIN>,Int<300>,Int<100>,Int<400>,Scale<BladeAngle<>,Scale<BladeAngle<0,16000>,Int<4000>,Int<26000>>,Int<6000>>>>,SaberBase::LOCKUP_NORMAL>,ResponsiveLightningBlockL<Strobe<White,AudioFlicker<White,Blue>,50,1>,TrConcat<TrInstant,AlphaL<White,Bump<Int<12000>,Int<18000>>>,TrFade<200>>,TrConcat<TrInstant,HumpFlickerL<AlphaL<White,Int<16000>>,30>,TrSmoothFade<600>>>,ResponsiveStabL<Orange,TrWipeIn<600>,TrWipe<600>>,EffectSequence<EFFECT_BLAST,TransitionEffectL<TrConcat<TrInstant,AlphaL<White,BlastF<200,200>>,TrFade<300>>,EFFECT_BLAST>,ResponsiveBlastL<White,Int<400>,Scale<SwingSpeed<200>,Int<100>,Int<400>>,Int<400>>,ResponsiveBlastWaveL<White,Scale<SwingSpeed<400>,Int<500>,Int<200>>,Scale<SwingSpeed<400>,Int<100>,Int<400>>>,ResponsiveBlastFadeL<White,Scale<SwingSpeed<400>,Int<6000>,Int<12000>>,Scale<SwingSpeed<400>,Int<400>,Int<100>>>,ResponsiveBlastL<White,Scale<SwingSpeed<400>,Int<400>,Int<100>>,Scale<SwingSpeed<400>,Int<200>,Int<100>>,Scale<SwingSpeed<400>,Int<400>,Int<200>>>>,ResponsiveClashL<TransitionEffect<Rgb<255,225,0>,NavajoWhite,TrInstant,TrFade<100>,EFFECT_CLASH>,TrInstant,TrFade<400>,Scale<BladeAngle<0,16000>,Int<4000>,Int<26000>>,Int<6000>,Int<20000>>,LockupTrL<AlphaL<BrownNoiseFlickerL<White,Int<300>>,SmoothStep<Int<30000>,Int<5000>>>,TrWipeIn<400>,TrFade<300>,SaberBase::LOCKUP_DRAG>,
	LockupTrL<AlphaL<Remap<Scale<RampF,Int<65536>,Int<0>>,StaticFire<Mix<TwistAngle<>,OrangeRed,DarkOrange>,Mix<TwistAngle<>,OrangeRed,Orange>,0,3,5,3000,10>>,SmoothStep<IntArg<MELT_SIZE_ARG,26000>,Int<6000>>>,TrConcat<TrWipeIn<100>,AlphaL<Red,SmoothStep<Int<29000>,Int<8000>>>,TrExtend<2000,TrFade<300>>,AlphaL<Mix<TwistAngle<>,Red,Orange>,SmoothStep<Int<29000>,Int<8000>>>,TrFade<3000>>,TrWipe<200>,SaberBase::LOCKUP_MELT>,
	EffectSequence<EFFECT_POWERSAVE,AlphaL<Black,Int<8192>>,AlphaL<Black,Int<16384>>,AlphaL<Black,Int<24576>>,AlphaL<Black,Int<0>>>,
	InOutTrL<TrWipe<300>,TrWipeIn<500>,Black>,
	TransitionEffectL<TrConcat<TrInstant,AlphaL<Mix<BatteryLevel,Red,Green>,Bump<BatteryLevel,Int<10000>>>,TrDelay<2000>,AlphaL<Mix<BatteryLevel,Red,Green>,Bump<BatteryLevel,Int<10000>>>,TrFade<1000>>,EFFECT_BATTERY_LEVEL>,
	TransitionEffectL<TrConcat<TrInstant,AlphaL<Green,Bump<Int<0>,Int<4000>>>,TrFade<300>,AlphaL<DodgerBlue,Bump<Int<0>,Int<4000>>>,TrFade<300>,AlphaL<DeepSkyBlue,Bump<Int<0>,Int<4000>>>,TrDelay<7350>>,EFFECT_PREON>
	>>()
349

It’s either seeing it in your presets.ini or something else you did. It also depends on how many blades you have and other factors in the styles themselves. It’s most likely specific to what you did, unless it’s repeatable on the test styles or a fully built Edit Mode style I’m not sure what to do with it.

350

Ok no problem, I’ll mess with it more, it’s definitely very situational lol.

It does spark another question though, if I start upgrading my current 5.9 styles to edit mode styles or styles with options, do I need to do anything with those presets in the ini or do they get “updated” automatically?

351

Nope, the styles just need to be set up correctly, the OS generates the .ini files you don’t do anything to it.

352

Very awesome, thanks again!

353

I’ll reply later with a paste to the config as well as any serial monitor info I capture.

In the meantime if this is fixed today let me know.

Issue: Volume Controls not working. Fett263 button prop.

Not sure I am missing something as to the instructions/steps here, is anyone else (aside from one other I know of) experiencing an issue w volume control?

Enter Edit Mode holding Pwr/Aux until blade ignites and it says “EditMode”.

Twist saber until it says “VolumeControl”.

Tap Pwr to begin being able to twist saber, then rotate up or down (Scroll hours are “softer” with newest GitHub download) with saber held parallel to ground (horizontal). *Also tried it on a flat surface (table).

Tap Aux to exit.

When I tap Pwr it exits rather than enters and is now has just basically done a standard ignition.

Messed w it for two hours and gotta goto work so will try again later. May swap in a fresh battery but it’s still not in the red zone so honestly this shouldn’t be an issue.

354

There’s two ways to do volume in my prop (controls depend on 1 button or 2 button). If you’re in Edit Mode then Edit Volume is under the Edit Settings submenu, you have to enter the Edit Volume mode before you can actually edit it. There is no prompt that I know of that says “VolumeControl” so not sure where that came from, if you have mods or are using sounds outside of the provided prompts then take a look at your Serial Monitor to see what it’s trying to play, but your description is missing the Edit Settings submenu so you’re not actually entering Edit Volume.

There is also a Volume Menu option while the saber is off, controls are explained in the prop file.

355

Volume Control meaning the font that plays when you enter it or whatever the voice prompt would be but in my case it was the saber stand sound font from Fallen Order or the SpeederBike revving from Son of Corellia. They are all properly labeled so they aren’t the issue but I disabled those already just in case and it still isn’t doing what it should. Yes I removed the temp and ini files from the SD to make sure it also wasn’t that.

So I’ll take a video and post it as well as yes, whatever I get from serial monitor.

Here’s the thing though, and another person can validate this, it all worked fine for a whole day then started acting up.

356

I just tested on 6.1 with 2 button config. I can get volume control when the saber is off by entering volume menu with the button commands. Rotate the saber counterclockwise reduces volume, clockwise increases volume. Volume level saves with power button.

Also tested it in “edit mode/settings/edit volume”. That works as above as well.

357

I’m not sure if you’re referencing my issues with volume menu or not, but my issue is not with entering or exiting the menu. I’m having trouble with the dial (only in the volume menu). Your message did prompt me to go into Edit Mode->Settings->Volume to see how that dial responded. It didn’t lock up on me at all no matter how quickly I turned the dial. As you mentioned, my issue with the other dial was working for a bit, then suddenly wasn’t anymore

358

Loving 6.1 so far, makes 1 button configs sooooouch easier.

However a couple things I keep having occuring:

Sometimes, I will ignite, there will be no sounds, no hum, but blast effects will still play sounds. Saber will not retract until I hold down aux, then “battle mode off” plays and I can retract the saber.

When this happens, I have to pull the power and when powered up again, it functions normally.

I think this has to do with sleepode but not sure.

Additionally, when entering volume menu, I can turn the volume to maximum no problem, but turning down volume often only allows for 2-3 clicks and then it does not respond. Exiting the volume menu and going back in is the only way to turn volume all the way down. Sometimes, I have to repeat 3 times to get to minimum.

This may or may not occur when entering volume menu through edit mode, have not tried enough times to test.

1 Like
359

Fett263, NoSloppy, and MegatoothSith thanks for your patience and time. I’m gonna run more testing but in the meantime I did double check and there was a spare folder on the SD for the custom sounds that I missed in the deleting process called “CustomMenuSounds”. It’s a weird thing how it interfered in the menu though because it wasn’t in any specific font pack. I just had it by itself in its own folder. Since it was possible it may have interfered with how things read I grabbed a different SD as a test bed then went about removing that. From there I cleared any leftover tmp and ini files, flashed the board, and it does work as it should so far.

360

Can you try to replicate while connected to Serial Monitor and provide the output. It sounds like you have a button sticking but let’s see what presses are being seen.

1 Like
361

I’m looking into this with profezzorn, it appears isolated to the standalone Volume Menu while Off, if you’re over-turning the dial instead of taking “steps” (turn-stop-turn-stop) the sound is getting hung up so the dial doesn’t register. Once we get a fix we’ll update.

1 Like
362

Glad to hear, if you have odd behavior always best to start “clean”.