ProffieOS 8.4 beta (call for testers!)

[orntar]

I appreciate the shout out. I feel like I did start early on this. I have been busy with a home reno project, but I could set aside some time to test my display more if needed…

[olivierflying747-8]

@profezzorn

Spoken battery level in both volts or percentage.

tested

@profezzorn

Next / previous preset.

tested

@profezzorn

Defaults to KILL on boot.

tested

@profezzorn

Option to use separate effect sounds to match the current mode.
By using alt sound folders in the font, each mode can have better matched effects
(reload, full, clipin/clipout, etc…).
Sounds for the modes should go in the following alt folders:

• STUN mode - alt000
• KILL mode - alt001
• AUTO mode - alt002

tested

@profezzorn

No jam if empty.

While testing, I hadn’t memorized the control for reload. Trying to “find” reload while empty, at times, I kept firing. I never had a jam while empty, so I guess it could be marked as tested ?

@profezzorn

AUTOFIRE mode is enabled simply by having auto.wav files available in the sound font.
This mode also counts bullets and causes an “empty clip” if you use
#define BLASTER_SHOTS_UNTIL_EMPTY.
Each shot is timed to the length of the wav file that’s playing, and
the empty sound repeats at same rate auto was firing for added realism.

tested

I played with blaster_BC_buttons with my multi_prop. All the above are working as advertised.

[profezzorn]

@olivierflying747-8

Not sure if this counts, but I wanted some extra sounds added in my local sound library to avoid multiple identical EFFECT defines compile errors between mine and others props while using my multi_prop. So I added some sounds to my local sound_library_v2:

No, that doesn’t really count.
It’s not testing that the V2 sound library works, it’s testing that the V2 library can be extended to V3 or something?

[profezzorn]

Top post updated - thank you!