PWM on clutch would be a bonkers approach... however, I think the launch control on the M3 CSL used a PWM type method on the clutch (rapidly opening/closing it so the engine didn't bog down), which is pretty cool.
Onyx is great but so far Ruud has only put in a few variables (system.html output lists them), but not sure why there is a limit. Ie, no tyre rates, rolling rad, rolling coeff, pacejka, clutch torque, car cameras, sounds, etc etc...
The WHOLE car.ini variable list should be in Onyx, and every user input should also be in there too.
Same for the track special.ini stuff too.
If it's exposed then it lets us be creative and do things better.
Ie, recently I added a nice ABS script which is imo tons better than Ruud's implement. Not putting down Ruud's work of course, but we can spend more time getting these things perfect than Ruud can... just exposing the right variables to us is all he needs to do!
I too would like to see the clutch exposed. Current operation in the very latest version *should* be linear, not the square of the value set (it was a square curve before apparently)
Having the clutch times exposed via Onyx system script variables, we could then make the clutch times slower when at low engine loads, and then make them faster when at high engine loads (perhaps via a crv lookup)
That way automatic gearbox would be nice and slow when tootling around, and then sharpen up when you floor it.
Again, not something Ruud should waste his time on, we can do all these things...
Hopefully it is Ruud's plan to expose all these needed variables to Onyx asap
All variables exposed and some crv loading logic would make Racer suddenly very very powerful. Why hard-code when it can all be editable?
Dave