I think I’ve got more implemented in mine already (more than 1k lines of code for the interface alone).
I’ve got the x,y grids for facial features (with presets too) working, with all the proper hairstyle, facial hair, feature and heritage names pulled straight from GTAO character creator/barber shops and mapped to correct list indexes (skipping things that don’t belong like the nightvision helmet).
I’ve made a pull request to skinchanger with changes that make face blending and facial features possible. You can already use these customizations with esx_skin without any changes to it if you pull skinchanger from my fork.
I’ve got custom color palettes built (taken from GTAO) separated for hair, lipsticks and blushers, while this creator just uses one huge palette with what seems to be all the colors that RageUI authors created.
I’ve actually took time to analyze data and behaviour of GTA Online’s character creator and tried to mimic it (and maybe improve, but that’s more for later) as best as I could. Is why I need these color mappings.
I’ve spent a lot of time on this project.
I also plan to separate clothes from character features into two completely different menus inside one resource.
Also this creator you linked depends on esx_skin which I find weird, a character creator should REPLACE esx_skin as they serve exact same purpose. Mine depends only on es_extended and skinchanger.
Thanks for that link though, I was wondering if I could use natives to manipulate the faces instead of skinchanger and still save it, this shows me that I can. Updating the x,y grids in realtime with skinchanger events being sent every frame is really slow.
Yes, I pull from RageUI into my fork pretty regularly and it absolutely uses the 2.0 version now.
As a side note, the creator you linked actually has installation instructions that require modifying other resources… imo that’s a very bad way to go about it. If you use resources from other people and these resources aren’t adequate for your purposes, make a fork or (even better) a pull request, then tell users to get the dependencies from your fork. Always design your projects to be as self-contained as possible.