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.
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.
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.
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?
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
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.
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.
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....
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.
run dxdiag, the Device Name on the Display tab will tell you.
My best guess for the low framerate is a combination of:
Not enough RAM (XP might help with this, W7 probably won't)
Rubbish on-board graphics (not even XP will help with this).