Quote from R5Rider :

I have kind of a problem running LFS in my notebook.
It's an AMD Turion 64bits 2.0GHz single core, 1,5Gb DDR-2 and a shared memory ATI X1100 256Mb. It runs slow, but very very slow.
Running on XP, haven't tested yet with Win7.

EDIT:
When I meant that it runs slow, it is in single player with NO AI

That's your problem.
My 1.6GHz Turion (albeit an x2 - LFS isn't parallel threaded though so it won't make much difference) is more than enough for LFS, but the X1300 struggles a little. It's just about playable at 2xAA, but any more and it kills it.

Edit:
W7 is unlikely to give you any performance improvements, as you're graphics limited. Vista/W7 can help a lot when CPU limited.

Chances are, the frequencies made at ~3500rpm are matching the crossover frequency of your speakers. Frequencies on and around the crossover often sound much louder than others on many (usually cheaper) x.1 systems.

My speakers do the same thing with a few cars (although most prominently in the XRG/XRT). The crossover on mine is ~125Hz and that's pretty much the frequency range of the XRG @3500rpm, particularly when coasting.

There's not a lot you can do about it, other than tweaking the crossover in your audio driver's settings (if it has that option), or finding a system wide Equaliser (good luck - if you find one that works, let me know ) and reducing some frequencies at around 110-170Hz.

Raw stats are interesting and often revealing.

Intepretations/evaluations of stats are pulled out of the arse of whoever has an opinion to prove.

IMO, a third 'middle ground' setup option would be good.

This would give:
- Stock: Showroom spec, with only tyre pressures etc adjustable (as Scawen described as the limited option)
- Sane/Race: Some components can be changed (suspension, brakes, gear ratios, diffs etc) but not infinitely variable and with sensible limits. This should make adjustments similar to most racing series possible.
- Extreme: As it is now, with unrealistic limits and fine adjustments.

Personally, I'd be happy with just the first two (stock + sane), but I know a lot of people like taking things to the limits to see what can be done.

Quote from Shadowww :

It >could< be repack of debian too. :P

Or just about any base distro running the Gnome desktop environment.

After scanning the website, it's actually based on slackware

/offtopic

That tells me that there's something wrong somewhere and it's not LFS related.

Anything above 0% packet loss is bad, as is 'jitter' that high.

Either the router is indeed to blame, or something's happening with your ISP, either overloaded or traffic shaping etc.

Looks like you're not getting any position updates until you join the track.

Random guess: perhaps UDP packets aren't being recieved properly by your system.
There's a key combination I hit by accident occasionally that forces TCP for position packets instead of UDP. No idea what it is though. Failing that, check firewall(s)/router settings etc.

I have replays for:
race 2 http://www.mediafire.com/download.php?jtkymzjnnjj
race 7 http://www.mediafire.com/download.php?mmnxktzwhdy

Quote from Postman Pat :

The thing you alter with the software in a sim, usually called FOV, would be GFOV (geometric field of view). Which according to tons of research - some in driving sims - very much affects accurate perception of speed and distance.

Yeah, that's pretty much what I was trying to say. You're only really going to get an accurate perception of speed when GFOV==DFOV and it's large enough to display what you'd see in your periferal vision.


The dynamic alteration of GFOV in games is used quite a lot, and can help when done properly (ie not like when you press the nitros in NFS). Curved/fishbowl GFOV (higher values on the edges of screen than the centre) is used in a few. Motion blur is often used as well (usually badly).

The problem is, all these tricks need to be subtle or the illusion fails completely. It's very hard to get a good balence between subtlety (sp?) while actually making enough difference to prepresent perception properly.


I've yet to find a game that achieves it, and I doubt it's even possible. Proper speed/distance perception is one of those things that only works for the few people who have the right hardware - for everyone else there must be compromise.

Field of View, by definition, is constant.

The 'correct' FOV depends on the overall width of the screen(s) and how far away from them your eyes are.

Unfortunately, the vast majority of people don't have 180+ degrees worth of screen coverage - most of the time, only 25-50 degrees or so.

Using the 'correct' FOV, you will not get an accurate sense of speed at such a small FOV, as you can't see peripheral movement. You also can't see anything of what's next to you for the same reasons. With such setups (low physical FOV) the ingame FOV is always a compromise between accuracy, sense of speed (for racing games anyway) and how much of what's around you you need to see.

In an ideal world, everyone would have at least 160 degrees of screen coverage - ideally 360 degrees - and then the 'correct' FOV can be used properly and you will get an accurate sense of speed.

Unfortunately, that'll probably never happen.

If you press shift + f4 in LFS, it will toggle fullscreen/windowed mode.

I've also had no problems with W7 64

Quote from tristancliffe :

I run Windows 7 64 bit, and had no problems. Well, actually, I did seem to struggle making a shortcut in the Games quicklist - when I loaded LFS from it it said it couldn't do something - but that was easily fixed with a couple of minutes fiddling.

For some reason, when dragging the .exe into the Games list, it doesn't include the "start in" path in the shortcut it creates. This means LFS has no idea where all the other files are, so gives an error.

If you right-click LFS.exe, create shortcut, rename the shortcut to whatever you want, then drag the shortcut into the games list, it'll work fine.

Quote from Senninha25 :

Oh yeah, I kind of mentioned a problem with FlipCams in Z17, well I read that Scawen had implemented new commands that rendered FlipCams unusable. Does someone (sorry for potential spam) know those commands? I'm completely baffled with this.

The commands added were to make flipcams useable after a change in the code had broken it.

The new commands are:
/view save
/view reload

To restore functionality, you'll have to edit /data/scripts/fc_reloadview.lfs by putting "/view reload" at the end of the file.
Add "/view save" to the start of every fc_runCam*.lfs file

It should now work as it used to before z17.

(I think that's right)

Last edited by Degats, Wed 21 Oct 2009, 19:44.

Gui/click misalignment fixed from test 2

Can't reproduce any of the others in z19 or any of the tests.


HD4890, ccc v9.9, vista64 sp2, clean lfs install for all.

Same here with the UI when loading lfs into fullscreen.

Clickable areas seem to be misaligned about 4px right, 16px down.

Vista x64

ed: 1440x900 if that makes any difference

You could try:

> Download a demo of a game released in the last couple of years or so and see how it handles it.
> Reinstall LFS (extract the installer to another folder somewhere)
> Reinstall/update drivers
> Check GPU temps (GPU-Z - it can log them to file as well)
> If you've got a more powerful PSU somewhere, try it - dodgy PSUs can cause all manner of weird and wonderful problems.
> Test the RAM (unlikely to be the problem, but you never know)
> Check over your motherboard for any capacitors that look like they've been oozing.

Quote from hsvdt :

I don't know if this is the right place but what i would like to see is when changing gears the driver moves a gear shift leaver
its just a thought and I dont care if anyone diasagress

Should be in the Improvement Suggestions forum.

As ever, the problem with that is that you've finished changing gear by the time the animation would even reach the shifter as it can't predict when you're going to change gear.

TDU compensates by reaching down when it thinks you're going to change, which can look weird as it's often wrong and reaches down for no reason. Other times when you shift and it's not expecting it, it doesn't move at all.

Personally I'd prefer it not to be there at all as it will always look unnatural, but I'm sure others would disagree with me

/offtopic

Quote from Scawen :

How does Flipcams try to reload views? Does it flick to cockpit then back to custom view?

Default behaviour is: /press v then /shift v
An alternative behaviour commented out in the script file is /view custom.

Default won't do anything if you're not already in custom view, alternative switches to the new view regardless of current view.

Edit: If you were to add "/reload_view" the only change to flipcams needed would be to add that command to a single script file.

Last edited by Degats, Mon 12 Oct 2009, 19:00.

Same here with the flipcams problem.

The program appears to be operating properly - message appears, folders in /data are renamed - but the views aren't reloaded/updated from the files.

Edit: maybe LFS no longer reads the views file every time the view changes to custom?

Regarding having the mouse visible, when I need to use the mouse I use it in wheel/xy mode (yes I know I'm a rare breed) rather than mouse mode so I can have better control over throttle/brake.
I find having the mouse visible useful so I can have an idea of my throttle/brake input while paying attention to the road.
I'm probably the only one who thinks this, but thought it was worth a mention

Quote from pik_d :

If I am right, the "lag bars" in the lower left are currently in the same order as the connections list. This can be used to tell who is lagging without actually having to cycle through the players by position matching between the two.

Exactly my thoughts as well

Quote from logitekg25 :

should i just contact logitech tech support? (i havent tried it yet :razz

Probably

I've never had the profiler window do that while it knows the controller is there, so I can't help you

It does that when the wheel is disconnected and the profiler can no-longer detect it. It may be possible something else has caused it, I dunno.

I've never had any profiler problems in Vista(32 or 64) as long as the profiler window has been loaded at least once in that windows session and no other program/window steals focus from LFS.


Incidentally, as this is a different issue, you should really have made a new thread IMO

The biggest effect on the flight of a jump is based on what the throttle/brakes are doing just before takeoff and how they affect the weight transfer.

If you accelerate just before take-off, the nose tends to rise. Brake and it'll dip (like in the OP's video). A constant speed or slight acceleration will be more level. How much each of these will actually affect the car depends on the particular ramp, weight distribution and aerodynamics.

Sadly, it's very hard to control jumps off the autocross ramps in LFS as they have next to zero friction. You do have some control on the dirt jumps however.


Throttle changes in-flight will make next to no difference in the kind of cars in lfs with the kinds of speeds possible. May be possible to test it using big wheels in tweak, I dunno.

Possible solution:

Implement a (reasonable) maximum possible speed/acceleration for the steering imputs - possibly based on the FFB calculations, max reasonable force on the ingame steering wheel etc.

Problem solved for all 'unrealistic' controllers, including wheels with very low rotation.

kthxbai


(probably more trouble/effort than it's worth though)

Quote from pandera :

it looked like everyone else was lagging

A sure sign that it is in fact you that's lagging

If some but not all seem to be lagging, it's generally an idication that their connection to the server is worse than yours. If everyone else seems to be lagging, then it's almost certainly you, not them.

Hopefully back to being constructive...

Quote from ScoobRX :

Lol, sorry to interrupt the whole argument...

But I was wondering if the new tire physics would cause the force feedback to behave differently. For example will opposite lock occur with a bit less force now? (The stopping force on the wheel after you finish the initial part of the counter steer feels very strong and springy as is right now)

I very much doubt the FFB model itself will change.
As I understand it, it behaves as a result of forces on the steering wheels etc and as such it should behave differently if the physics change, particularly a change like tyre physics. I didn't have a FFB wheel to compare the last time the tyre model changed, so I can't give you an answer for certain, but I'd be surprised if FFB doesn't feel different as a result of new tyre physics.