Even before the patch I had on my notes to disable this warning if the actual ESC key is pressed. But it was too close to patch day, and I knew there would be a complication, because the assigned buttons do a fake key press. Do you think it would be fine if the warning only came up if an assigned controller button to ESC was pressed, and not the real key? It is extremely annoying when you are jumped out of that screen by mistakenly pressing the controller button assigned to ESC, so there is a good reason for this feature.
Your drivers are (falsely?) reporting the existence of at least one slider axis so it has the Slider 1 that, on some other Logitech wheels, is used for a clutch axis. It would be possible to specifically exclude this for that specific wheel. But it's not really a problem, I think. You can unassign that axis if it annoys you.
I don't know why you are seeing double vision effect. Normally when I have seen something like that, it was in a debug version or in some kind of view that caused the frame rate to go lower or half (e.g. in SHIFT+U mode, looking at the whole world). Is it any different if SteamVR is running or not running?
As Whiskey said, with Logitech wheels you need to refocus LFS once after plugging in the wheel, e.g. with ALT+TAB or by clicking on another window and back to LFS. Annoying but at least you don't need to restart LFS.
This should be fine now. It was fixed so when you are in the controls screen you see your own axes, not those of the viewed car.
Thanks, it seems quite clear now. It would be nice to stick with a single installation of LFS otherwise it's kind of wasteful.
So it looks like the basic things you need are:
1) Easy way to set up ONE wheel in an instance of LFS where there are actually several wheels connected to the computer. Basically selecting that device with a click or two after starting LFS and that could do a 'refresh' but ignore all the other controllers, not creating a massive list of axes and buttons.
2) A way to select the audio output device.
Those are the most important things. Then the next thing is:
3) A way for LFS to try to centre the wheel so it is ready at the start of a race or after a car reset.
After that there are refinements that would be nice but may be difficult and are not essential:
4) Some way to select a player or start up LFS with command line options that select the screen, wheel and speakers all in one.
For now I will just forget about number 4, assuming that you will be happy enough just being able to easily select the wheel device and audio device with the minimum amount of messing around after starting each instance of LFS. And I assume that you are happy enough with the screen setup, though I don't really know how you do that. Is it like one massive desktop, and you slide LFS across to the appropriate monitor then press SHIFT+F11?
The issue is unusual - using a single computer for multiple instances of LFS with their own input and output devices.
Each instance of LFS needs to be able to select its graphics and audio device and its force feedback input device.
OK, my first question is, do you have separate installations of Live for Speed on the single computer? A separate installation that is intended to connect to its required devices?
I understand this can be complicated / annoying to set up the first time, but it's not clear to me why you need to set it up again after a restart. Are the input devices not reported in the same order each time the computer starts? So that each instance of LFS can simply load its previously assigned axes and buttons?
Or is the problem that you don't know which ones will be plugged in, and it can be different every time?
I'll look into this audio device selection in the next few days. Hopefully will know more by Wednesday. I'm busy sorting out quite a few things at the moment.
Interesting, I agree a gently centering wheel would be useful.
Yes, it does seem to make sense that LFS could automatically connect the FF device to the device whose axis is selected for steering. Then there would be no need for the FF device option. I've added this to my notes. If anyone can think of a case where this would not work, please let me know.
You just need to set the numbers in the Range column. Move your handbrake axis to see which range it covers, and set those Range numbers to cover that range (or preferably a bit less than the range).
E.g. if the handbrake axis returns values from 5 to 1000, set the Range from 100 to 1000. Then the first bit of motion won't move the in-game handbrake at all, but the other 90% of movement will move the in-game handbrake.
The new system has far more possibilities than the old one but sometime you do have to type in a value, for these special cases.
It has been an interesting month for Virtual Reality, with the Oculus Rift and HTC Vive headsets now being shipped to customers. Live for Speed is so good to use in VR, it was our top priority to make sure it works with the new headsets and latest software. The result is our latest version, 0.6P, which you can now download. We also worked a lot on controller support. More game controllers and steering wheels are now set up automatically and multiple controller setups are also much better supported.
Thanks for the test. I realise that multiple controller setups will need axis reassignment the first time using this update.
I hope it is a bit easier now that the axis names are correct and there is a scroll bar that may help.
EDIT: also the first controller in the list should be set up correctly so one of the wheels should be already correct for one of your LFS instances. I hope your 3 LFS instances are installed into their own folders so each has a separate controller setup - otherwise I can't see how it would work!
There is a selector (in the Axes/FF section) for which device to use as the force feedback device. So for example if you have assigned axes to the third wheel in your list, you must also select the third force feedback device.
This should be selectable in the Logitech drivers software.
Interesting. I see that C button was quite useful at times. Anyway not really a problem because you can do exactly the same, but manually. You just want the min and max values to be centred around your centre value. In your case, it centres at -8, so you should reduce the max value for that axis by 16. So it runs from -1000 to 984. The good thing is that will really stay there as a user setting and you won't need to redo it each time.
If you have a Vive or Rift please give it a go. I'm also interested to hear from anyone if the automatic controller setup seems to work OK. To test that, move or rename the relevant .con file in your data\misc folder before starting LFS so LFS does not read your existing controller setup.