If I’m using OS 8 and each preset uses a complex blade style, how many fonts/presets should i have at max? How many if it’s a simple preset repasted for each font? (like a static color)? Also, does the edit menu (like color change and stuff) have to reside within each preset on OS8 or is it accessible no matter how many presets you have?
It’s hard to put an exact number on that especially given complex can mean different things. My experience is that I can only get around 8 of some of what I considered to be complex styles to fit. For less complex styles, you can fit quite a few. Have you already tried and not been able to get them on there, or are you just doing some preliminary research?
I can’t even fit more than one bladestyle on my 2.2 with OS8. Stuck with OS7.
Oh wow. I have to admit it’s been a while since I tried to max one out. My v2.2 builds these days are usually rebuilds of existing sabers, so they’re not pushing the board. So I ran some real compiles this morning.
Using the LGT duo config that ships on their cards (34 presets, nice styles but not overly complex) on a V2.2:
| OS 7.15 | OS 8.10 | |
|---|---|---|
| As shipped | 243,568 (92%) | 254,384 (97%) |
| With Fett263 + full features | 250,200 (95%) | 260,328 (99%) |
So the board is basically full in every combination, even bone stock. The budget scales with presets times style complexity times blades, and edit-mode styles with all the RgbArg/IntArg slots cost several times more than hardcoded ones, which lines up with what astromech is seeing. A fully loaded build really can run out of room that fast.
Dropping back to OS7 only buys about 4%, roughly one complex style worth of space. The bigger levers are reusing the same style across presets (identical styles share the space), trimming defines you don’t use, and going lighter on edit-mode styles.
I generally reach for a V3.9 these days. Double the flash makes the whole problem disappear if you have the newer hardware.
Bonus experiment, because the compiles were cheap: to test the style-sharing claim I built configs where every preset is the exact same style, and just kept adding presets.
Fonts on the SD card were never the limit at all...
| Presets (all the same style) | OS 7.15 | OS 8.10 |
|---|---|---|
| 1 | 174,168 (66%) | 187,040 (71%) |
| 60 | 175,624 (66%) | 188,512 (71%) |
| 240 | 180,536 (68%) | 193,408 (73%) |
Two things jumped out. First, a config with a single preset is already 66% of the board, so the OS itself owns two thirds of a V2.2 before you add anything. Second, look how little the preset count matters once the style is shared: 240 presets costs about 6KB more than 1. Each preset that reuses an existing style adds roughly 27 bytes.
Then I got curious where the actual wall is and kept going. The compiler finally said no just shy of 1,700 presets, and here’s the fun part: it wasn’t flash that ran out. The board ran out of RAM for the preset list itself, with 12% of the flash still free. So the real limits are styles times complexity times blades for flash, and if you ever manage to sidestep that with sharing, RAM caps the preset list around 1,700.
1 Like
ah ok thx. I was just doing some research before hand. I just got a proffie 2.2 which came with mostly flicker and fire-like styles but a few responsive ones. I guess it’s good that i can fit as many fonts as i want tho, just recycle the presets and just one or two super nice blade styles. Also, I noticed that on some fonts the color change won’t work. Is that because you have to code that into each preset? (that’s kind of what I meant when i said, " Also, does the edit menu (like color change and stuff) have to reside within each preset on OS8 or is it accessible no matter how many presets you have?"). This one came with os 5.9 so I’m gonna change it to the newer one soon unless it would serve my purposes less
Good question, and it actually explains what you’re seeing on 5.9. The edit menu is global. It lives in the button/prop code, not in the presets, so it’s there no matter how many presets you have. What changes is whether each preset’s style knows how to respond to it.
Color change only works if the style was written to support it. If a style has hardcoded colors, the menu will spin but not change. So it’s not the font, it’s how each style was built. Some of yours have color change baked in, some don’t.
OS8 with full edit mode is the same idea, just bigger: one global menu, works on any number of presets, but only styles built with the editable slots respond. Those editable styles are also the expensive ones from my compiles earlier, several times the size of hardcoded styles. Wanting everything fully editable is exactly how a 2.2 fills up fast. On a 2.2 I’d do a mix, fully editable on the few presets you actually mess with and simpler styles everywhere else. And yeah, upgrading from 5.9 is worth it. That’s where the newer edit stuff lives, and you saw from my numbers what it costs in space, which on your board sounds like a non-issue since you’re planning to share some of the styles anyway.
That’s helpful thanks! Also, i asked kyberphonic who made the blade styles for his shadow lord video and he said arjsworkshop on insta. Do you know of him and how i could get the blade style he made?
Glad it helped I don’t know him, but if you end up tracking down the style and it’s ok to share that would be awesome!
FWIW, setting up Option Styles with Style Arguments and/or Edit Mode to create presets will typically allow you to fit a good amount more by using a single style across multiple presets while still having different combinations of options and colors.
My config helper tool can help set up Using Functions and Style Arguments to generate more presets. The videos at the top of this thread is a good starting point.
1 Like
Yes, and that’s something I wholeheartedly support! Thanks for all you do Fett263. I always use your using functions and it’s quite helpful.
so it uses less memory if it’s a “subset” of a blade style rather than a whole one?
oh also, if i wanted to make a blade style that mirrored an ignition sound that has two parts (or make a preon + an ignition sound), how do i have the very bottom of the blade light up white until the second sound plays and then it ignites into another color/effect?
You’d set up a preon effect and then have a preon.wav and out.wav in the font.
1 Like