Congrats, AchimPL! Enjoy LFS S2, you sure deserve it! 
12 and a half hours left or so...
Well I sure am holding thumbs for AchimPL, that's one very deserving demo racer right there.
EDIT: Waaait, it's not from the time of Jeff's post, so it was actually 9hr 20min... and now it's 8hr 20min
Well I sure am holding thumbs for AchimPL, that's one very deserving demo racer right there.
EDIT: Waaait, it's not from the time of Jeff's post, so it was actually 9hr 20min... and now it's 8hr 20min
Last edited by axus, .
Wel done lol can i use it its so gud.
On a more serious note, I agree with Roadie, who cares?
On a more serious note, I agree with Roadie, who cares?
What if you have passengers? And are you taking marshals into account?
Jeff spoke to me over MSN about this a few days ago. It's a sweet idea, good going!
High res car skins are 1024x1024, high res helmet skins are 512x512. It's already possible to only use your high res skin "credits" for car skins only.
I agree with Android and geeman. That's not how things work in LFS.
It's essentially not much different than the SMS service though. The thing is, not everyone can make use of this feature and not everyone wants it so it'd be unfair splitting the charge between everyone by increasing the license cost. At the same time, it's a great feature to have because some people will find it useful. This isn't content, or anything that increases the functionality of LFS, just a nicety.
Something that would be really useful is to combine RAF analysis to test balance in a certain corner. Often we end up with setups which are incredible around most corners but one or two corners, because of their camber, bumps etc. are messy. It would be really helpful to take the data from an RAF where we've done a decent job around that corner despite the difficulties due to setup and analyse the understeer/oversteer due to damping etc. from that RAF while limiting the time for just that corner.
The more complicated option would be to optimise the setup using a generic algorithm for that corner, from the track mesh, following a line as close as possible to that in a specific RAF. That, in itself is going to probably take a month to research, plan and code though. Still, great work so far.
The more complicated option would be to optimise the setup using a generic algorithm for that corner, from the track mesh, following a line as close as possible to that in a specific RAF. That, in itself is going to probably take a month to research, plan and code though.
Still, great work so far.frankwer, please elaborate. Even if the BF1's physics isn't finished (ie. not all aspects of physics relating to it are simulated), nothing was fudged thus far. That's what Niels is getting at.
As for the inertias, the matrix has this form:
I assume rFactor just uses I_xx, I_yy and I_zz, you'll have to figure out which is which in LFS.
As for the inertias, the matrix has this form:
[ I_xx, -I_xy, -I_xz ]
[ -I_yx, I_yy, -I_yz ]
[ -I_zx, -I_zy, I_zz ]I assume rFactor just uses I_xx, I_yy and I_zz, you'll have to figure out which is which in LFS.
Damn BMW pitcrew. Good job by Kubica though - he really needed to get a good race in.
Amazing job by Hamilton again, who has now taken the F1 driver's championship. (And he out-classed Alonso in front of his home crowd.)
Amazing job by Hamilton again, who has now taken the F1 driver's championship. (And he out-classed Alonso in front of his home crowd.)
Because you want it. You know you do. Stop living in denial.
Just the ones you download from now on - if you delete all your 512x skins, next time you see them online, they'll get downloaded again in 1024x though.
2000 skins is probably enough for half a year of racing...
for that difference, I think that's worth it.As for skin compression, that's an option in the graphics options.
I would (mostly to support the devs - not that I'm that concerned about the look of the cars I'm racing because my PC isn't that great to begin with) but bandwidth restrictions and a weak PC are stopping me. That said, I think it's a great feature, thumbs up to the devs for implementing it.
It automatically calibrates.
I guess the driver just forgets to run the calibration routine for some reason, when it's on separate axes - it works fine on combined so it must be a software bug.I don't think it would be that complicated to have a special character indicate the shortcut in a translation - though it's more coding for Scawen and he's already said he'd like to get Patch X out soon - so if it's easier, the shortcut keys could be hidden from a misc option.
Thanks for the update!
Wouldn't it be better to just have a letter underlined in each of the options and have these available at a single key-press from the menu so its as compact as before? The shortcuts that people would use from outside the menu can be looked up in controls anyway.
Wouldn't it be better to just have a letter underlined in each of the options and have these available at a single key-press from the menu so its as compact as before? The shortcuts that people would use from outside the menu can be looked up in controls anyway.
Axes are stuck like this in LFS, no matter what I do:
Annoying problem with a MOMO (Racing)
I've been having a bit of trouble with my MOMO wheel lately - it works fine on combined axes but the moment I try to separate the axes, it shows both pedals as being at maximum in the profiler and only shows a single axis in game. Anyone had these problems before? It's really annoying.
Anyone had these problems before? It's really annoying.Chuck Norris is capable of temporarily embodying people he choses to embody - just for fun!
That's a bit ambiguous - lagging, in technical terms, usually means network lag (ie. a delay in the transfer of data due to a network). I think you're probably referring to stuttering - ie. a decrease in FPS. Does this actually happen consistently and does the problem go away when you enable auto-clutch again? The two things seem rather unrelated.
FGED GREDG RDFGDR GSFDG