You can get lap number and (sort of) lap distance percentage from InSim MCI packets.

You just have to assign the correct axis to the clutch in the controller setup. Even if you set the gearbox to automatic you still have to put the car in gear, otherwise it will remain in neutral.

LFS won't allow you to release the E-brake until you put the car in gear for the first time. If you're using the H-shifter, make sure that you've mapped the shifter correctly and that "H-shifter" is selected in the controller setup.

Car doesn't loose power because of the cooling system. Air density decreases with its temperature so in hot weather there is less oxygen in the engine. Less oxygen means that less fuel is burnt which is where the power loss comes from.

Thermodynamically speaking just the fact that the fuel is burning in hotter environment results in less fuel being burnt (Le Châtelier's principle).

OutGauge misconfiguration. The LEDs will blink until you get first valid OutGauge packet. Don't worry, you're like the 115th person to have run into this...

The config looks good, can you try some tools that use OutGauge to verify that it works? Are you sure there isn't anything else already listening on 30000/UDP like a BitTorrent downloader?

Oh God, and I seriously thought I wouldn't have to explain this to anybody because it's so frikkin' obvious.

Quote from Racer X NZ :

So that's just a report I was telling you about earlier from the BBC that keeps getting deleted. Didn't comment about it's accuracy. And given the weather at the time it's highly unlikely.

The one I asked you to watch was the CNN one, that is rather interesting.
The Russian media had spotted this earlier, so had the German Airforce expert. It would be interesting to actually get this checked forensically by an expert.

http://www.anderweltonline.com ... oad/PDF/Cockpit-MH017.pdf
This is a different shot of the same area. This only occurs around the cockpit area.

Shooting down a highly automated aircraft by trying to kill its crew is like the most idiotic thing to do. These aircraft fly almost by themselves and MH17 was flying on autopilot shortly prior the crash. Killing the crew or destroying the controls won't necessarily switch the automation off. Aircraft with such damage can fly thousands of miles before it crashes due to fuel starvation or some progressive structural failure.

Quote from Racer X NZ :

And before some hero points out that the SU 25 cannot attain these altitudes I suggest a little bit more research on their part. If you do this you will discover that in 2010 the Ukraine issued a contract for an upgrade to an improved SU 25 M1 spec, with seriously uprated engines (R-195) and avionics.

Again, you are very wrong. Ukrainian Su-25M1 is a joke of an upgrade (sorry). The R-195 engine provides about 10 % of additional thrust over R-95Sh, that won't increase the service ceiling by 3 km. It is also not specific to the Ukrainian M1. Original Su-25 had a maximum ceiling of about 7 km in clean configuration - that means WITHOUT any weapons except for the internal cannon. Max ceiling depends quite a lot on weather conditions but even if an Su-25 managed to fist its way up to 10 km, it would be at the very edge of its performance envelope. It absolutely would not have been able to precisely target MH17's cockpit and take it out with a gun. Go look at the specs, they're all over the Internet! You also seem to be forgetting the fact that max speed of Su-25 is quite close to B777 cruising speed. Therefore it is almost impossible for it to climb high enough, catch up with it and aim weapons at it.

Even if the Ukrainians devised some sort of evil scheme, why wouldn't they have just moved one of their own Buks close to the conflict zone and use that? Or better yet, why wouldn't they have shot it down with Su-27 or MiG-29 which could have accomplished such a task easily and from 50 km away.

Quote from Racer X NZ :

As supported by Russian radar information released to the EU which stated the aircraft were at a similar altitude. This is impossible with a standard SU 25.

Russian source mentioning "similar" altitude... now that's a lead! Or rather... not.

Quote from Racer X NZ :

Upon entering Ukrainian airspace, MH17 was instructed by Ukrainian air traffic control to fly at 33,000ft. The M1 spec isn't capable of 35,000ft.

Buk-M1 can engage targets flying as high as 72,000 ft.

You're not getting any OutGauge data; probably because it's not enabled in LFS cfg.txt.

Quote from Be2K :

the Problem there is, the RPM Values are incorrect. The Red lights showing up to early.

When ever i edited the Values it seems that the program just ignore them and it uses default values..

The mod follows the settings in the config file. What you might be missing is the fact that the second value controls when the LEDs start to flash and not when the first red LEDs light up.

Car rendering is broken with 0.6F2. The problem is fixable by putting D3DCompiler_43.dll into LFS directory. It seems that as of 0.6F2 it's necessary to use native versions of both "d3dx9_43.dll" and "D3DCompiler_43.dll". I haven't run a benchmark yet but there seems to be some performance gain even on WINE. This is valid for an nVidia card with the latest proprietary drivers, YMMV.

Sidenote: WINE reports

once while LFS runs. This means that this function is not actually implemented, it just returns immediately with a successful result so whatever it should do is not done.

Quote from Lotesdelere :

http://www.euronews.com/2014/0 ... se-to-malaysian-airliner/

CNN - quoting Russian sources - says that the Ukrainian jet in question was an Su-25, Soviet version of A-10. Su-25 has max ceiling of about 7 km (without any payload) and a top speed of ~980 kph. If it was there, it is VERY unlikely that it flew outside the war zone, let alone engaged MH17. Its presence could have confused Buk's radar operator but that's about it.

Quote from amp88 :

Source? Didn't you see my post on the subject of the 'incorrect' timestamp on the video? Or did you see it and choose to ignore it (possibly because I'm obviously a CIA plant who's here to try and brainwash people into accepting the almighty US and A as their personal saviour)?

As much as Racer X accuses us of ignoring evidence of conspiracy he ignores evidence that disproves his nutcase theories. BTW, a very thorough analysis of the "Creation time" glitch can be found here: https://gist.github.com/klaufir/d1e694c064322a7fbc15

@Racer X:
You realize that about half of your "proofs" of a Ukrainian coverup have already been conclusively disproven, even in this very thread?

Quote from ACCAkut :

my oppinion: Accidental shot down from separatists site, maybe aided by russian agents/soldiers (as in "push this button to fire BUK", not as in "now shoot civilian aircraft")

This is my theory as well. I assume that basic operation of the missile complex is not all that difficult (YouTube even has some videos with a simulator of S-75 and S-125 launchers). It is only at real wartime when there are multiple targets, enemy airplanes with antiradar missiles and strong ECM conditions when you have only seconds to find, identify and fire on the target. This is when you need a well trained, professional and experienced crew. The crew that manned the launcher that (probably) shot down MH17 was in no imminent danger and hitting one of the largest passenger jets ever to fly is not exactly a paramount of combat skills... This is why I have no problem believing that the Russians could have given the separatists some "How to shoot a plane down with Buk M1" crash course not realizing they would make such a terrible mistake.

Quote from Racer X NZ :

https://www.youtube.com/watch? ... UT3w&feature=youtu.be

Did it ?, this seems to suggest something different, using 'your' information.

Let's have a look at come context here.

From 12th July 2014


From 14th July 2014


From 16th July 2014


From 17th July 2014


It is not unusual for aircraft to be routed slightly away from their original route to avoid bad weather or traffic congestion. There were also two other aircraft in MH17 vicinity at the moment it crashed (https://twitter.com/flightrada ... 89843415002001408/photo/1) so if MH17 wasn't there, they could've hit another passenger aircraft.

Quote from Racer X NZ :

Not unusual having 'Your to blame' videos posted before the event happens. Sandy Hook is a great example of this.......

I thought that amp88 just showed that YouTube sets the creation time one day ahead of the actual time of uploading.

Quote from Racer X NZ :

Ukranian Air Traffic control dropped the hight from a requested 35000 ft to 33000 ft, and also changed the flight track. Right over a war zone to be exact.

It didn't. Check the tracking information on FlightRadat24.com or FlightAware.com. You'll find that it followed exactly the same path as other MH17 flights.

Does anybody know how the YouTube creation and tagging time work? I find it rather odd that some of those allegedly intercepted phone calls uploaded by Ukrainian Intelligence seem to have been created the evening before this all happened. I'm not sure if timezones would account for the difference. I'm on a pretty slow connection now so I cannot check this against my own video.
(https://www.youtube.com/watch?v=V5E8kDo2n6g)

This is so much of a sick theory... Jesus

- Since Putin was returning from Brazil to Vnukovo airfield, flying over Donetsk in Ukraine would be a hell of a detour.
- Surface-to-air missile systems primarily use radars to guide the missiles. Visual appearance of the plane does not matter. Even if you were trying to identify the aircraft visually, the lack of 4 contrails should give you a clear info that you are not looking at an Il-96. Contrails are one of the few things you can easily make out from the ground.
- The accident you are referring to happened during a big military exercise during which 24 missiles were fired and one of them hit a wrong target. It should also be noted that the weapon that hit the Tu-154 was most likely fired from an S-200V system from 1970.
- The reported times where the flightpaths of MH17 and RA-96016 were supposed to intersect are 40 minutes apart. An airliner travels about 600 km within 40 minutes... how lousy a shot would you have to be to miss your target by that much?
- MH17 had been tracked by Ukrainian ATC since it entered their airspace. They knew the aircraft was there and where it was going. It also followed the same flightpath as the previous flights.
- Why would the Ukrainians try to shoot a Russian plane down anyway? I thought they were trying to keep the Russian forces outside the Ukraine borders.

Do you actually spend any time thinking when you're concorting these theories or do you just empty a bottle of cheap liquor and type whatever happens to cross your mind?

Updated Linux benchmarking tool for 0.6F. The results are not entirely comparable with Fraps on Windows but hopefully the difference is minimal. Linux kernel 3.4 or above is required. Run

to build. See the "privileges.txt" file to set up advanced permission caps to avoid having to run this tool as root.

Gitweb link: http://gitweb.devoid-pointer.net/?p=LFSBench.git;a=summary

Quote from Ripley :

But he said his brother's pc is exactly the same, and it runs LFS!

It'd be helpful if they compared driver versions and installed updates on both machines. I've seen a laptop where I had to roll the audio drivers like five versions back to get the sound working...

Quote from Bose321 :

That must be why...my PC...without specific WDDM 1.2 drivers say that I have 1.2. Just like my previous graphics cards told me I had DX11 while they were DX9 only.

And where exactly did you look? When I run dxdiag it reports the WDDM version and supported D3D API versions correctly. (WDDM 1.0 and 9Ex in my case). Driver that shows WDDM 1.2 support was obviously designed with Win 8 in mind.

Quote from Bose321 :

I'm pretty sure you will have the same problems under Windows 7 if you had exactly the same drivers across the machine since the drivers on Windows 7 and Windows 8 are usually the same.

Except that they are... you know... not. Windows 8 features WDDM 1.2 as opposed to Win 7's WDDM 1.1 and the dxdiag report Danoon posted suggests that the drivers he has currently installed make use of WDDM 1.2. There is therefore a possibility that the drivers might work correctly on Win 7 because it's only something Win 8 specific that is broken.

You can lower the force feedback strength in the controller options in the game.

Quote from rowdog :

Catalyst is still way ahead of open driver. In the past, I've had to use Catalyst to run LFS and pretty much any game. I was shocked to see that LFS actually worked with the open driver when I came back after a year and a half. I'd guess that it works for me because Arch Linux uses a very recent version of the driver and my ATI 6950 is way over spec for LFS.

YMMV depending on the specific card model but I myself had a very pleasant experience with R6400M (and r600 based chip) and FOSS drivers. Even Unigine: Valley ran correcly. Hint: dynamic power management is still disabled by default on some cards so you might want to switch it on manually by specifying "radeon.dpm=1" in the kernel bootline. Besides saving a lot of power on idle it provides better performance as well.

As long as proper sysfs structure is created you can change the range in

like this

From kernel 3.16 the attribute won't be world-writable anymore so you'll need proper access right. I'll hopefully write a udev rule to automate this before 3.16 comes out.

A heads-up for Linux gamers using Logitech wheels. Due to this change (https://git.kernel.org/cgit/li ... 5e5c99d0d657d22a7dbc69334) it will no longer be possible to easily change the range of the wheel without proper permissions through sysfs. We intend to write a udev rule to resolve this situation properly and securely.

Quote from sicotange :

I could try a more recent version of Linux. To be honest I'm looking for the Linux version of XP. A no-bullshit OS stripped of glitter.

If you don't mind getting your hands dirty a little bit you can give some minimal installation of Debian Testing a shot. You'll get updates on a rolling basis but with (hopefully) sufficient soaking period to work out most of the problems. I've also had a pretty pleasant experience with LXDE spin of Fedora 19, although I used it only in VirtualBox for some kernel hacking

Quote from sicotange :

It's even worse with HTML5. Somehow Firefox manages to hang when a clip plays on youtube in HTML5 modus. That is when LFS is running. I suspect Wine is creating some sort of conflict.

You seem to be running a rather old kernel. The i915 driver in the kernel has received numerous improvements since 3.8.0 and so has Mesa (the OpenGL library). Unless you have specific reasons for using this version you might want to give another distro with newer software versions a go - or update if your distro provides updated packages. Ubuntu 14.04 uses kernel 3.13, recent updates of Fedora 20 gets you 3.14. Both of these distros are on mesa 10.1 with the possibility of mesa 10.2 arriving for F20.