Cosmetics Editor v3 - Known issues and TODOs

[garrettjoecox]

Anyone is able to take these on, if you need any help or pointers on adding additional cosmetics reach out to me on discord @ProxySaw

Todo List

• Clean up UI at the top of the window to be a bit cleaner
• Rainbow slider Tweaks
  • Reverse direction, so that faster is to the right, slower to the left
  • Describe what the number does (eg: full color cycle every x seconds)
  • Allow for even slower cycling
• Rainbow color "popping" every 10 to 20 seconds (this is a me being bad at math thing I think)
• Missing cosmetics from v2
  • Title screen fire
  • Magic effects
• Additional cosmetics
  • Health fairy color
  • Hookshot
  • Gradient trail colors

Known issues

• Some textures can only be as bright as the original color, notably link's hair, boots and gloves.
• Start/A/B color previews should respect color scheme (just the previews arent, the in game colors are)
• Shop cursor flashes for some colors
• In some cases when there are two colors to customize for an item, if the colors are too different(?) there is some weird clamping happening turning parts of the color black. This happens with the master sword when it's in the pedestal and some of the magic effects. This could be related to the reason saria's song has black color clamping in it's texture. I have verified this issue was introduced here
• Crash when re-sizing link on file select menu

[Gamer1758]

navi doesnt rainbow properly, she does change on reloads and soft/hard targeting, the target arrow(s) do rainbow properly.

[garrettjoecox]

Broken biggoron's sword doesn't match biggoron's sword

[garrettjoecox]

Sword trails don't properly reset until scene reload

[garrettjoecox]

Changing various colors in the cosmetics editor the game will crash on Wii U

[garrettjoecox]

Game crashes for windows DEBUG when changing cosmetics that involve DList patching the displayListEnd() command

[briaguya0]

i think the

Allow for even slower cycling

part would be best addressed by standardizing the rainbow rate across all interpolation values. Since it updates every frame, running rainbow at high frame rates (like 144+ fps) makes it really fast.

[briaguya0]

might be worth looking into simplifying the rainbow calculation by just changing the Hue value in an HSL color and then getting the RGB from that (then every frame we'd just be doing a currentHue + hueStep % 360 (or 2PI) then feeding it into something like https://web.archive.org/web/20030820171808/https://astronomy.swin.edu.au/~pbourke/colour/hsl/

just a thought, i tried digging into the current rainbow code a little and it's a bit hard to parse