Well, there's a couple of reasons why I usually ask someone else: either I ask someone I know because I use to like the sets he uses, or I ask someone I just saw doing something I know I couldn't do with my current set (like riding a specific kerb, or cornering at a speed I couldn't).
If you're trying to use LFSRelax, extract the folder named bin and give it a better name. Mine is in LFS's folder and is named LFSRelax.
Then launch LFSRelax.exe, launch LFS, press T and type "/insim=29999" (without the quotes). I'm not 100% sure it's the correct syntax (as I use to launch LFS from a batch file) but I hope someone will correct me if it's wrong.
You can enable/disable the various functions by editing LFSRelax.cfg. For example replacing "EnableTSView = true" with "EnableTSView = false" would disable the TeamSpeak display feature.
If you need more help with LFSRelax, I'd suggest you to post in its thread.
Whatever the reason you write like you do, don't be surprised if you don't get the answers you expect. I've read your last post four times and I couldn't figure out half of what you're trying to say. If you can't be arsed writing in an understandable way (whatever it takes), don't be surprised if no one bothers trying to decipher your fricking code.
Update: oh, BTW insulting people is not one of the best ways to get help either.
A proper racing school would have to be a whole sim of its own, IMO. I think a simple one like you suggested wouldn't really teach you racing, it would just help you learn the specific track you're on. You mention braking points, apex speed, etc, but you can already learn these by spectating a fast racer online or watching a hotlap replay.
Alternatively you can also learn to figure these out yourself, like it is done IRL. All you need to know is that an early turn-in leads to an early apex, which in turn leads to running wide at track-out. So start with a bit early braking points and late turn-ins, so you have plenty of tarmac left at track-out, and progressively bring your braking points deeper and your turn-in points earlier, until you find the right combination for each corner.
You may think it's a waste of time to do this when you could be told what to do, but you'd miss an important thing such a simplistic racing school wouldn't teach you: these braking/turn-in/apex/track-out points are only valid when you're alone on track. In a race they'll often vary because of the cars around you. For example if you wait for your optimal braking point at T1 in the first lap, you'll wreck half the cars ahead of you because you should have started braking when the leader reached the braking point. Similarly, if you experienced by yourself the results of early apexing, you'll know what to expect and how to react. But if you've only learned to always brake and turn-in at the same point, when a car spinning ahead of you will force you to turn-in earlier, you'll crash.
Great, I'm glad to see you guys collaborating, Gail-Luron and riskredruM!
I have a few bug reports about the new InGame feature:
1. The first split always shows your last split as the best one (at least it's the case when watching mpr replays, as I didn't try it online yet). In other words, both Split1 times are always identical.
2. The last split boxes give the best last split, and your lap time. I'd expect the best last split and my most recent last split.
In both cases, see the attached screenshot.
3. If you press SHIFT+B to hide InGame's info, it works as expected. But if you press it again, it no longer works and InGame's info stays hidden.
Sorry to disagree with you, Gunn, but I like the subforums idea, personally. I don't think it would add clutter, because there are several of these subforum that I'd never visit (like track or car requests). So for me it would actually reduce the clutter.
It would probably be easy and not so time consuming for the mods to move to the right subforum the messages that have been posted at the first level. And I'm sure that people posting in the wrong place would be flamed often enough to make them think twice about it the next time. And that's on the assumption that you cannot make it impossible to post at the first level (which I'm sure you could).
Some people like posting their ideas, even if they already have been discussed to death, and others like to flame the former ones. Fine, let them do it. I think there's no way to prevent it anyway. But make it easy for those who aren't interested to ignore it.
IMO the search feature could also be improved by restricting the basic search to the current subforum, and by selecting automatically the subforum you came from in the advanced search screen instead of the current "Search All Open Forums". Without this change, I think the advanced search would be the only place where such subforums would add clutter.
I think you can make the view to change automatically. For example if you want to use the chase view with the cars that by default use paddles to change gears, open the file .../LFS/data/scripts/paddles.lfs and add "/view fol" at the bottom of it (without the quotes). The view should then switch each time the paddles script runs, which happens when you get into the car.
There's an option somewhere to replace the FPS with the current time. I can't check right now because I'm back in Mac OS, but I think it's in the Misc screen.
Update: actually, the one in my screenshots is displayed while viewing replays. This is new in patch X, but I didn't realize that it was displayed only when the time is displayed instead of the FPS. I thought everyone was seeing it. When driving, there's a simple clock that doesn't show the date. This one isn't new, though.
For the records (and those who may find this thread because they have the same problem), here's what I figured out:
For some reason (probably drivers), the fan of my graphics card kept running at 32 % max, whatever the card's temperature. It seems that the artifacts start appearing when it reaches 75 or 80°C. So I'm now using ATITool to override the fan speed control, so the temperature doesn't exceed 70°C. And I'm no longer seeing any artifacts.
That was my point, mate. I'm sure that if you tried to make sense of it, instead of just backing off or staring blankly at the screen, you'd figure it out. Glad you got it sorted out anyway.
I'd like the ability to display extra information, like InGame does, and being able to show/hide this information via hotkey(s) (I'd love InGame if it wasn't that buggy, but unfortunately it looks like it's been dropped). More specifically, I'd like to be able to display:
- Timesheets (like LFS', but persistent, because LFS' disappear too soon in qualification and is hidden when you display tyres temperature during races).
- Gaps with the leader, and the cars ahead and behind (with driver names).
- Splits: best, personal best, last.
- Fuel: percentage of tank, percentage per lap, number of laps in tank (red when < 2).
See, this isn't too much. And that should give you a nice distraction when you take a break from working on LFSStats and LFSLapper.
It's not that hard, really. Did you even try? Everything's commented and if you can read you should be able to figure it out. For exemple to disable a given function, you just have to replace true with false in one place. So don't decide that you won't be able to do it before trying, and if you have specific questions when you do try, we'll be happy to answer them.
@ Gai-Luron: a couple of notes:
- I couldn't get it to load correctly when I had an admin password in LFS (and of course the matching password in the cfg file). InSim kept complaining at launch that the passwords didn't match. I had to remove the password from both places to get it to work. I've experienced the same problem with several other InSim apps, so I don't know if the bug is in those apps, in LFS, or in my config.
- It'd be cool to have a hotkey to hide all the buttons. For example when I'm in the lobby, each time someone talks in TeamSpeak the button showing their name appears (as expected) which leads the grid and the connections list to be hidden. Being able to temporarily turn the buttons display off would be very handy, here.
- Are you considering adding other functions to LFSRelax? I have some ideas.
I forgot to mention that you can already do that with ALT+FKeys, for example (but not with numpad keys).
Go to Options > Game and define message hotkeys set to "/run fc_runCam1", "/run fc_runCam2", "/run fc_runCam3", etc (without the quotes). Note that the prev/next hotkeys will keep working as expected. So for example if you jump directly from CAM 1 to CAM 4 and press the prev hotkey, you'll get CAM 3.
And while you're there, you may also want to define hotkey to access the other views directly, by setting hotkeys to "/view heli", "/view fol" (chase view), "/view cam" (track cams), "/view driver", or "/view custom" (FlipCams).
BTW, I'd love to see videos that use FlipCams, so when you have something to show, please feel free to post a link here.
Thanks for your report and follow-up, Flinty. There was a bug in the installer preventing to use the ALT+F11/ALT+F12 hotkeys that is now fixed. I just released the 1.0.1 where the only change is this fix to the installer. You can download the new version from the top message in this thread.
Those who already installed FlipCams 1.0 and didn't want to use the ALT+F11/ALT+F12 hotkeys don't need to upgrade it.
@BruTaLysT & JasonJ: Thanks for the feedback, guys. Lots of good ideas, here, even if unfortunately some might not be possible to implement (Jason is right about the num pad key not being usable to trigger scripts).
@Flinty: This is odd. When you launch LFS, do you see the message saying "FlipCams: CAM 1"? What if you run the installer again over your current install and choose ALT+F11/ALT+F12? (your existing cams will be preserved)
Some people asked me questions on how to use FlipCams, during online races, which to be honest isn't the best occasion. So here's a little "Getting Started" that I hope will answer those questions.
The installer creates the new custom views by duplicating four times the existing one for each car. So the first thing you'll have to do is to edit those new views to your liking.
1. Go on track in single player and press v until the custom view is displayed. It's the one after the cockpit view that by default shows only the wheels. Let's say this wheels-only view is displayed and you want to keep it.
2. Press FlipCams' next camera hotkey (CTRL+F12 by default or whatever you chose in the installer). You'll see "FlipCams: CAM 2" displayed in the chat area, but the view itself will not change (more exactly it will change, but since they're all identical at that point you won't see a difference). Press SHIFT-O, click on VIEW, then on CUSTOM VIEW.
3. Now edit the custom view as you want. You can make the car's body visible, set the mirrors and dashboard to "real", move the camera, change the FOV, etc. When you're done, click OK to exit the options.
4. At that point, CAM 1 and CAM 2 are defined. Repeat the steps 2 and 3 until you've customized all the cameras, and you're done.
You'll have to do this for each car, though.
I hope this helps! Feel free to post any question you may have here, but please don't be offended if I don't reply to questions asked during races. Most of the time I ignore the chats while I'm driving. Or at least I try.
I've done what you suggested and that works perfectly in most cases. However there's one occasion when it doesn't work: when a session (like a race) is restarted. Then, since I'm already in the car, those scripts aren't triggered.
The session starts event I suggested would be fired, in this case. So I still think it would be useful. FWIW.
Hmm... I have no inside information, but the way I guess skidmarks work is that each is saved on its own. So if two skidmarks are partially overlapping but weren't made at the same time, they wouldn't be saved as one large skidmark but still as two of them. Therefore, if tens of skidmarks were on the top of each others, each would still have to be drawn on its own. And soon or later LFS would use all of your machine's resources drawing skidmarks whose most wouldn't even be visible because they'd be hidden under others.
I don't see the point either. I would if LFS script had flow control, like conditionals, loops, and so on, but for now the only thing it would do is making scripts unreadable to most people, which frankly is not the best way to promote LFS scripting.