brain farts

[stan.distortion]

Only glanced through but is there a scheduler in vdrift? Different process priorities etc? Guessing there must be. Can/do you drop things moving fast on the screen so big sums can be disguised motion blur? Anything fast cant be seen clearly, everything going to fast in a crash to see etc.

[NaN]

scheduler in vdrift?

No, there is no scheduler. At least I haven't seen one.

big sums can be disguised motion blur?

Motion blur is Joe's baby. Maybe he can elaborate on this.

[stan.distortion]

Scheduler for what?

So stuff that not as important as other stuff can be done every so many frames instead of every frame. I think there was something in the controls that did this. Either that or it did something weird when I was looking at the controls with timing, any kind of built in delays for keyboard controls where sluggish at lower framerates possibly, or could have read it somewhere else entirely, really not sure.
???
Hang on, I copied an pasted that?? Kind of obvious it can happen but its weird seeing it
Short on time at the mo but will try and get vdrift up to date and give it a go, sounds like some good stuff being done, thanks.
stan.

[NaN]

Hang on, I copied an pasted that?? Kind of obvious it can happen but its weird seeing it

Don't worry I was editing my post in that moment. 8)

[NaN]

built in delays for keyboard controls

No idea. Haven't looked into eventsystem yet.

[stan.distortion]

Last time I was looking at vdrift there where changes made to allow a table of values to be used for spring and damper rates. Did this work out ok? Did it have a negative or positive effect on system load?
I'm asking because I had a few thoughts on the tire calculations and they are getting some attention at the mo. Mainly this was to pre-calculate values for either points or bands around the tire and apply ware, temp, load etc. values to them to get current grip values based on how many of those points (or what amount of band) made up the contact patch.
The idea was to have the pacejka calculations done at startup to reduce processor load at the cost of memory and allow any amount of extra tweeking to be done with them at the cost of even more memory.
No idea how much load these calculations create or if this would be any faster, noting it down just in case its any use.
cheers

[stan.distortion]

How much would need changing to have both tables and formula for entries in the config?
Tried using a square root to simulate a basic damping curve before and wondering if it would be possible to use either tables or formula to say 'this value is a square root of suspension velocity' or a table of values in the config.
Thinking about it because of the tire calculations, I always thought something wasn't right with them and if 2 cars with different equations could be tested at the same time it would easier to compare them.
Didn't dig into the pacejka equations much but I'm guessing that tables for all the variables would result in a massive amount of data.....too much for a text file.......a binary file for tire data.......ok, down that road madness lies......I'll shut up now
cheers

[NaN]

square root to simulate a basic damping curve

Hey I had the same idea recently. To approximate a digressive damper. But haven't tested it. :lol:

[stan.distortion]

Made a huge difference, its what the damper section should be doing but I haven't even tried it yet.
If the cars are launching them selves off kerbs try changing the damper force line to use the square root of velocity instead just velocity, I'm still updating vdrift-data from svn, will give it a try then.
cheers

[stan.distortion]

Ok, tried the XS around rouen and its very nice
Putting this here not to clog up the other thread.
Feels very nice, tires feel wierd though, very sudden transition that feels like there is too much deadzone on the wheel. Deadzone is at zero and while cornering there is response through that area of the wheel input.

[NaN]

too much deadzone

I remember having read something about steering in the forum. But my focus has been cardynamics. Don't know where/how steering angle/deadzone is adjusted/calculated. :?

[stan.distortion]

at what suspension travel distance should there be bump stops on the XS?

[NaN]

Well, I used the overtravel value with a stiffness between 100000-500000. So using 0.05m of the travel should be enough I guess. But I have no idea what realistic values are.

[stan.distortion]

See some sections commented out with overtravel, is it used on trunk?

[NaN]

I found this: http://www.cardomain.com/ride/742393

It looks like they are quite progressive.