1. Could you extend "0-30, 0-60, 0-150 mph" values from "N.Ns" to "N.NNs" (in order to see changes 1/100sec), please.
2. When I watch the "Acceleration Data Table" and adjust gear ratios (for ex. 1st and/or 2nd gear) it is inconvenient to (RE)scroll-down data window to track changes at higher speeds (somewhere in the bottom of those text window), cause when data changes scroller goes up automatically.
It would be good to keep scroller's position.
2.5. It Also would be convenient to make LFS GRC window resizeable.
We could use maximize window then, and to see a lot more data from "Acceleration Data Table" . Graphs would be more detail/precise too
3rd - Is a kind of bug? :
When you start LFS GRC (I used v.2.5.1), you can not access Acceleration Graph
(these one
I've found the only way to make it available is to go to "Options -> Misc -> " and to uncheck (despite it was checked by default) "Enable Acceleration calc..s" checkbox and then put a check back.
Though, you should do it every application restart
Hi,
I've found strange FF-bug when using Formula XR, Formula V8, and FZ50GTR. Steps to reproduce:
1.Choose one of the above cars and use the game's road_1 setup (though bug occurs on other setups too).
2.Start practice/race
3.Stay motionless on the track (be at 0km/h and don't move)
4.Press brake pedal to the metal and hold it (at 100%)
5.Turn the steering wheel and release it from your arms
6.You'll get an infinite loop of huge oscillations.
My steering wheel moves from left to right and back to left infinitely.
You can see the video here: lfs_ff.mov (Quicktime-video, 4.5mb)
My system details:
I have a Microsoft FF Sidewinder wheel, wheel settings: FF strength set to 100%, centering force 0%.
[Added]: Deadzone set to 0.
Additional details: *Problem occurs when I use FF strength set to 50% and/or more.. (in LFS). *Problem occurs on Formula XR, Formula V8, and FZ50GTR cars.
*Problem doesn't occur on cars with road (non-slick) tyres (I've tested XF GTi and XR GT).
_______________________________________________________________
Is this a FF implementation bug or may it be connected to some tyre specific data ?