Yeah, I thought it should have come up already but I also couldn't find any sign of previous discussion (searched for a few mins with various keywords...).
I chose this forum btw because the improvements one says "...suggestions on how to improve the LFS simulation" which this really isn't
I got an email today about the new version (0.6F), and in it I noticed a warning: "Use your LFS username and password only on the first 4 websites listed above (the Merchandise shop is not run by LFS)".
Well, I reckon it isn't your CPU (my Duo is much slower - 1.8GHz - and I have almost no issues except on open layouts), so I'm guessing the GPU is a bit of a dog. Mine's also 256MB but copes pretty well without setting everything to low/off - Radeon 1650XT. AA & AF are on too.
Remember that LFS is single-threaded. CPUs have not got much faster since 7 (!!!) years ago when I bought my pretty meh CPU - it's still only a factor of 4 slower than the fastest CPU you can buy when running this single-threaded benchmark http://www.cpubenchmark.net/singleThread.html
So, unless I'm mistaken about your CPU, it's probably not much more than a factor of 2 slower than the best money can buy on single threaded code like LFS...
Or possibly I should get sleep cos I'm writing nonsense
I'm hugely excited about the Rift, despite knowing that I'll probably need a new PC before there'll be any point in me buying one (!).
I am a bit worried about how playable it'll be though, given that I won't be able to see the keyboard. Since I use the paddles to shift, the lack of hand movement (to a stick) won't bother me.
Something that hugely surprised me a few years back: when I tried to show some friends and family how cool LFS is, a couple of them felt nauseous driving it on a normal screen! (Can't recall if it was a laptop or desktop - probably laptop - but I've never felt remotely nauseous in LFS or games so this baffles me.)
Yup, they stand out nicely It actually crossed my mind briefly to wonder if the new colours were deliberate. (I dismissed that crazy idea about a second later though :P)
And omg, who could possibly vote to change them?
Darn yes, I keep forgetting that file exists, ta. (Having said that, one line early in autocross.txt says "All the editor keys are listed on that screen." )
Remarks:
a) OOO, that's really pretty - don't fix it
b) Whoa, a measuring tool?? Cool! But it isn't listed in the "keys" list - is that deliberate or a bug? (Google helped me to find that "d" is listed in the wiki manual as the key for the measuring tool...)
c) what's that little window with "x400 x1 ... Width: 44 ..." etc in it? I don't get that when I hit "d"
d) are there any other keys that work in edit mode that aren't listed when you hit the "keys" button?
I'm thinking that (just possibly) Dave was not being sarcastic with his original post ("just what was needed")
Like most people, I also thought "aw shit" at first, but then things like the CEO mentions above started to occur to me. If FB truly stay hands-off then it's probably a major win all round...
And as Jason says, we can all chill out cos VR is inevitable now.
(Having said all that - I was fighting the impulse to buy one until I read the news. Now... I'm not. Will wait and see.)
Huh? Noooo noooo, you've got it all wrong. This guarantees we'll have the tyre physics patch in July, cos Scawen will want to have it out of the way before enjoying his new Rift
Hmm, I reckon that's overstating the risk quite a bit for a "typical" user who is behind a NATing router with little or no port forwarding turned on.
Having said that, even though I'm a big fan of XP I'm not hugely keen on staying with it much after April. I don't like 7 much so far, strongly dislike Vista, and 8[.1] is just weird. So... wtf to do.
I'm tempted to stick with XP a little longer, on the basis that most of the risk I currently experience is via the browser (+ Flash etc.) in any case. When I replace this PC (well overdue) I suppose I'll have to choose between 7 and 8....
Edit: forgot to ask Scawen a question:
I'm guessing that (surely??) there must be a "supported" and vendor-independent way to drive multiple screens - if this is the case then do you dislike it because it saps performance (relative to a single-surface model) or for another reason?
Ah yes, it was good (compared to 3.1 anyway!) but I'm presuming you never experienced NT 3.51. IMHO nobody who did would ever consider going back to WFW 3.11 NT3.51 was the pinnacle of stability, and a bling-free zone.
My "textures (excluding skins)" is set to high - changing that probably wouldn't help though? (Because it says "excluding skins").
My "car and helmet skins" is set to compressed, which (from the explanation offered by the question-mark button) appears to be the option for best performance. I am too noobish to know how to do high/super-high res skins (so am presumably doing neither ).
However, your comment also made me think again about the skins_x folder - it had got quite big so (by coincidence, lol) I purged it last night. Will see if that makes a difference... (I'm thinking that reads/writes to that folder might take a while if the folder has thousands of entries.)
Funnily enough I'm noticing pit-out (and possibly join-related??) stutter much more recently than I ever recall from the past. However I'm mostly running 0.6E - I don't think it has been any better/worse with E13/14.
Yeah, that's pretty much what I mean (many ways to tackle it but that's one).
And in fact I reckon LFS already has all the maths to handle velocity changing between timepoints because I seem to recall that it uses multiple derivatives in order to make multiplayer mode work well with only a few updates per second. (Can't recall how many derivatives tho.) That's the part that could make it more accurate to do it by interpolation than (what I'm guessing is) the current scheme
(To do the best possible job on it, you would also need to store the previous point's information - position, time, velocity, accel, and the higher derivatives; the storage required would be negligible. However, doing it by just using the current point's info is probably acceptably accurate anyway.)
Huh?
I'm unsure where you see a problem here.
Interpolation of a smoothly varying quantity is NOT the same as a guess.
(In fact, it's arguably better than the current scheme, but the difference would only be apparent if you really split hairs.)
Ah, OK, excellent point, thanks. I had been thinking that open tracks were harder on the CPU because of the physics loop doing more, but that didn't quite make sense either. Your explanation does seem to match the evidence awfully well
Agreed, BUT (as I once suggested in the distant past) LFS could semi-trivially interpolate between the current position+time and the previous one to give much higher precision splits. This would free the physics clock to be run at whatever we want. (Probably same for everyone tho, or sync issues...)
What's not overly clear is whether we'd gain anything at all by exceeding 100 Hz. How does one quantify smoothness?
Last night I played with limiting the frame rate to 50fps (I was hoping for exactly 2 physics updates per frame). It didn't really work though as the expected frequency lock did not occur - it was dancing around the 48 fps mark... (It was capable of 90-100 fps when not limited.)
Funny you say that - some time back, before I realised LFS was single-threaded, I had assumed that there was a physics thread which would regularly update, and a separate graphics thread which would display stuff from the most recent snapshot (bit like double-buffering) of the physics data
(Beneath this was the possibly-wrong assumption that the snapshots required by the graphics thread were pretty small.)
My own particular problem right now appears to be linked to CPU overload (open tracks). Not sure what would fix that. Is it really the case that the physics loop is still updating at 100 Hz even when the CPU is pegged and the graphics update rate falls to 30 fps or less?
(I confess I have yet to try the DX9 patch as I was assuming it would make things worse.)
Edit: no argument on the tiny pixels. Total waste!
Yes, this struck me the other day. So the problem (if it exists!) is likely to be connected with inputs from controllers (as someone else suggested) and/or visual feedback. The car would then be nominally doing exactly what it's told, but what the driver is telling it to do is messed up either because the driver isn't seeing the right things or the controllers aren't being read in a timely fashion...
I'm planning to do some experiments myself later. Might even do "blind" tests (i.e. I get someone else to set the fps limit and switch off the fps display )
Makes sense, BUT I could have sworn someone asserted (some years ago? :shrug that the LFS physics loop was not entirely unaffected by the display FPS and thus (the argument went) it might feel better to have vsync off... Personally I don't think I ever tested it much though.
Fair point, but whenever I succumb to the temptation to try demo, the normal pattern is that I enjoy it for a bit, and then it's ruined by idiots and I end up just wishing I hadn't bothered. (Having a grumpy day today! )
Good idea, will check that out. The only downside of organised stuff is the need to find time to practice, rather than just enjoy some casual races. I do enjoy organised events now and then though.
When I really think about it, I reckon I don't really care about the Scirocco, or the new tyre physics - I'd appreciate them but if they never come, big deal.
I would kinda like new tracks, but again, no biggie.
I don't even care about the visuals.
What I really miss is drivers to race against. Had a look tonight, and no servers seemed worth bothering with - hardly anyone about
So, other people must care about something, cos they are leaving.
I'm wondering if the non-arrival of the promised stuff actually drove people away, or if the lack of developments would have done the same anyway even if stuff hadn't been announced...
Nice one! Gorgeous little car (well, not so little compared to your last one ) - shame it's so pricey in Norway, but enjoy it.
And so long as you do plenty of mileage and not too much city driving, the diesel is absolutely the right choice - plenty of power and fuel economy.
I'm gonna have to replace my own ancient and unwell Punto very soon. Much tinier budget, much lower mileage, so probly another ancient petrol shitbox...
[Edit: I reckon Takumi got banned for posting a really tasteless remark on the RIP thread.]
Hmm, when you say "no core is near 100%", are you saying that all cores are sharing the load, and if so, is the total CPU load from LFS equal to one core's worth? If so then you really are CPU-bound because LFS only seems to use one thread. For example, on my PC, I get 50% CPU load whenever LFS is CPU-bound because I only have two cores...