The online racing simulator
Searching in All forums
(948 results)
AndroidXP
S3 licensed
Sorry but that is a terrible translation
AndroidXP
S3 licensed
Quote from franky500 :i was planning on locking this.. but i think i will let it go to prove a point to the op.

Also sitting here in a pool of my own piss

^ Once the point has been proven, lock this thread and give out infractions for spamming image macros. Don't forget to sticky this thread for everyone to see.
AndroidXP
S3 licensed
Wenn du ein G25 hast, dann kannst du nur mit dem Schaltmodus schalten, den das Auto auch unterstützt. Sprich bei den normalen Straßenautos funktioniert die manuelle Schaltung, während man bei den meisten Rennwagen die sequentielle Schaltung bzw. die Schaltwippen verwenden muss.

PS: Das hier ist ein Englisches Forum
AndroidXP
S3 licensed
My condolences.




AndroidXP
S3 licensed
Ignoring the fact that threads like this are completely useless, I'd go with wet weather.

Tbh, I think night races would be a try-once-and-then-never-again gimmick, and I can't see the appeal of driving fast without seeing the track. Most people can't even handle the effects of wind, how do you think night races compare to that? (Though granted, that is an argument valid for both night and wet races.)

The only time where night races (implying a dynamic day-night cycle) would be cool is on the 24h race, but that's about it. Driving in rain, however, is something much more common to happen in real racing. Having to deal with changing conditions and pit strategy sounds, at least to me, much more interesting than setting the monitor brightness to max.
AndroidXP
S3 licensed
Quote from Krammeh :Try making an exception....

in the case command, make a default....

Post random advice that is useless without knowing the faulty code in question....
AndroidXP
S3 licensed
You should join the "I completely misunderstood Tristan's thread title club".
AndroidXP
S3 licensed
What do you consider a normal takeoff? Personally I find it rather hard to do a smooth low-rev takeoff in any car in LFS, probably because the low end torque modelling isn't that great and because I'm missing the buttfeel to tell me when the clutch is gripping. The clutch heating model is definitely not perfect, but not THAT bad either.
AndroidXP
S3 licensed
This is not true. When you want to buy a license, after you select the payment method, you will be redirected to the EULA screen with an "I agree" and "Cancel" button at the bottom.
Testing RAM (physically)
AndroidXP
S3 licensed
Stroke it gently.
AndroidXP
S3 licensed
Depends on the car and damage. On high grip FWD cars the yank when shifting can be quite noticeable, which is caused by the steering resistance being low due to the driven front wheels, but when you shift you momentarily don't accelerate, making the FFB much stronger for a split second. There can be a similar effect if the suspension is bent and the car pulls slightly into one direction, but this pull is reversed off throttle.

"Losing grip" is a too broad term to say whether there is anything to feel or not. Locking up the front wheels while cornering? Yes, definitely feelable. Going off road? Yes. Off-power or RWD understeer? No. On-power FWD understeer? Yep. Understeer transforming to oversteer? Yes, mostly.
AndroidXP
S3 licensed
^ Yep, crashes can affect the suspension geometry and by that also what you feel through the wheel. A head-on crash for example tends to make the steering very light, as the caster is reduced or even inverted. Of course this is not really realistic, because in a real car you wouldn't be able to drive any more after that kind of impact
AndroidXP
S3 licensed
Because the devs say so.
AndroidXP
S3 licensed
If luck is on his side he'll survive the massive blood loss and blood poisoning caused by a ruptured colon, but I'd wager this is actually the smaller problem. What baffles my mind is how the spike is not protruding out of his back, through his spine. Either it was stable enough to bend the spike without taking damage, or it's actually completely shredded inside. Yummy.
AndroidXP
S3 licensed
Can't follow you there, at school they don't teach Becky-math. I don't see how it is valid to put a digit after the recurrence, since this would stop the recurrence by definition. So if we allow this for whatever reason, then the difference would only be 0.0(0)1 if we were talking about 0.9(9)9, which we aren't.

Anyway, I'm out of here. That's like discussing if Pi and 3.141592...(insert Pi digits here) are the same thing. The former is simply the only way to write it fully
AndroidXP
S3 licensed
Quote from Woz :"Misinterpreting the meaning of the use of the "…" (ellipsis) in 0.999… accounts for some of the misunderstanding about its equality to 1. The use here is different from the usage in language or in 0.99…9, in which the ellipsis specifies that some finite portion is left unstated or otherwise omitted. When used to specify a recurring decimal, "…" means that some infinite portion is left unstated, which can only be interpreted as a number by using the mathematical concept of limits."

Let me repeat that VITAL part... "When used to specify a recurring decimal, "…" means that some infinite portion is left unstated, which can only be interpreted as a number by using the mathematical concept of limits."

You do realise that YOU are the one this paragraph talks about? Did you even understand what it says? For some reason you think there is a tiny difference between 1 and 0.9~ (to use your notation), which there is not. There would be one if 0.9~ was finite, which it isn't. There is no botching whatsoever going on, since this is the only way to write a number with a recurrence.


Now, I'll try to explain this by how I think about it, sorry if I don't make sense:

What do you think is inbetween 0.9~9 (some '9' digit of the recurrence) and 1? On a finite number, you could say, "ha, there is 0.9...91, 0.9...92 [...] 0.9...99." Note that the finite number stops at some point (only continuing with '0' if you want so), which gives you "room" to have a final digit. But on .9~ we are infinitely repeating the 9, there is simply no point where you ever cut off the line of 9s to make room for something (a difference) to exist between 0.9~ and 1. The difference between 0.9~ and 1 is 0.

*sigh* anyway...
AndroidXP
S3 licensed
Is this a very well disguised troll attempt?
AndroidXP
S3 licensed
AndroidXP
S3 licensed
You can't. You have to view the hotlap replay and in the lap before the lap you want to extract, hit ESC and click "Output lap data" (I think, can't remember exactly).
AndroidXP
S3 licensed
±0

I can think of countless things I'd rather have the devs work on other than... trucks.
AndroidXP
S3 licensed
No, 1/3 IS 0.333... recurring. There is no rounding error, people just can't wrap it around their head that 0.999... recurring and 1 are the same number. It is just ingrained in their heads that for each number there is only one way to write it (without using fractions), which is simply not true.

E: Beaten, twice
AndroidXP
S3 licensed
Quote from Jakg :but wouldn't of stopped
[...]
but the train would of carried

:gnasher:
AndroidXP
S3 licensed
It's very logical and simple, but you opened a can of worms here
FGED GREDG RDFGDR GSFDG