Never really thought about it, but that's actually surprising, as it means LFS really does store passwords in clear text, or at least in a form that allows decryption (tbh, I think the latter).
The problem is twofold; First, if your mail account is compromised the hacker can gain access to the account without you noticing that something is amiss (he just deletes the password retrieval mail and you'll never know). On a password reset / reassign your account might be compromised or stolen, but at least you know that happened because you can't login anymore, which should make any sensible person change all his passwords immediately to limit damage. Second, by knowing the cleartext password you can potentially hack into other accounts of the victim that might be linked to a different inaccessible mail account (or where a "password forgotten" would reset the password), because many people use the same or similar passwords for various sites.
Other than that, storing the passwords in cleartext could cause all of the above to happen if the LFS database is breached somehow, so not only the LFS accounts would be affected, but potentially much more important / painful-to-deal-with places too. Though as I said above, I really don't think LFS does that but uses a decryptable format instead. Would be kinda ironic if the creators of such otherwise good software committed such a security faux pas.
However, what I don't understand is why the passwords are even decryptable. They should just use a good hashing algorithm and compare the password input to the hash instead, because even the LFS devs should have no business in actually knowing my password. The only "benefit" from decrypting the passwords is so that you can send it in the password retrieval mail, but as we know that's not a tangible benefit for anyone at all.
Pff, look at what a noob softcore sim this is becoming!
Which colour is better, red or green? (Bonus points if asked by a colour-blind person.)
My point is that there is no answer to that, because a physics engine has many different aspects, each of which can be simulated with different levels of accuracy and correctness.
I think it cannot legally be disallowed, but it is strongly discouraged by the devs. The problem is actually not regarding the selling or the seller, but the buyer, because the used license doesn't only include the content as a fresh license would, but also the name, reputation and any potential bans (potentially even a system-wide online ban!), too. In the worst case the seller could even at some point decide to want his license back and get the license password reset if he still has his confirmation of purchase.
In the end the used-license buyer is the one who bears all the risk and if anything happens then he will be the loser, because the devs have explicitly stated that they won't even try to start untangling the mess that results of selling or giving away a license.
Heh, you know what was funny about the "learning" the AI had previously? It wasn't actually learning, but just let some algorithms run every time it crossed the finish line to "optimize" the whole driving line. Whether the new driving line actually turned out to be any faster wasn't even checked afterwards 
This was also the reason that on some tracks the line was gradually "optimized" into the grass that made the AI cars spin every lap without fail. Learning indeed.
The new AI is much better in terms of speed and competitiveness, but is much less random regarding the driving line if no obstacles are on the track. However that is kinda offset by the much more aggressive overtaking moves, which (hilariously) are sometimes so aggressive and quick that the overtaking AI drivers spin themselves out from the sudden movement.
More competent AI drivers would be a very nice thing and interesting to watch, but I fear accomplishing just that is actually quite complex and time-consuming, so Scawen probably won't really get to that before doing actually online-racing relevant stuff (optimistically put).
Figuring out a system to make AI behaviour scriptable (= user editable) would be absolutely fascinating, though. I can already imagine the leagues consisting solely of user-created AI.
This was also the reason that on some tracks the line was gradually "optimized" into the grass that made the AI cars spin every lap without fail. Learning indeed.
The new AI is much better in terms of speed and competitiveness, but is much less random regarding the driving line if no obstacles are on the track. However that is kinda offset by the much more aggressive overtaking moves, which (hilariously) are sometimes so aggressive and quick that the overtaking AI drivers spin themselves out from the sudden movement.
More competent AI drivers would be a very nice thing and interesting to watch, but I fear accomplishing just that is actually quite complex and time-consuming, so Scawen probably won't really get to that before doing actually online-racing relevant stuff (optimistically put).
Figuring out a system to make AI behaviour scriptable (= user editable) would be absolutely fascinating, though. I can already imagine the leagues consisting solely of user-created AI.
You don't necessarily have to see the other cars at all times to know where they are. As you gain experience and improve your race craft you'll learn to anticipate the movements of your opponents and over time get a much better situational awareness and feel for your surroundings.
Keeping the other cars in mind and extrapolating their paths without having them in your vision is a major factor in good race craft IMO - you actually start thinking about what your opponent is most likely going to do or what he can do, instead of just reacting to what happens on the screen.
That said of course you don't drive completely blind; regularly checking the mirrors and using the look features is a must if you don't want to be a hazard on track. Having your opponents more "mind mapped" will help you reduce the amount of mirror checking and looking you have to do, though, which is good since these actions can be rather irritating and compromise your consistency/concentration.
As for the camera view, I use the bog standard cockpit view with an 78° fov angle.
Keeping the other cars in mind and extrapolating their paths without having them in your vision is a major factor in good race craft IMO - you actually start thinking about what your opponent is most likely going to do or what he can do, instead of just reacting to what happens on the screen.
That said of course you don't drive completely blind; regularly checking the mirrors and using the look features is a must if you don't want to be a hazard on track. Having your opponents more "mind mapped" will help you reduce the amount of mirror checking and looking you have to do, though, which is good since these actions can be rather irritating and compromise your consistency/concentration.
As for the camera view, I use the bog standard cockpit view with an 78° fov angle.
You can use scripting to have other keys (or wheel buttons) emulate the key presses to 7, 8, 9 or 0, but there is no way to directly rebind those keys from inside the game.
Scripting in general: http://en.lfsmanual.net/wiki/Script_Guide
Example script for wheel controlled indicator selection: http://en.lfsmanual.net/wiki/Script_Guide#Indicator_Control
Scripting in general: http://en.lfsmanual.net/wiki/Script_Guide
Example script for wheel controlled indicator selection: http://en.lfsmanual.net/wiki/Script_Guide#Indicator_Control
http://en.lfsmanual.net/wiki/Keys#Car_Controls
7 - Left indicator
8 - Right indicator
9 - Hazard lights
0 - Indicators off
7 - Left indicator
8 - Right indicator
9 - Hazard lights
0 - Indicators off
They aren't square. At least not more square than floating point precision permits. The sections just hold the information, but have nothing to do with the collision between tyre and asphalt itself.
E: Or was that meant as a jab at "hurr, nothing is analogue"?
E: Or was that meant as a jab at "hurr, nothing is analogue"?
0 1 0 1 0 1 0 1 0 1 = Digital
1 10 11 100 101 110 111 1000 1001 1010 = Analog
?LFS doesn't simulate the oil pressure at all - the current oil pressure gauge is just a copy of the tachometer. Sure one is linked to the other in reality, but it is not a 1:1 link. It's just there for fluff at the moment, and simply displaying the RPM again is something that looks vaguely correct without actually taking more than a few minutes development time to implement.
Of course the LEDs don't work with LFS, as Scawen hasn't coded in that feature yet, nor has anyone written a tool that could accomplish the same via OutGauge.
Personally I wouldn't count on Scawen implementing that into LFS directly any time soon.
Personally I wouldn't count on Scawen implementing that into LFS directly any time soon.
I am Mecha Mom, the bringer of the manchild, destined to break the Whitehouse.
Or
I am Tiny Maximus, the evil, evil basementdweller, destined to annihilate all and pillage everything.
Oh yeaaah
Or
I am Tiny Maximus, the evil, evil basementdweller, destined to annihilate all and pillage everything.
Oh yeaaah
Looking at the list of things still to do Scawen posted... maybe Christmas next year.
Make sure the G25 is plugged in when booting your PC. That way it does its auto-calibration routine and personally I never have to recalibrate my G25 when starting up LFS (as seldom as that is).
If the wheel in LFS is not calibrated on startup, for the most part all that is necessary is pressing all the pedals once and rotating the wheel fully left & right (can be done anywhere in LFS, even while on the track), without any further actions needed.
If your calibration itself (axis assignment, etc.) does not persist, then make sure your whole LFS folder has write protection disabled and that the account you're using to play LFS has write rights to the LFS folder and all subfolders/files.
If the wheel in LFS is not calibrated on startup, for the most part all that is necessary is pressing all the pedals once and rotating the wheel fully left & right (can be done anywhere in LFS, even while on the track), without any further actions needed.
If your calibration itself (axis assignment, etc.) does not persist, then make sure your whole LFS folder has write protection disabled and that the account you're using to play LFS has write rights to the LFS folder and all subfolders/files.
I'm completely blown away by the amount of effort you put into your post. If only all beggars were this eloquent!
:snowman:
:snowman:
Actually, the most likely reason is that the tyre load sensitivity in LFS is flawed which is which probably makes locked diffs work better than they should. In any way, we'll just have to see what the new tyre physics patch that will come out at some point in the future improves, and if it finally rids us of this locked diff nonsense.
How did you get that idea? To me it simply looks like sending hardware commands to the wheel.
Here, that's how it looks with C#/SlimDX:
Now if I had a G27 I might've played around with that a little, but alas, I don't
You cannot compile single files, only projects.
A project [.csproj] is a "container" (it doesn't actually contain files, it just points to them) for the C# source files [.cs] and all other files that belong to your project (images, etc.). It also has a certain output type, either Windows/Console Application [.exe] or Class Library [.dll], which defines what the result of a successful compilation is.
A solution [.sln] is merely a "container" pointing to different projects, so that related projects can be grouped together.
So what you want to do is, open either the solution or project, then locate the file you want to modify in the Solution Explorer (should be a tab on the right side, alternatively View > Solution Explorer). Open it and modify whatever you like, unless it already has the modifications, of course. Then go to the Build menu and select Build Solution (or equivalent, whatever is available. I think F6 is the shortcut). This will generate a new output in the "Debug" or "Release" subfolder of the project. Navigate there with normal Explorer, then replace whatever file the Lapper application is (I guess some .exe?) in the directory you installed Lapper to and try out your changes. Don't forget to back up the original .exe though, just in case you screw up.
A project [.csproj] is a "container" (it doesn't actually contain files, it just points to them) for the C# source files [.cs] and all other files that belong to your project (images, etc.). It also has a certain output type, either Windows/Console Application [.exe] or Class Library [.dll], which defines what the result of a successful compilation is.
A solution [.sln] is merely a "container" pointing to different projects, so that related projects can be grouped together.
So what you want to do is, open either the solution or project, then locate the file you want to modify in the Solution Explorer (should be a tab on the right side, alternatively View > Solution Explorer). Open it and modify whatever you like, unless it already has the modifications, of course. Then go to the Build menu and select Build Solution (or equivalent, whatever is available. I think F6 is the shortcut). This will generate a new output in the "Debug" or "Release" subfolder of the project. Navigate there with normal Explorer, then replace whatever file the Lapper application is (I guess some .exe?) in the directory you installed Lapper to and try out your changes. Don't forget to back up the original .exe though, just in case you screw up.
Well, I guess something this "extensive" changelist
must've broken it just for your PC
must've broken it just for your PC
Too bad he misplaced it three days after, hence "had"
Don't worry, that's just because you're a LFS forum moderator
Then maybe it's your memory that gets corrupted. Sorry but Z28 works for pretty much everyone else, and the screenshots you posted show the telltale signs of vertex data corruption usually caused by GFX card overheating. I had the same happen to me back when I still had the stock cooler for my 6600GT.
Also 18°C inside your computer? Must be really cold in your room. Or the temp sensors are broken.
Also 18°C inside your computer? Must be really cold in your room. Or the temp sensors are broken.
Has nothing to do with Z28 - that's your graphics card overheating. Try dusting it off and make sure your PC gets enough air circulation going to keep it from getting too hot.
Ahh yes, the good old times of the Clean Rammers Club. How I miss the times where everyone followed the proper ramming regulations
FGED GREDG RDFGDR GSFDG