I did a fresh clean install of LFS 0.7D into a new folder.
I changed the cfg.txt file as suggested, on both LFS (old folder and new folder)
On this fresh install I was able to apply patches 0.7D15, 0.7D16 and 0.7D17. And they all worked correctly.
In my old LFS folder I installed several patches and all patches prior to 0.7D16 worked fine.
But patches 0.7D16 and 0.7D17, in my old LFS folder makes LFS crash.
But if I install patch 0.7D15 or earlier everything works fine again.
Probably the problem is on my machine. I will gradually migrate the settings and scripts from the old folder to the new one to see what could have caused the problem.
It's a great opportunity to clean up the LFS folder.
Maybe someday you'll find time to improve the display of car damage as well? Currently, it's difficult to "read" which part is damaged and how bad (without consulting the documentation). Perhaps there will later be a similar representation as for engine damage. That would be cool too!
This point is probably already on your list. In any case, I'm also looking forward to further improvements to the details.
Personally, I’m not sure if you really want the average.
The average doesn’t matter as much as the actual, having both of course works, but if is necessary…
But I’ve literally wanted this for 16 years :happytears:
Whilst I agree, the average will only always play catch up to the Actual fuel used.
Fx. If you have a code 80 for 3 laps, then the avg is going haywire untill it’s coming back to normal.
I believe this was also the issue with “Laps of fuel left” if you had driven slowly for some laps, it took a long time before it became relevant and true again.
New display in F9 / F10 views shows estimated laps given fuel usage
Mods to delete in Cleanup mode of mods screen are shown bright red
FIX: Some cars' live settings were not adjustable without F11 view
FIX: /altf and /ctrlf now cannot be followed by another command
More updated translations - thank you translators!
I agree with johneysvk, that something like a 5 lap (or adjustable) average would be more useful to track driving style changes in practive. Also looking at the screenshot above I can't help but to ask if there is an standardized clutch icon we could use instead of "CT" with isn't as really self-explanatory as the rest (while also using a different font compared to the other "middle stuff").
On a personal side note (and this really is for later): It might be a good idea to make the "F9 view" either more customizable (like being able to hide stuff like the g-meter). It's kinda becomming crowded with additional information. As an alternative anything related to "damage" (Engine, Clutch?) could also find a home in the "F10-view"
Maybe having the choice between avg of last 5-10-15 or fuel per lap would be a solution, I think everyone is in two minds about how the “right way” is for reading fuel.
*EDIT* Personally I would always like to mark a lap, we have this function on the real cars to mark a lap, and use that for referencing deltas etc, same goes for fuel, so it shows -0.07 or +0.07 if you’ve used more or less last lap, it’s very handy when you have to make 28 laps but can only do 27 on full push
I agree 3J it is getting a bit crowded but it does look like Scawen has a bit of a design update in store for us when looking at text font etc.
Hi Scawen, I tested version 0.7D18 with the scripts I have on LFS startup and everything worked correctly.
I use a series of scripts to dynamically change the functions of the buttons on the DFGT steering wheel. These scripts are based on a set of scripts I found on the forum.
I'm attaching the scripts to this message in case you want to do some additional testing.
Thanks for that. I've checked it out and reproduced the hang.
Now I think that, with the latest fix, it is actually OK. Without the fix, the line splitting interpreted many of those key assignments as "run this script right now". As there were several such assignments in each file, the bug caused many recursive script calls. There is a recursion depth limit but that didn't prevent the problem. For example if the recursion depth limit is 12, but each scrips calls 10 scripts (because of the bug) it could run 10*10*10*10*10*10*10*10*10*10*10*10 scripts. So it may not have been a true hang but could take an extremely long time to complete the task.
That is just a normal thing that can sometimes happen, but actually is just antivirus giving a false positive. That has been the case every time that has happened in the past.
We now have 3 download locations for mods (NL/JP/US)
If you enable Options... Misc - Allow HTTP redirect [EXPERIMENTAL]
Locations in Asia and Oceania should download mods from Japan
Locations in North and South America should download from USA
In that case you should see a yellow redirect chat message
Please let us know if this helps!
Sorry, I should have made clear: I don't use those automatic startup scripts - I'm not calling them, only LFS is (the automated calling). IE, whatever LFS does is triggering the warning.
I've just checked, and the script is still being run despite the warning.