Hi Alex,
The low speed problems might be a little bit improved with a different
integration method, but I think basically you'll just see a situation where the
problems become visible at a lower speed, but are still there.
In the slip ratio case it's simply because you're dividing by the tire's
velocity. The smaller it gets, the more extreme the slip ratios become. (Bang
bang!) The same thing happens at low speed slip angles too, and doesn't really
go away no matter what you do. At low speed, the slip angles can jump very
quickly to very big positive and then negative numbers. Another integration
method might help, but the problem will still intrinsically be there.
IIRC, Matt Jessick mentioned that he worked for many years on aerospace
simulators where the problem also existed. Motion simulators don't like to
stop, generally.
The quickest way to fix/improve this that I know of is to have a low cutoff
speed, where the slip ratio calculation changes to a simple subtraction
problem. Here's what I do:
IF ABS(Tire_Long_Vel) < 1 THEN
Slip_Ratio(Tire) = ((Tire_Rot_Vel(Tire) * Tire_Radius(Tire)) - Tire_Long_Vel)
* .5
ELSE
'//Brian Beckman's formula--
Slip_Ratio(Tire) = ((Tire_Rot_Vel(Tire) * Tire_Radius(Tire)) - Tire_Long_Vel)
/ '//
ABS(Tire_Long_Vel)
END IF
When the tire velocity is below 1 ft/sec, it simply leaves out the division
part. Then I throw in a little factor to multiply by. Works for me. Of
course, you can't stop on hills with that though, but if you're 2-D here, this
should work fine. (You might play with the constants of course to get it to
work with your system, or maybe even have them self adjust according to
velocity. Hmm...)
I don't know how to fix it in the lateral/slip angle direction either. Haven't
given it much thought anyway because sideways jitters aren't visible with cars.
The only way a really slow computer hurts my low speed performance is if it is
so slow that it can't do the calculations in real time any longer, which just
doesn't happen on my 333Mhz laptop. Graphics and intersection calcs (unless
you're good at trees) will take up most of the CPU time, probably. If it
starts to happen anyway, it's time to raise the "minimum system requirements",
I think! ;-)
That would be great! Thanks :-) Will you be continuing on and making another
simulator of your own for us to play with? :-D
Todd Wasson
---
Performance Simulations
Drag Racing and Top Speed Prediction
Software
http://PerformanceSimulations.Com
My little car sim screenshots:
http://performancesimulations.com/scnshot4.htm