That question was mostly answered on the same line:
This kind of system is technically possible (probably even relatively easily) provided someone can reliably host a database & web front end. Getting an InSim app to connect to the DB should be simple enough.
The main problem is that different admin teams tend to have different ways of dealing with things - some may disagree on the lengths of bans or the reasons for them. Ban appeals could potentially be tricky as well.
Some of the issues could be worked out using opt-ins for specific ban reasons (intentional wrecking being an obvious example) and most teams probably wouldn't want to opt-in to rules specific to only a few servers.
However, this would make the system more complicated, which brings forward the other potential issue - are there enough persistent trouble-makers to make it worth the effort?
If enough people are interested, it might be worth it, providing people are willing to put the time & effort (and money) in to keep it going in the long run.
A possible solution - not quite as quick to use, but should work with InSim as it is now:
The player would need to bind 3 commands to function keys (!up !down !select for example. "/o " instead of "!" for a local InSim program)
The 'active' button would have a different colour to the others. The player changes the active button using the up and down binds, and the select bind to effectively click the active button. The player would be able to navigate a menu system while still maintaining control.
DX10 is not backwards compatable (for code simplification/performance reasons). DX9 and earlier games run on a seperate DX9 API.
FWIW, I've never had aero get disabled by LFS. I generally only get that happen with old DirectX overlay methods - I don't actually remember any games disabling aero, only videos/media players.
However, I have had the occasional graphics driver crash in the past with other games which will knock out aero in the process.
The problem could easily be a broken driver which doesn't play nice with LFS for whatever reason - I have heard a few cases of the newer nVidia cards not being too stable with older games, this may or may not be related.
Do you use any overlays? (Steam/Xfire/gauges etc) I know Steam's isn't (or wasn't) too stable with LFS.
Has anyone else got this issue? If so, post full OS, graphics specs and driver version(s) - might help narrow down the cause.
Getting the data from the .pth files and converting to the open configurations is easier said than done
- The nodes are in different places on the same bit of track in the different configurations, due both to the way they were created and the different speeds involved
- There'll be much overlapping/intersecting of nodes where different routes intersect, particularly if there's a choice of route. I assume these overlaps/intersections would cause problems.
Not impossible, but the junctions in particular would be tricky, especially if there's no graphical way of removing/shortening them.
As I mentioned in an earlier post, you'd have to feed information to the InSim program based on the chosen route and use something like a lookup table to convert the non-sequential nodes to sequential equivalents. The order of the non-sequential nodes would have to be different for each route of course.
Multiple choice routes would probably have to use a combination of the above and algorithms similar to route-finding software like google maps. The route junctions could still be tricky though.
I was mostly referring to the node values sent via InSim - I'm afraid I'm not too familiar with PTH files.
It would be impossible to work out the correct direction of travel, unless the order of the nodes (not necessarily consecutive or all ascending/in the same order) is given to the InSim application for every given layout/config.
These could probably be cobbled together if there is a choice of route using techniques similar to those mapping software uses to plan travel directions. Flags & direction info could then be calculated by the InSim application. It wouldn't necessarily be easy, but it's certainly doable.
(The above may have come out in a bit of a mess, I'm tired )
Edit: If there isn't a choice of route, it'd be as simple as a lookup table.
Are you sure? Scawen has only mentioned no flags/wrong way detection afaik, which doesn't imply there aren't any nodes or similar.
Of course the server itself couldn't have a hope of working out flags or direction, but if there were nodes of some description, an InSim application could potentially do it if it knows the route(s) of the layout.
One question that immediately jumps to mind:
How will the track nodes work in open configurations? They obviously can't be consecutive anymore when there are multiple routes possible.
This.
LFS currently measures speed calculated from the driven wheels/transmission. There was quite a discussion about it at the time it was implemented IIRC.
If you want 'GPS' speed, this value can be obtained using InSim.
I never said it wasn't huge for near(ish) servers - but when the intercontinental links are 300ms+ themselves, an extra 10-16% isn't going to make all that much difference in the grand scheme of things
The biggest latency difference between fibre and copper is usually down to the trickery required to get the high speeds down the copper and not succumb to massive packet loss. Switching interleaving off alone on an ADSL line can reduce ping by 20ms or so.
ADSL commonly has a 30-50ms time to the first hop. It's usually fibre all the way from there. I get twice the latency to my local exchange, than from the exchange to the middle of Europe.
From what I've seen of pingtest.net scores (fairly unreliable, I know) fibre lines usually get <15ms to wherever the test server is, often <10ms. The links to the local exchange/fibre backhaul are going to be a fair bit lower.
Having said that, 30-50ms isn't going to make a whole lot of difference when 300ms typical pings to the other side of the world are concerned, although a couple of peers with ADSL are going to be 60-100ms slower to eachother than they would on fibre.
For what it's worth, LFS can handle high ping quite well, providing it's stable. High jitter tends to confuse the prediction system though :/
You may want to give TrackIR (or one of the free alternatives) a try - it should be more natural to move your head slightly to look around rather than curling your toes