Back to Main Page

This was an idea posted on GTAForums that I decided to investigate.


Glowing Brake Discs - Red Hot Action

During my rounds of GTAForums, I stumbled across a thread about Red Hot Brake Discs. The idea seemed interesting and had the potential to be another addition to GVE and VEP... so challenge accepted!

If anyone has read the Driver Information System page, you will have seen the parts about the door markers. This seemed like a prime candidate to adapt that system for something wheel based. So I quickly put together the code that got me the bone positions of the wheels and immediately ran into the scripter's worst nightmare... addon vehicle modders.

By rights, I should have been able to use the hub_lf, hub_rf etc... bones but of course, that would have required addons to use those bones properly... never going to happen. So I opted for the wheel bones and that proved equally as risky. I had to choose one, so wheel bones it was. I got the location of each bone and to move the effect into a visible area, I added a .025f offset, or -.025f depending on which side of the vehicle they were on.

Note: Under consideration is the ability to specify vehicles in the ini file with offsets so that any really troublesome vehicles can be manually adjusted to be perfect.

So that got me the markers in roughly the right place and then I turned the front wheels. There were two problems with the front wheels.

1) They turned when you steered.
2) The amount they turned was slightly different to the amount of steering that was being applied.

The solution to number 1 was something I had dealt with in my CCTV watcher mod and that was rotating an offset around a base object that was also rotating. The front wheels turned on a car that was also turning.

The solution I had used was a Quaternion.Euler function, that would rotate a position around a rotation. I was lucky to have found that because that's the kind of thing I could take days to think about and then still not have something that worked.

Number 2 is something I have taken a shortcut with for now, it actually rotates 80% of the steering angle, which seems to work okay for the outer wheel but the inner wheel is going to be different, so that's something I will have to come back to.

Update: Number 2 turned out to be a pain in the backside. I hadn't taken into account the steering lock ratio, which I now have but like real cars, when you turn left or right, the inner and outer wheels turn by different amounts. So it was a case of "Which of these numbers will modify the angle by the right amount to make things work?". That now seems to be fixed... fingers crossed.

Further Update: Number 2 isn't fixed... what a complete pain this is, there seems to be no consistency in the turn amount. I must be missing a value somewhere but I just don't know what. Sometimes, the consequences of being a broken person are far-reaching, having no info sources makes things doubly-difficult. :(

So I had the markers, they all tracked the wheels, so now it was time to create the effect. This was basically a case of modifying the red, green and alpha values to simulate heat build-up in the discs. The heat is built up based on the speed you are travelling and the amount of brake pressure being applied. That's probably an overly simplistic way to do it but it seems to work. Sometimes, simple things just work and simple things cost very little in processing power, so it's good when they do work.

So zero heat = 0 Alpha = 0 Red level. As the heat increases, so do the Alpha and Red levels, which probably seems obvious. Alpha is clamped at 192, in the hope of allowing the texture behind to still appear visible to a small extent.

But then there's the Green level, which I wanted a bit more control over, that's a level I call overheat. Overheat is a level that starts to kick in as the discs hit 33% of their maximum heat level and it's based on the accumulation of that final 66% of heat. But to ensure the discs don't go into blazing yellow, they're restricted to build up at half-rate and clamped at half-maximum value.

Here's a more graphical view of how it works... this doesn't quite convey the actual colour process as it appears ingame but it gives you the idea.

Once you stop braking, the brakes cool down based on elapsed time and Alpha, Red and Green levels decrease accordingly.

This is a short video of how the effect looks in a replay around the airfield with 3 Acura NSX cars. Even though the processing is based on simple number manipulation, it seems to work well.


As you can probably guess from this, I have already built this into VEP so that any cars sent to it during LCA replays are able to display the effects. The player vehicle functions will be moved into GVE once I am happy that things are stable. If performance shows signs of suffering, I have code in place that will detect which side the car is being viewed from and will only display the effect on the wheels on that side. The effect is small though, so it might be okay as it is.

An issue did pop up today with the different sized wheels and the effect size. So I added some code to get the wheel dimensions and to scale the effect based on the rim size. This will work independent from front to rear, to cater for any vehicles with bigger rear wheels.

So that's another rapid development cycle for something that has reaped big rewards in the mods I use. It just shows, even the smallest ideas that nobody else cares about, are always worth time investing in them.

Update: I decided to add an adjustment mode to this to combat the wheel issues. It's a simple mode that just lets you move the effect forwards and backwards from the wheel and allows you to scale the effect. It then saves those settings to an ini file that is read by GVE and VEP, so that it can adjust any vehicles that get used. Simple enough but as you can see from this image, it makes all the difference. The top view is before adjustment, the bottom view is after.

Update: Well once again I asked a question for some info and once again, I was met with a wall of silence. I was missing a vital piece of the puzzle to fix the front wheel brake discs and I couldn't find it, so I asked for help. It seems no matter how much help I give out, there is always zero help in return from the "community".

I actually did find it with the help of my Offset Watcher mod, which dumps a real-time updating hex dump of selectable memory locations onto the screen. So now the brake discs perfectly align with the front wheels, which is extremely satisfying.

Funny really, I was asked if this mod was going to see the public light of day. Every time I write a mod, I always ask myself that and then after I have tried to get help, I remind myself that it isn't. This was the 4th personal request mod I have created since I stopped public modding, I still provide answers, I still provide solutions and the GTA V Modding community still provides a reason for me to have nothing to do with it. And it's a pity, because this mod is so much better in the game, than it is on the crappy videos I produce. People could have been creating videos with these mods and instead, they're left to just watch them.

I am genuinely proud of the mods I create and share, I wonder if there are people genuinely proud of the irreperable damage they have done to the GTA V modding scene? I sometimes think there are.

Update: Turns out my jubilation was premature about finding the missing vehicle property and after another day of watching endless screens of values, without even a hint of knowing if I am in the right place, I am sorely tempted to just quit. I have spent the day dumping 6000+ line data files that weigh in just short of 100KB and nowhere does this steerWheelMult value even appear as a value that matches what is written in vehicles.meta. I even created something blatantly obvious, .345678 in the meta file and that value was nowhere in the data I dumped. But if there does seem to be a matching value, it isn't there in another car, which means it was just a coincidental match.

What is really intriguing is the one source I can usually rely on to get accurate info like this, is also wrong. So at least the value is not just eluding me, the other person's code always returns 1, which is of course, incorrect.

So the solution to this problem turned out to be another parameter in the DAS (Disc Adjustment System) config files. You can now set the simulated steerWheelMult value with gamepad inputs and they get saved for both GVE and VEP to use when required. Is it ideal? No. Does it work? Yes and at this point in time, that is all that matters.