Yes, but with one hand I can only get to F9 at a stretch and only F8 if I use my left hand. When driving with anything other than keyboard, taking both hands off the controller is very likely to cause unwanted steering input.
I hadn't considered the repercussions of simply making Alt Gr = Alt, but it does seem wrong that it gets interpreted as Ctrl rather than either Alt or nothing when used with F keys. When used with a standard letter that doesn't have an option for the modifier, it often doesn't do anything at all (text input on some other apps).
Many other programs, particularly games, interpret the Alt Gr key as a kind of 'Right Alt' which can vary its use depending on the key combination. I'm not sure what interpretation would be best for LFS, or even if it's worth changing, but having Alt Gr + F* do nothing or assume Alt + F* would be more logical than pressing the Ctrl + equivalent.
Alt Gr != Ctrl
This is a fairly minor bug, but it's been bugging me recently (no pun intended).
The "Alt Gr" key seems to be interpreted by lfs as Ctrl instead of Alt. When I try to use the Alt Gr key to do the Alt + F7-12 binds with one hand, LFS runs the Ctrl + F equivalent.
The "Alt Gr" key seems to be interpreted by lfs as Ctrl instead of Alt. When I try to use the Alt Gr key to do the Alt + F7-12 binds with one hand, LFS runs the Ctrl + F equivalent.
Yes, the Scirocco was announced mid-2008, but the tyre physics update wasn't announced until much later.
The VW was almost ready to go in Dec. 2008, which is why we got the pre-release announcement. However, there were some problems found with the handling, so release was delayed until the infamous "early 2009" to let Scawen sort out the problems.
It turned out that the problems were actually caused by errors in the tyre physics model, so Scawen quietly started research and work on a new model. He didn't announce that he was working on the tyre physics until August 2009 after he knew that the new model was an improvement over the current one.
I'm pretty sure that the 3D model + textures etc for the VWS will have been finished long ago, but the ESP system will need to be (re)written once Scawen has finished the new tyre physics.
Thus concludes a summary of what I understand has gone on with the VWS/Physics announcements. I may have forgotten some things and/or got it a bit wrong, but I doubt it's far off.
Setting the deviceIDright/left to -1 for the unused monitor is supposed to work.
I think I got it working like that with v1.08 I think, but it wasn't reliable. YMMV
I think I got it working like that with v1.08 I think, but it wasn't reliable. YMMV
People also slate BT Wholesale.
Most problems with ISPs and/or bad quality connections are down to congestion. BT Wholesale (any non-LLU '8 meg' service) is usually oversubscribed and as such can't handle the traffic going through it.
Cable isn't immune to this either - the connection is still shared, but with people on your street, as well as people in the same town or on the backhaul. Traffic management and silly daily download limits still apply to VM cable (unless you fork out for the top-tier package). Location and who set up the connection in the first place (NTL/Telewest/Blueyonder) dictates how many people it's shared with and if it affects download. Sometimes the download isn't shared locally, but the upload usually is.
LLU ADSL however depends entirely on the ISP as to what the contention ratio is and therefore how likely congestion is. ISPs do exist that provide 1:1 contention (ie you have your connection speed 'allocated' and not shared with anyone else) at competitive prices. With such ISPs, the only problem you'll have - unless you have a poor quality line (BT's fault) - is if some muppet breaks a fibre link somewhere.
It's all swings and roundabouts - VM is generally fine if you have the top tier package. LLU ADSL is usually fairly good, but that will depend on the ISP. The poor sods who are stuck with non-LLU '8 meg, my arse' packages because they happen to live somewhere without cable/LLU have to lump it unfortunately.
Another thing to point out with the '8 meg' packages is that they've started to falsely blame line quality for not being able to get the full speed. BT now reckon that the line where I am atm can only handle up to 6mbit. I know for a fact it can do over 7.5mbit, because it did when the 8bit service was first enabled at this exchange. Now they have a lot more people using it here, the connection (not the line) just can't get that fast anymore.
Most problems with ISPs and/or bad quality connections are down to congestion. BT Wholesale (any non-LLU '8 meg' service) is usually oversubscribed and as such can't handle the traffic going through it.
Cable isn't immune to this either - the connection is still shared, but with people on your street, as well as people in the same town or on the backhaul. Traffic management and silly daily download limits still apply to VM cable (unless you fork out for the top-tier package). Location and who set up the connection in the first place (NTL/Telewest/Blueyonder) dictates how many people it's shared with and if it affects download. Sometimes the download isn't shared locally, but the upload usually is.
LLU ADSL however depends entirely on the ISP as to what the contention ratio is and therefore how likely congestion is. ISPs do exist that provide 1:1 contention (ie you have your connection speed 'allocated' and not shared with anyone else) at competitive prices. With such ISPs, the only problem you'll have - unless you have a poor quality line (BT's fault) - is if some muppet breaks a fibre link somewhere.
It's all swings and roundabouts - VM is generally fine if you have the top tier package. LLU ADSL is usually fairly good, but that will depend on the ISP. The poor sods who are stuck with non-LLU '8 meg, my arse' packages because they happen to live somewhere without cable/LLU have to lump it unfortunately.
Another thing to point out with the '8 meg' packages is that they've started to falsely blame line quality for not being able to get the full speed. BT now reckon that the line where I am atm can only handle up to 6mbit. I know for a fact it can do over 7.5mbit, because it did when the 8bit service was first enabled at this exchange. Now they have a lot more people using it here, the connection (not the line) just can't get that fast anymore.
Hmm, I'm out of ideas for solutions tbh, short of contacting sky/bt.
The 10 day thing is to determine the best sync speed for the line. This usually causes the connection to loose sync several times (would mean a complete disconnect for a minute or three), which is nothing like the problems you're describing.
From the attenuation figures you gave, the distance from the exchange is certainly not the problem. If you were to get ADSL2+, you should ideally get ~22mbit at 16dB, according to be - although the attenuation would be different with ADSL2+, so that won't be an accurate figure. You should certainly be able to get at least 5-6mbit on ADSL1.
The problem is like one or more of:
- congestion at the exchange
- problem with the line itself or its connection to the exchange
- problem with cabling between the line and the router/modem
- problem with the modem
1.3mbit actual and those latencies is unacceptable for an 'up to 8meg' ADSL connection when you're that close to the exchange. Call tech support is all I can really suggest for now.
ed: stick your phone number in the box at the top of this page to see what you should get with ADSL2+ (or ADSL1 if be isn't enabled on your exchange). There's a similar test in the broadband section of BT's site.
The 10 day thing is to determine the best sync speed for the line. This usually causes the connection to loose sync several times (would mean a complete disconnect for a minute or three), which is nothing like the problems you're describing.
From the attenuation figures you gave, the distance from the exchange is certainly not the problem. If you were to get ADSL2+, you should ideally get ~22mbit at 16dB, according to be - although the attenuation would be different with ADSL2+, so that won't be an accurate figure. You should certainly be able to get at least 5-6mbit on ADSL1.
The problem is like one or more of:
- congestion at the exchange
- problem with the line itself or its connection to the exchange
- problem with cabling between the line and the router/modem
- problem with the modem
1.3mbit actual and those latencies is unacceptable for an 'up to 8meg' ADSL connection when you're that close to the exchange. Call tech support is all I can really suggest for now.
ed: stick your phone number in the box at the top of this page to see what you should get with ADSL2+ (or ADSL1 if be isn't enabled on your exchange). There's a similar test in the broadband section of BT's site.
Last edited by Degats, .
Packet loss is one of the problems (and will cause you to loose connection to any server sooner or later) although the high-ish ping and high jitter will make car-car interaction horrible.
If they don't have LLU at your exchange, you'll most likely be on ADSL1 (someone else may be able to confirm how sky broadband works when not LLU)
That download speed is fairly shocking - as teedot asked, how far away is your exchange? (If you don't know, look in your router status for something like 'downstream attenuation' - it'll be a number, most likely reported in dB. Failing that, PM me your post code and I'll look it up for you.)
I'm assuming as you're with sky, you also have a sky TV box? If so, chain two ADSL filters between the sky box and anything else - that trick is supposed to solve all sorts of problems on ADSL2+; it'll probably help with ADSL as well.
Another thing to try:
Plug a touch-tone phone directly into the master socket, dial 17070 and go to option 2.
This is known as the quiet line test - the connection should be absolutely silent - no hiss, pops or crackles.
If you hear anything, that would indicate a fault on the line - phone BT and mention the quiet line test.
If they don't have LLU at your exchange, you'll most likely be on ADSL1 (someone else may be able to confirm how sky broadband works when not LLU)
That download speed is fairly shocking - as teedot asked, how far away is your exchange? (If you don't know, look in your router status for something like 'downstream attenuation' - it'll be a number, most likely reported in dB. Failing that, PM me your post code and I'll look it up for you.)
I'm assuming as you're with sky, you also have a sky TV box? If so, chain two ADSL filters between the sky box and anything else - that trick is supposed to solve all sorts of problems on ADSL2+; it'll probably help with ADSL as well.
Another thing to try:
Plug a touch-tone phone directly into the master socket, dial 17070 and go to option 2.
This is known as the quiet line test - the connection should be absolutely silent - no hiss, pops or crackles.
If you hear anything, that would indicate a fault on the line - phone BT and mention the quiet line test.
Try speedtest.net and pingtest.net and post the results here.
Are you using an ADSL filter between the modem and the master socket?
How long did you run ping for? Try at least 100 to get a decent reading (ping -n 100 lfs.net)
What kind of ADSL (1/2/2+)? who is the ISP? Do you have problems connecting at all times of the day or only some?
Are you using an ADSL filter between the modem and the master socket?
How long did you run ping for? Try at least 100 to get a decent reading (ping -n 100 lfs.net)
What kind of ADSL (1/2/2+)? who is the ISP? Do you have problems connecting at all times of the day or only some?
As far as I'm aware, the current LFS model is purely mathematical. No tables, just equations.
There are several hosts that run using WINE on Linux with no problems. Mine included.
This isn't an LFS problem - upgrade WINE, check that UDP packets are passing through unheeded, make sure all the right ports are forwarded.
This isn't an LFS problem - upgrade WINE, check that UDP packets are passing through unheeded, make sure all the right ports are forwarded.
Try telling them that S1/2/3 is just a level of content (as it is now) and not a program version (which is what it used to be)
You need a 5000 series ATi (Eyefinity) to be able to span in Vista/7 afaik.
The ability to set a maximum time as well as number of laps would probably be useful for leagues with time constraints.
If it becomes impossible to complete full race distance within the time limit - pace cars/slower than expected lap times etc - the race ends when the time is up.
This comes up occasionally in F1 (2hr limit) and quite often in BTCC support races.
ed: it may already be possible to do this by setting a time limit mid-race via InSim. Smaller time increments for the time limits would still be useful though.
If it becomes impossible to complete full race distance within the time limit - pace cars/slower than expected lap times etc - the race ends when the time is up.
This comes up occasionally in F1 (2hr limit) and quite often in BTCC support races.
ed: it may already be possible to do this by setting a time limit mid-race via InSim. Smaller time increments for the time limits would still be useful though.
S1 isn't as dead as it used to be, now S1 licensees can join any S2 host which is using only S1 content at that time. Before this feature was enabled, CTRA 1 was the only busy S1 server.
What would you suggest to do with the current S1 users? Upgrade them for free, which would annoy the people who paid full price for S2; or restrict them to demo, annoying all the S1 users who can no-longer use their paid for content?
What would you suggest to do with the current S1 users? Upgrade them for free, which would annoy the people who paid full price for S2; or restrict them to demo, annoying all the S1 users who can no-longer use their paid for content?
OutSim outputs Z-axis g-forces. You could use these, along with an InSim button, to display them real-time.
Something, somewhere, is dropping/blocking UDP packets.
It's either a software firewall (Windows and/or third party - check both), hardware firewall/router, your ISP, or something broken in your LFS install. Check all of the above and make a clean install of LFS.
Options > View > Draw driver / wheel > [driver ON wheel ON]
If that doesn't work, make a clean install of LFS
It's either a software firewall (Windows and/or third party - check both), hardware firewall/router, your ISP, or something broken in your LFS install. Check all of the above and make a clean install of LFS.
Options > View > Draw driver / wheel > [driver ON wheel ON]
If that doesn't work, make a clean install of LFS
Not necessarily - It was replaced for S2 by the UFR, as the LX8 and XFR would be alone in their own classes. (See here)
This doesn't mean it won't make an appearance in S3 at some point.
There was a graph posted a few years back with S2 licence numbers over time, with reference to various major patch releases and milestones.
I thought I'd saved a copy of it, but I haven't been able to find it :/
I seem to remember in excess of 100000, but my memory could be deceiving me as usual.
Ed: OK, it was lfs.net member growth, whatever that means. As of jul 2007, it was just over 160000 with a slight exponential increase. Make of that what you will.
I thought I'd saved a copy of it, but I haven't been able to find it :/
I seem to remember in excess of 100000, but my memory could be deceiving me as usual.
Ed: OK, it was lfs.net member growth, whatever that means. As of jul 2007, it was just over 160000 with a slight exponential increase. Make of that what you will.
Last edited by Degats, .
What kind of performance are you getting in LFS? It's possible it is actually using the nVidia one in LFS, just reporting it as the onboard.
The ABS and TC lights work in the same way:
Constantly on, there's an error (ie it's been switched off)
Constantly off, normal.
Flashing, it's active.
Constantly on, there's an error (ie it's been switched off)
Constantly off, normal.
Flashing, it's active.
Wrong.
Up until DX9, backwards compatibility was kept. However, with DX10, it was made deliberately incompatible to optimise it. In Vista and 7, both DX9 and DX10 run simultaneously, although programs will use one or the other. Similarly, DX10+ cards are usually also DX9 compatible to allow for either or both.
Programs have to be written for either DX9 or DX10+. Games that support both usually have different executables and/or libraries for each.
DX11 does have compatibility with DX10 and 10.1 though.
http://en.wikipedia.org/wiki/F ... _to_Windows_Vista#DirectX
Fair enough - it was affected by control rate when I was testing manual button clutch with a g25 shifter, presumably it doesn't always affect it then...
Bear in mind that the button clutch isn't instant - at the fastest button control rate, it's not far off what you can do with a pedal.
Perhaps reducing the fastest button control rate (which affects all control inputs AFAIK) would achieve the same thing?
Not that that would stop profiler macros or emulated axis, which can actually be instant....
Perhaps reducing the fastest button control rate (which affects all control inputs AFAIK) would achieve the same thing?
Not that that would stop profiler macros or emulated axis, which can actually be instant....
Manual clutch override when you haven't got a clutch pedal or are using sequential?
I find it quite useful when I have to use my joystick or a mouse.
Yep, I think that's probably the problem - nothing you can really do about it I'm afraid 
Check your power settings anyway, they may be making things worse.
Check your power settings anyway, they may be making things worse.
FGED GREDG RDFGDR GSFDG