I have a OLED screen want to add some extra images for my proffieboard 2.2

B_Duarte · October 17, 2024, 4:37am

I added a font image that’s great. Can you add a bmp image for when the saber uses force or turns on. I wasn’t sure how you would type that in. For font I just have “font” titled for that image and that works. I saw a guy I don’t know if it was a old video typed like font.bmp. If anyone has any ideas, would be appreciated

profezzorn · October 17, 2024, 6:38am

You can start reading here:

Although that page is a bit outdated. The full list of available effects can be found here:

github.com

profezzorn/ProffieOS/blob/d2ae53b2c35c59e3a3bd124fb17351220857459d/display/ssd1306.h#L83


      
            float ProffieOSClipoutImageDuration;
            // for OLED displays, the time a destruct.bmp will play
            float ProffieOSDestructImageDuration;
          };
          
          
          
          #define INIT_IMG(X, ARGS...) ,IMG_##X(ConcatByteArrays<PREFIX, STRTYPE(#X)>::str, nullptr, Effect::FileType::IMAGE)
          #define DEF_IMG(X, ARGS...) Effect IMG_##X;
          
          #define ONCE_PER_EFFECT(X)			\
            X(boot)					\
            X(font)					\
            X(blst)					\
            X(clsh)					\
            X(force)					\
            X(preon)					\
            X(out)					\
            X(in)						\
            X(pstoff)					\
            X(on)						\

Sabersense · October 17, 2024, 11:52am

There’s a free download of a fun set of oled files on my website. The animations break up and crackle during clashes and blasts etc., to add a little bit more realism.

https://sabersense.square.site/downloads-freebies

B_Duarte · October 17, 2024, 1:04pm

Thanks I’ll work on it.

B_Duarte · October 17, 2024, 1:05pm

I’ll definitely check this out thank you.

ryryog25 · October 17, 2024, 3:13pm

There’s also the OLED bmp generator:

NoSloppy · October 18, 2024, 4:08am

I noticed in the ReadMe that it says to edit hybrid_font.h to customise image durations.
You are supposed to just do that in the font config.ini file, something like:

# -------- IMAGE DURATIONS -------- #

# Below are the display durations in milliseconds.
# If commented out or not specified, the default is used.
# As of ProffieOS 7, effect images and/or font "name" text
# can use 0.0 to automatically sync to the effect sound file duration.

# Boot image duration
# Uses the specified duration,
# falls back to the Font image duration if not specified,
# or defaults to 3500ms.
ProffieOSBootImageDuration=4000.0

# Font image duration
# Default 3000.0
ProffieOSFontImageDuration=0.0

# On image duration (if not looped)
# ProffieOSOnImageDuration=5000.0

# Blast image duration
# Default 1000.0
ProffieOSBlastImageDuration=0.0

# Clash image duration
# Default 500.0
ProffieOSClashImageDuration=0.0

# Force image duration
# Default 2000.0
ProffieOSForceImageDuration=0.0

# ---- Images below supported as of ProffieOS 7 ---- #

# Text Message duration 
# Used primarily for preset "name", but also Startup screen text and errors.
# Uses the specified duration,
# falls back to the Font image duration if not specified,
# or defaults to 3000ms.
# *Note* Startup text will display for a minimum of 3500ms to ensure readability.
ProffieOSTextMessageDuration=3500.0

# Preon always autosyncs

# Out image duration
# Default 2000.0
ProffieOSOutImageDuration=0.0

# In image duration
# Default 2000.0
ProffieOSInImageDuration=0.0

# Pstoff image duration
# Default 2000.0
ProffieOSPstoffImageDuration=0.0

Sabersense · October 18, 2024, 8:03am

That’s only needed if you’re using OS 6 or earlier. Under OS7, you don’t need to do it because the system is able to check and work with combinations of parameters from different config.ini files.

If memory serves, the issue prior to OS7 was that since many fonts have their own config.ini files, those files always took priority, and if a parameter wasn’t included in them, it would use the system default of that parameter. This made it tricky to have one oled folder shared across the entire system because it meant to change config.ini oled settings, you would have to do it in every font folder - if you tried it in a shared (common) oled folder, that oled config.ini would get dumped the moment the system found one in the font folder - even if that font folder one didn’t have any oled settings listed.

But then the Prof changed the system so that ProffieOS could take one set of parameters from a shared folder, and unless the font folder config.ini specifically over-rode those parameters, it would continue to use them rather than dumping them and going for system defaults.

This thread tells the full story of how it came about:

OLED Newbie Questions ProffieOS

I’m new to the OLED party, but I’ve been experimenting over the last couple of days. I’ve got it working thanks to NoSloppy’s excellent video tutorial series, but I have a few little questions: I’ve noticed that regardless of the length of a boot animation, it seems to play around five times. Is this controllable in the config somewhere? I know you can use the bpm thing to stop animations looping, but the way I’ve built my animations doesn’t yet include the slices that Brian talks about to split out the frames. All I did was grab a CFX animation as a single bitmap and add my own layers on top of each frame in Affinity Photo (Photoshop equivalent). I guess I will need to get to grips with the slicer thing in GIMP. WIP. Kind of related to the above, is there anywhere I can specify how long the OLED should display a given single frame or animation? I seem to recall reading something about editing the font’s individual config file, but all the ones I’ve looked at just have a humstart number and nothing else. I’m guessing that since the files are dealt with the same as wavs, that you can’t stack them so more than one file plays in sequence? The reason I ask is making long clip files that are 128 pixels by about 10,000 pixels could become a little unwieldy in the picture editing software if you want “edits”, although I guess it would word and might well be easier than any alternative. The book says to wire it to the SD + and regular ground. Does this mean it will never power down until you use the kill key? If so, is there any harm in running the negative from an LED FET and using a bladestyle to power it down after, say, 15 minutes of inactivity? As always, any thoughts welcome. Thanks in advance.

B_Duarte · October 18, 2024, 11:05am

Ya I am using OS6 it seems to work fine. In this case It sounds like time to change it. I am really a if it ain’t broke leave it. I built a fx hasbro Kylo Ren saber basically a total gut and install. There’s just allot of room in it for the OLED. So I put it in for some fun. I only got it to show the Kylo animation from the Cfx extra folder. I also have installed a few of those boards so knew about them. So I just put that bmp file in and titled it"font" and that worked so that’s good. I’ll have to work on that . Once again I appreciate everyone’s help. This continues to be a favorite hobby for me. I enjoy the challenges. My first board was the nano biscotte after that I was hooked!