Messages

Seven

My understanding is that grip can be seen as analogous to friction in physics. You have two friction coefficients: a static one and a dynamic one. This results in a very simple linear equation that will just switch coefficients when the maxium static force is applied instead of having to deal with an elaborate hybrid formula.

When the force is less than the maximum static force, you have a friction force opposite that cancels out with it. This maximum force is proportional to the modulo of the normal, which is equal to the car weight if the car is standing on the ground, just in the opposite direction. The proportion between them is called "static friction coefficient". This means that two cars with the same tyres (since it's the tyres that make contact with the ground) will be able to maintain grip up to different maximum forces if they have different weights. In other words, the type of tyre is an integral part of the grip if we see it this way.

Now, there are a couple of things here that general classical mechanics are not taking into account. One is that, at sufficiently high speeds, the air becomes significant and the downforce you mention adds to the normal (in the opposite direction), which increases the grip. The other thing is that, if a car is heavier, it not only gravitates more (weighs more), but also has a greater inertia, so it'll be harder to keep it on track on a curve. In other words, the grip will be reduced. This is a centrifugal, ficticious force, so it makes sense that is left out of the general rule, but it's a lot simpler to calculate it as a force anyway.

In short, without an atmosphere and with a car that's going negligibly fast in comparison to it's weight (we're talking spherical cows here), it's all really simple

It really looks great. I agree that it's an amazing design

If this is just copying the remote data from the player into the local opponent, then with a couple of touches to Stunts code, it should be possible to make it so you're not required to wait for the other one to move

Dark

Oh!  The car must have been desperately asking for more!

Scotland

Dandruff 

Uhm... maybe that's legal, I don't know, but I don't feel it to be correct. I mean, if I don't provide the source myself, then whatever site I point to might go down or remove it or change it and then I'd be providing an incomplete source.

Right. When I am the user and I download software, I rarely download the source unless I want to compile it for some reason or examine the code. Most of the free software code around today is written in horrible languages such as java, ha, ha or using lots of OOP, so studying the source normally isn't of any use to me. Then it's good to have an option like your #1.

Of course, if I split it, then people have to be aware that they can't redistribute package #1 without also putting the other packages available at the same location.

I've heard about Allegro and have been browsing its site many times, but never actually worked with it. If it can be statically compiled and doesn't get too big, it could work for me. Since the old version supports DOS, I reckon it does fit in that category.

I have a problem with including third party software in my work and it has to do with licensing. In part, it's just because of something I don't know very well, but it's also a matter of discomfort. I'll explain...

I usually make my programs GPLv3 unless I'm making them only for myself, in which case I don't apply a license (all rights reserved). Of course, this means that I can only use libraries that are compatible with the GPLv3. I think Allegro is. Now, the thing is, when I later distribute my program, I have to make the source available, but then this means I have to also make the library source available, since it's part of the program code now. Am I correct?

Including all the source is very untidy and complicates the compiling for whoever downloads the source, but if I include a precompiled version of the library, the package gets even bigger. So I don't know what's the best solution for this. To make matters worse, if the library has dependencies, now I have to include the source code of those dependencies as well. Each dependency will be written in a different style and have its compilation parameters, etc.

Now say I'm wrong and I can just leave out the source code that I didn't make, then this is what brings me the discomfort: I know I wouldn't really be providing the user with all they need to compile the program, so I feel it's cheating.

So... that's my issue with third party libraries, ha, ha. What would you do about this?  How would you handle it?

Ah!  I love that song. I play it in the piano frequently....
So...

Piano

Yep. It sounds fair as it is

Alright. I've posted with all five cars this time! :p  Later, I'll probably update some of my laps, but starting from now, I've ensured my full post 

(Sharon) Stone