Select one of the following categories to start browsing the latest GTA 5 PC mods:
@kmcgurty1 ah, my mistake. Well, the script is out there now. We'll just have to let it die it's slow death.
@kanersps Ehh. I'm with you, sort of. This is something that I've been using for a while on my own and figured I'd share the code with those who wanted it. There are (probably) enough trainers, quick car mods, and kitchen sink mods to go around, but I've yet to see something that would allow a player to create a palette of their favorite colors and press a button to see them instantly applied to their current vehicle. And I agree that essentially this script is superfluous, and only has a small, singular focus.
That being said, with the amount that I use this script in everyday gameplay, even while having a comprehensive .net-based trainer, makes me think that this code isn't entirely without value.
@viper-kk @DylanCHFE I can change the thumbnail. I'm not sure what else to use, so I am open to suggestions.
By popular demand: Mod toggle added.
@Flava0ne unfortunately, pure black tints are not (currently) in the PC release, and as far as I can figure, only exist in the XBOX/PS4 versions. They may be added during a later update/DLC release, but as of this moment, pure black tint (and dark green tint) aren't in the PC version. *sad face*
I'm trying to get a video, but its both slow going and extremely boring. It's essentially a static video of the rims changing on a truck, car, and motorcycle, which is the only thing the mod does.
I also have a pretty crappy laptop using an Intel 4400 trying to chew on this thing, meaning screenshots and videos look like crap (see above). I'm a decent coder, but my equipment isn't exactly top notch, gnome sayin'? I'll try to get some more screenshots up, at any rate.
Anyway, it's a non-obfuscated LUA script that is open for viewing/editing. It couldn't do anything nefarious if it tried.
It would have all rims according to the update you have. The function is modular and polls all available rims, so if you have the update, then the rims will be there.
I wonder if using the native name rather than the hash would make a difference? So instead of
VEHICLE._0x2AA720E4287BF269(veh, 0, true)
you could use
VEHICLE._SET_VEHICLE_NEON_LIGHT_ENABLED(veh, 0, true)
I have no idea why that would make a significant difference, but it might be worth trying.
@Jo990 Cheetah Carbon R is 18, not 19. If you are looking at the rims database, you need to subtract one from the number.
@sp4c3m4n "soundjester" works for me.