- In one of the replays I watched, a drivers crashed after a few laps, pressed shift+p then return, so his car was in a garage. Then he stayed there without moving for 5 or 10 minutes (I suspect he used tab to spectate other cars or went AFK). But LFS Race Viewer stayed focused on his car, and came back to it as soon as I switched manually to another car. It's only when he spectated that LRV started showing other cars again.
- Maybe LRV could use the cars position (or use it more) when looking for a battle to show. Because in one replay, two guys near the back of the grid that weren't particularly fast nor battling stayed close to each other for a lot of laps, and LRV was showing them most of the time.
- How does it choose which car to watch at the start? It's often one near the back of the grid. It would seem more logical to me to watch the pole man until something "catches LRV's attention".
And it would be great to have a hotkey to enable/disable LRV from within LFS, so during a replay you could switch between LRV and manual control, and back.
Nah, the guys who spend their time doing that kind of shit only do it to get some recognition. Whether they want a security admin job or they want to shine, they wouldn't want their "exploits" to be attributed to someone else.
Basically, DNS servers translate the domain name in the urls you request (like www.lfsforum.net) into the server's IP address (like 208.69.32.139). This is done by looking up the domain name in a huge database, but since there are DNS servers all around the world (most ISPs have their own to speed up accesses) these servers have to keep their copy of that database up-to-date. They do it automatically, by sharing the changes done to their copy with the other DNS servers around them. So when a domain name is created, for example, it will take a few days for this change to propagate to all the DNS servers around the world.
It may also happen that some entries in a DNS server's database somewhere get corrupted, or changed by mistake, and this erroneous data will propagate too, causing the kind of trouble that many of us have experienced in the last couple of weeks.
OpenDns.com provides the same service, but apparently they maintain their own copy of the domain names database, where the errors that made lfs servers unreachable didn't propagate. So if this is your case too, switching from using your ISP's DNS server to OpenDns' would fix the problem. See their site for detailed how to's.
I haven't tried the Windows version, but the Mac version has some unique features, like dragging the tabs around to reorder them or dragging one tab out of the tabs bar to create a new window. It also allows you to resize dynamically text boxes in any form (textareas, not text inputs), to drop an icon onto a file input element (instead of clicking on Browse and selecting the file), etc. I would expect the Windows version to have these features too.
To the original poster: File the bug to Apple, please. You're using a beta version and the reason why this beta has been released was to find and fix such bugs. It wouldn't take you much longer to report it to Apple than it did to post about it here, and at least it would be useful (I believe there's even a "Report Bugs To Apple" command in one of the menus).
It all depends on how close you are to the car's limits, but basically, the only way to change your line through a corner is to loose speed.
The fastest way around a corner is always the largest possible radius. If your turn-in, apex and track-out point are correct, the radius will be greater than if you just followed the edge of the track on the outside (by about 50% for a 90° corner on a reasonably wide racetrack), and it will be much greater than if you followed it on the inside (about 90° for the same corner!). So when possible, use as much track as you can to increase this radius (by being as close as possible to the outside at turn-in and track-out, and to the inside at the apex).
According to geometry, if your turn-in point is too early, you'll apex too early, and you'll run wide at track-out (unless you tighten your radius, which, if you're close to the limit, can only be done by slowing down). If your turn-in is too late, you'll apex later, and you'll have plenty of room left on the outside at track-out (but you'll be slower). Therefore, the safe way to figure out your line through a corner is to start with a late turn-in, that will guaranty you to stay on the tarmac at track-out, and progressively move your turn-in earlier until you find the point that allows the highest speed around the corner.
I'm not sure it can be unnoticed because the car is in neutral and produces no engine sound (at least that was the case the only time I saw someone using it).
F1's have a reverse gear, but AFAIK they're not allowed (or weren't, at least) to use it on the track or in the pits, except in case of emergency. Mansel was black flagged (in 89) because he used it in the pits (and then he didn't see the black flag and kept going).
Last edited by FL!P, .
Reason : Corrected the year when it happened
Yes, I'm compiling ideas and thoughts about the next version. But I have no idea when I'll have time to really work on it, because the only time I could spare at the moment would have to be taken from racing. So there will be a new version, but don't expect it in the next few weeks.
Found it! In LFSRelax.cfg, search for "ViewCollision = true" and replace it with "ViewCollision = false". It's a debug feature that was probably intended to be false by default. I didn't see those coordinates because I migrated my cfg file from the previous version.
I've never seen those numbers, so I may be wrong, but try this:
1. open LFSRelax.cfg
2. scroll down to the bottom of the file
3. look for "AccelerationPrivateMessage = ^3{AccelerationTime}^7 ..." (that line is actually longer)
4. insert '#' in front of this line (without the quotes).
5. save and close the file, then relaunch LFSRelax, LFS, and try again.
Hmm, the script runs probably before LFS switches from the garage/lobby to the track, then. So the view command is triggered too early (either at a point where it cannot work, or just before LFS sets the view on its own). If this is the case, I'm afraid that changing the view from the sequential script won't be possible before Scawen implements some wait command.
Edit: Isn't it possible to make a satisfying chase cam in custom view? In this case, you could set the custom view to be the default one, and LFS would load it each time you get into the car.
Weird. What happens if you put "/view custom" instead?
You could also try putting "/press v" twice in the script.
I know you can run another script, from sequential.lfs, so if it doesn't run the view command for some reason, try creating a new script, put "/view fol" in it, and call that script from sequential.lfs, using "/run <yourScriptName>".
There's an option that allows to change the steering linearity, but I forgot its name. I'm sure someone else will chime in with the answer.