Have a look here, works well https://forum.studio-397.com/index....ith-look-ahead-or-look-to-apex-feature.39316/
Is there any chance the help thread can be updated? My payer.json has two lines for the lookahead angle, but it does not exactly match the information posted years ago. Here is the original line: Lookahead Angle="1.70000" // Angle to lookahead (yaw) w/ steering in radians (= degrees / 57) and here is what I have in my player.json "Lookahead Angle":0.2, "Lookahead Angle#":"Angle to lookahead (yaw) w\/ steering in radians (= degrees \/ 57)",
@davehenrie That's exactly the same parameter, the first is in .ini format, the second is in JSON format. The parameter and explanation hasn't changed at all. The main 'danger' when editing the value is accidentally deleting the , after the value, which will break it. An editor that recognises JSONs properly will likely show it more like the example, by the way. The formatting comma and extra slashes are just part of the JSON layout, a proper viewer won't show them.
I was able to find a cheap 24" widescreen. Between that and the look-to-apex adjustment, I can run the correct FOV and be able to see around just fine.