Although I see they require XRdials_ALP.dds to be modified too. My first XFG dash used empty dds file to maximize dash area just like those, but pretty soon I realised of all the flaws that come with it. Well I didn't supply dds files with it to be honest, but there will always be someone who will simply forget to do that and dash will not look like it is supposed to.
Also including such a dashes into autoinstaller will require some changes and complexity. I don't think I should just like that overwrite dds textures, users consent is definitely needed in that case IMO.
I thought to do that, but mpg seem rather complicated because there are several Gallon definitions. I can detect if mph is selected in LFS and automatically change to L/100Km to mpg, however question is which one?
Probably I could add another option to select which gallon you want to use, but I guess most people will leave it on default so they will see "wrong" fuel consumption.
Go to data\scripts\autoexec.lfs, open it with notepad. That is script that executes each time LFS starts. You will see the line that starts LFSLazy as example.
Heppi ju tuu sober edgar
However some of that stuff used (what can I see from pic) is still unavailable in public version, so it will not work as it should.
Is there any chance to make it working on openconfigs? Realtime gap is not required, just the gap on splits. Also would be nice to have positions list working there. I guess it is loads of work and I ask too much eh...
That sounds like doable. Will put that on TO-DO, tho haven't done any work on LFSLazy recently so not sure when will it be. There are some other things on my mind these days like the existance of mankind.
Main problem is correctly detecting open config tracks. That would most likely require reading loaded layout and comparing checkpoints position and heading. Of course in that case there should be hardcoded data about checkpoints of all open config tracks. And still even if I do that only thing I really gain is realtime gap and gap on splits.
Position list work based on nodes for MCI, as there is no nodes on open configs not sure that there is much I can do.
First thing is most likely to be done, but as there are so much open config tracks and it would require modifying quite some code I'm not sure I will do that anytime soon.