Kyoto and Westhill are empty. The other tracks all have spectators.

A VERY *3 minor issue, when running under wine if rift support is enabled LFS 0.6F3 will crash. With previous versions there was no crash [and I could pretend I was using a rift... ].

Hmm, if only creating in-car shadows was as easy as just "turning it on" :-)

You can use FaceTrackNoIR's Freetrack/TrackIR output (the default one) with LFS with no problems.

Personally I'm astonished that DK2 is incompatible with DK1, considering the whole point of the dev kits was to allow developers to get up to speed with programming for the thing.

Quote from cargame.nl :

Two things I noticed, the horizontal screen width cannot be bigger then 8000 mm ( 80 cm).

Uh, 8000 mm is 8 metres...

Hmm, in fact there is almost never any need to manually set the IP address, but I guess that isn't clear to people.

Not quite, the content of that page hasn't been updated since May 2008.

No, the potentiometers divide the voltage, so the range will still be the same.

Would be interesting to see how SM3 affects us Wine users too.

Interesting stuff. Regarding bloom and other lens effects; I like to think I'm looking at the scene through my own eyes, not with a camera.

Well, sending commands from the CPU to GPU also takes time. Rendering the cars in 1 pass instead 3 passes will save a bit.

I've noticed there are minor graphical differences between 0.6F and 0.6F2: the dashboard surround on the XRG/XRT is slightly lighter in 0.6F2, for example.

I don't have the glasses so I can't be sure, but I suspect those IPD and screen measurements will only work with a more accurate FOV. But most people don't drive with an accurate FOV and stick to 90 or more to get an artificial feeling of speed.

Anaglyph mode doesn't support multiple monitors either (so no angle or bezel compensation), so even though I do use 3 monitors with a more-or-less correct FOV, it's not going to work here. Yet.

You should try to understand what you've written and why it behaves the way it does. Follow the loops and conditions yourself, in your head. It's not magic, it's just logic.

You could do something like this, though of course I've not tested it:


But without understanding the code you're writing, and why, you're not going to get very far.

You've unrolled the loop (but left the loop in) and created every button again for each player.

Please learn about logic and flow-control, it's fundamental to programming.

0.6F2 works fine on my Linux install, with wine 1.4.1, and nvidia 319.82 drivers.

Do you feel in a position to be ready with taking pre-orders? :-) (a.k.a. take my money!)

Most people don't play racing simulators. Please shut up.

Agree with Forbin, sounds like the system RAM is dying. Try running memtest86.

We've already had the massive tease! We're now already being teased by not knowing when it will be released. Let Scawen get on with doing what is needed :-)

Quote from Aukoue :

I have, but then the steering wheel just starts spinning whenever I hit something. Without vibrations, it feels so unnatural!

I suggest you hold the steering wheel to stop it spinning. Mind control doesn't work too well.

G25s and G27s do not have a wheel vibration effect; it is faked in some games by alternating the wheel direction rapidly. LFS does not simulate vibration of the car through the wheel, only motion of the wheel based on forces to the steering system.

Quote from 5tag :

The same could be said about the parallel view side-by-side option. If half of your screen width is bigger than the distance between your pupils (which is almost certainly the case with say a 17" screen or bigger) you would actually need to point your eyes slightly outwards (Exotropia).

Side-by-side isn't actually displayed like that (except maybe on VR headsets where it's in-your-face), there is trickery within the monitor to present a single 3D image.

Quote from cargame.nl :

OK lets say it more detailed, there are still a lot out there who only have a single core processor, so there is no "putting thisandthat" on another core for them. I also don't get the impression from Scawen that he wants to drop all single core support so it then does not really matter does it?

Supporting multiple cores means using more threads. Single core processors are perfectly capable of running multiple threads.

Quote from cargame.nl :

Besides, multi core processors can compensate -a lot- themselves concerning single core programs (just explained in that short video). I don't really see the point what you try to make. There are not even problems with multi core processors. Why spend time on a problem which isn't a problem?

Not all multi core CPUs have Turboboost, and even when they do, properly sharing the workload, let's say over 4 cores at 3GHz, is way more beneficial than gaining a few hundred MHz on one core.

(By no means am I suggesting that actually using multiple threads is simple, mind you)

Last edited by PeterN, Wed, 2 Jul 2014 08:57.

"old solid state"

It's probably developed a fault which has made it unsafe to use. If you have the schematics you could try fault finding, if not finding a competent service engineer is a bit tricky in this modern throw-away world.

it seems likely the audio input on the amplifier is actually live to some degree, and connecting that to the earthed audio output on the computer will trip the safety devices on your supply. The mobile phone won't be earthed which is why it doesn't happen there.

Do not continue to use it until you find out what is wrong!

Gutholz, your PDF seems to have been printed in reverse... page 1 is at the bottom.