The small collisions don't have to be car rockets to end bad especially at SO. Sometimes a small scrape ends up being a heavy shunt, though the cars barely bumped each other. I my experience on LFS, while drifting, the cars rarely gets as close as while racing. Sometimes in a heated battle my opponent or I will attempt to maintain contact throughout at bend, and sometimes it doesn't end bad, but more often then not it does.
This is all theory, and forbin is right, that the collisions cannot be over simplified if we want something remotely realistic; however, as stated by Keling, the current car "car rocket" model is no where near realistic either.
And so, like the rest of these suggestions, the decision is up to Scavier whether they would consider making these changes. I just wanted to get the thought out there even if it has already been thought about. At least the re-mentioning of the idea might insight consideration for a temporary fix.
Of course the age old suggestion in all online racing games is, "Fix the lag collisions!" However, I want to propose an idea that might work, but I don't have any clue as to the feasibility of the actual programing of said idea.
The Problem: Cars shoot off from impossible collisions when nudged fairly hard while online.
A Solution: Void extremely high collision force values, then recalculate based on the closing speed at or near the instant before contact.
As the collision detection stands now, there is already a delay from the moment of impact to the resulting reaction; which, I think, can only be fixed with the brute force method, high CPU clock.
What is the feasibility of this solution, and could the calculation delay be a reasonably short time? Considering the net code makes position predictions, would calculating the collision ahead of time be possible?
lol "April fools! It's real!" everybody would automaticaly jump to the conclusion its an april fools joke so it's not real then bam, that punchline.
Ye would have been funny, oh the missed opportunities in life.
On T:
I didn't know the other track sections were drive-able while not being the primary track selected. I thought the car would fall to the underworld if it got passed the barriers.
If you consider racing a hobby, then participating in one race every 2.7 days is actually quite a lot of racing. LFS being a sim on a home PC is just a convenience, so racing much more than one race per 2.7 days is rather obsessive. Maybe obsessiveness is why this community goes apeshit over LFS development. Although I am one to be counted as obsessive over LFS.
Edit: Noscript is better, it can block partner sites while still allowing the main site; whereas if the main site, in Chrome, is allowed then all other sites are allowed.
Example: On gamerailers.com, with noscript, I can watch videos without having to watch the 30 sec ad before the video. This is not the case for Chrome. So back to Suckfox it is.
I agree Firefox sucks, but It has the holy of all addons, "noscript". Unless someone, maybe you dust, can enlighten me to similar features on other browsers, I will use sucky Firefox.