Live for Speed has released another minor update, bringing it to version 0.6F8. This minor update provides some more fixes to the title, as well as improving support for the Oculus Rift Virtual Reality headset. Some graphical updates have also been added, to improve the frame rate and loading times. For the full list of what has been added between the 0.6F and 0.6F8 update, check out the changelog below. Note that this is a test build, so there are likely some glitches, so if you come across any, you can comment in the thread here.
The LFS 6F update was released in June, and introduced support for the popular VR headset, and also upgraded the graphics engine to DirectX 9. Live for Speed’s developers also gave an update to the status of the long-awaited S3 update, assuring us that it is still in development. More tracks will also be updated to modern standards. For more on the 6F update and how Live for Speed S3 is coming along, you can check out the blog post here.
Changes from 0.6F7 to 0.6F8 :
Implemented Oculus Rift health & safety warning at startup
Option to store driving position (avoids setting it every time)
TIPS :
1) How to get LFS running on your Rift DK2 :
– Oculus Configuration Utility – Set your Rift to extended mode
– Windows Display – use extended desktop mode (not duplicated)
– Confusingly, set the DK2 to “portrait” (meaning rotated) mode in Windows
– Start LFS and click 3D on the View Options Screen
– Select Oculus Rift and click OK
– You should be given the option to exit, ready to restart in Rift mode
– Start LFS again after exiting in that way
2) To reset your seating position, there is a text command /rift reset which is assigned by default to the F8 key.
– Key assignments can be edited in Options – Game – F1 to F8
3) If, for any reason, LFS ends up on the Rift in 2D mode or with a black screen, you can get it back like this :
– Press ALT+F4 to exit LFS
– Delete the file “card_cfg.txt” in your LFS folder, so LFS starts up on the primary device (usually your monitor)
– After starting LFS again you can try to enter 3D mode again
4) Accessing your desktop while LFS is on the Rift.
– You will probably find that your mouse cursor is confined to the Rift’s virtual monitor
– Press CTRL+C to free the mouse and now the mouse can go onto the desktop
– When you click on a window on your desktop, LFS will be minimised
– To go back into the Rift, click on Live for Speed in your taskbar
Changes from 0.6F6 to 0.6F7 :
Graphical :
Removed / reduced some texture related graphical issues
Textures are automatically resaved (if needed) for faster load
Low res textures now load just as quickly as high res textures
FIX : Graphics options sometimes showed too many FSAA options
Misc :
Anisotropic filtering (AF) now default 4x
Mip bias sliders saved differently in cfg.txt
– You must set your mip bias and AF values again
Increased maximum value of multiplayer draw distance
Oculus Rift :
Mip bias sliders are available in Rift mode again (separate)
LFS starts up in windowed mode on desktop if unable to open Rift
Steer look and mouse look options are now disabled in Rift mode
Windows error message is displayed if the DLL cannot be loaded
Recompiled Oculus DLL now depends on fewer external libraries
FIX : Arcade view and helicopter view now work as expected
FIX : Button look and Pitch / Rotate view now work in Rift mode
FIX : Names above cars (N key) now stay still when view rolls
Changes from 0.6F5 to 0.6F6 :
Replay TV camera view is now displayed on a virtual monitor
3D level of the replay cameras adjustable from 0% to 100%
Changes from 0.6F4 to 0.6F5 :
Misc :
Frame rate limit now disabled if vertical sync is active
Oculus Rift :
Implemented chromatic aberration correction (pixel shader)
Simplified head yaw is transmitted in multiplayer packets
FIX : Low persistence setting could be out of sync with Rift
Changes from 0.6F3 to 0.6F4 :
Misc :
Driver’s body is now enabled by default
Reduced input lag when vertical sync is enabled
Oculus Rift :
Predicted head position is used with vertical sync
Enabled low persistence display mode (on by default)
More helpful and better looking multiple selection dialog
LFS will now start up on default device if Rift is not found
Helpful message if detected Rift has wrong screen orientation
Position is retained if headset moves out of tracking range
Single mip bias slider when in Rift mode
Changes from 0.6F2 to 0.6F3 :
First version with Oculus Rift DK2 support
FIX : Sometimes the wrong mip bias setting was used e.g. on text
FIX : LFS crashed if an out of bounds entry was typed in 3D dialog
Changes from 0.6F to 0.6F2 :
Two new 3D formats in TV / monitor /projector mode :
– red-cyan anaglyph
cheap red-cyan glasses are required
more expensive glasses can correct red (left) eye focus
colour perception is reduced and different in each eye
do not use this mode for a long time
– cross-eyed view
no equipment needed
the 3D world appears small
right eye looks at left image / left eye looks at right image
this is difficult for some people (with normal vision)
stop immediately if you feel any discomfort
do not use this mode for a long time
Skin downloading when watching a replay :
If a car or helmet skin in a replay is not available at LFS World
when you start the replay (with low or high res skins selected)
but you already have the skin in the other resolution then that
skin in the other resolution will be used instead of a plain car
Fixes :
Crash when using a wheel button assigned to /rift toggle command
Crash when pressing e.g. F8 when /press F8 was assigned to F8 key
Graphics :
New car shaders give higher frame rate when many cars on screen
FIX : Car lighting momentarily vertical as car entered a shadow
Misc :
Updated Estonian and Serbian translations
INSTALLATION INSTRUCTIONS :
A full version of LFS 0.6F must already be installed – www.lfs.net
To install the PATCH using the SELF EXTRACTING ARCHIVE :
1) Move or save the patch into your main LFS folder
2) Double click the patch to extract it to that folder
3) When you see “Confirm File Replace” select “Yes to All”
4) Now you can start LFS in the normal way
NOTE : You can see if the patch is correctly installed when you run
the program. At the bottom of the entry screen : 0.6F8