Thanks! I appreciate that!
Thanks for posting this topic. You’ve given me a good idea for my next bladestyle demo video on my channel. I’ll step through each of the Graflex blue bladestyles & RGB values I use for each SW episode that the graflex appears in:
Revenge of the Sith (technically a desert slayer, but it’s graflex-esque)
A New Hope
Empire Strikes Back
The Force Awakens
The Last Jedi
Rise of Skywalker
The Kenobi Series (Training flashback scene)
In each of these movies the blue value used is slightly different… darker in some cases, lighter in others - not just due to the back drop of a particular scene. During the time I’ve been doing bladestyle demo vids on my YT channel, when I do canon styles specifically, I will typically put together a “custom” color value I think matches the movie as best as I can get it, and will store that color value in my colors.h file. I’ve already done this for each of the movies, so might as well demo them all in one vid.
How intuitive to get them on colors.h so that they are always available for selection without add’l customization. I’ll have to forgo OS6 spoken color names for them, but probably worth it!
tl;dr You conceptually* should be able to put those customized values into colors.h for OS6 and give them customized names. You’re expanding the OS color list to where you can then just put the color into the style under the custom name. Similar should be possible with all the props, but I may be mistaken. You’d just need to be sure any given prop either has the list or feeds from colors.h and then respective color wav’s in the common folder structure so they are spoken. I know there’s more than one of us here that’s done this with the old OS.
Disclaimer: *At least that’s what I think/interpret without actually having done or tried it in the newest OS yet. I did this with OS5.7 when I put in “KatarnBlue” , “KatarnOrange”, YunYellow", and “QuRahnGreen” as custom shades.
Post the idea into the OS7 Feature Request topic. I’d love to see what the consensus is on this and the other stuff as to color values.
Off-Topic as far as Graflex and Obi blues but if anyone wants to research the Kyle color bit this is the old discussion.
If people can agree on colors, and some reasonable names for those colors, I don’t mind adding them to ProffieOS at all.
@profezzorn Sweet!
Ok team, there ya go. Who wants to start a thread for voting and submissions? I’m gonna love seeing this play out.
I’d say Fernando’s Silver option should be a standard colour.
Thanks @profezzorn! I’ll second @astromech re: silver. I wonder what colors we’ll be able to gain consensus on RGB values for.
Cheers to all who contributed to this. It’s been helpful to me as I tinker with just the blues!
The Color List in my prop contains additional colors I’ve developed that are supported by library as default options and built into Edit Mode as “starting points” for colors not in colors.h.
I’d shy away from “character” naming as it is wildly subjective IMHO. I’ve actually tried to color match for characters multiple times for the library and find it is extremely hard to do. Especially since there are so many factors involved in how people perceive colors as well as variations in blade materials, construction and the actual LEDs. More named colors is fine for generic color naming but I would not support a character color name as you’ll never get a consensus nor will it actually ever be “screen accurate”.
Agreed @Fett263. Consensus and accuracy are nearly impossible to achieve here for character-specific. While “Silver” may be an exception, many other colors will need tweaking.
That being said, your Gold, Silver, and Deep Purple are colors I’ve used as starting points for character-inspired colors.
Yeah, gold is another I use a lot and having it official would be cool.
Thanks. Yeah, the Color List colors are ones I’ve “dialed in” over time (with a good amount of testing) to look good both on the actual blades in person and in digital pictures, but it’s all subjective which is where finding a consensus will be challenging.
Consensus doesn’t have to be perfect though, people who disagree can always use RGB values.
I just don’t want to add (more) colors that people never use.
Totally agreed as to the character named color bit as well as the differences in visual interpretations. I was just citing an example is all. I wouldn’t expect those to be a standard. I do like the idea though of having specific options not just for us. Something other users can tap into if for nothing more than starting points would strengthen the overall package. @Fett263 putting in all that’s in edit mode has helped a ton.