It should work without any problems as long as each device is a joystick on its own. Are you looking to make a DIY handbrake? You can use arduino proMicro to be your joystick interface. Let me know if you need to know more about how to make one.
Yes, that's exactly why the clutch bite point in real sports cars is shorter. It's a tradeoff between being able to go through gears as fast as possible and a good start from a stand still. In a race, you use cluth to start only a few times, while gear shifts are in hundreds - thousands of times, so this is how it's optimized. Definately a very different use case compared to a normal road car driving.
In logi driver set 104% overall and use about 15% in lfs. Start from there and then adjust ffb in lfs only for each car to what feels good for you. Yes, driving with 1:1 steering in cars with 900deg is not easy at all, but I recommend you to use 1:1 for each car. If you plan to do drifting or rallyor just fool around, then you can lower it.
To set 1:1 steering, there are 2 ways. One is manualy in logi drivers, but this is simply a hassle if you change cars often. A better way is to leave lfs do it for you. In that case, set in logi driver 900deg and in lfs set wheel turn to 900 and wheel turn compensation to 1. The only downside of automatic is that you may lose electronic endstop effect - you will be able to rotate the wheel past the rotation limit for cars that have less than 900deg, but it's not a big deal concerning the benefits.
Yes, that would be doable, it's a good idea. You can play around and make the curve such that it's almost flat at the top, with a very small angle between horizontal line and then a bigger angle down to 0 input. The break point (center) could be somewhat before the actual central value of input. If you are very keen on doing a real life smooth start, some trial and error is required untill you nail the curve.
Note that axis clutch in lfs is saturated completely (fully open clutch) for about 70% of axis input, so take that into consideration when playing with DXtweak axis calibration.
Well, the bite point of clutch is known to be very small in lfs. One has to be very precise, so 8bit (logitech) pedals will not cut it. With 10bits like the ones from thrustmaster, it's a little bit easier, but still quite challenging.
We did mention this to Scawen, but for bikes. I wouldn't worry about it too much before a new tire physics is released. Then we can go nuts with all kinds of requests
Yeah, I think good solution would be a text command to set this timeout in server side. Default timeout should be in the order of magnitude of 1 lap, so 4min sounds reasonable.
You have to debug your code to see where the problem is. Without posting what you have so far and what is inside of this txt file, it's impossible to help further.
You have to put a limit such that $CurrPage is never negative (or less than 1) which ever is the starting value, it must not be less than starting value. But as I see, this limiter is already there, so there should be no problem. What kind of problem do you observe when pressing page back button?
This doesn't seems like a scroll bar as you would see in windows for example. I think it's just a manual trick, that shows certain number of lines of text. Pressing up and down button just itterates through the array, or some index.